14725 2007-07-23 11:25:24 -0700 [gtk] The WebKit Gtk+ port needs to be completed 2007-11-29 17:20:56 -0800 1 1 1 Unclassified WebKit New Bugs 523.x (Safari 3) All All RESOLVED INVALID Gtk P2 Normal --- 14726 14727 14729 14730 14731 14732 14734 14735 15561 1 zecke webkit-unassigned oldest_to_newest 3946 0 zecke 2007-07-23 11:25:24 -0700 We would like to have a complete WebKitGtk port as WebKit is a great rendering engine. Pending issues, design decisions will be created as individual bugs and link to this one. 3922 1 zecke 2007-07-23 13:14:35 -0700 Add the Gtk keyword, even to the curl bugs. 59264 2 alp 2007-10-23 12:46:04 -0700 The GTK+ port is in constant development and will never be completed. 59317 3 zecke 2007-10-24 00:52:18 -0700 That was not smart. You just destroyed the concept of keeping track of what needs to be done for the port.... Where do you want to document shortcomings, bugs, etc. then? If someone asked what needs to be done I always was able to point to bug #14275, what will be the replacement? 62736 4 alp 2007-11-29 17:20:56 -0800 (In reply to comment #3) > That was not smart. You just destroyed the concept of keeping track of what > needs to be done for the port.... > Where do you want to document shortcomings, bugs, etc. then? If someone asked > what needs to be done I always was able to point to bug #14275, what will be > the replacement? > We have several tags for the GTK+ port and even a Bugzilla component now. Our wiki pages link to a saved search that lists all bugs relevant to the GTK+ port. Using a tracking bug like this for a whole port seems redundant.