Bug 14725 - [gtk] The WebKit Gtk+ port needs to be completed
Summary: [gtk] The WebKit Gtk+ port needs to be completed
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 523.x (Safari 3)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: Gtk
Depends on: 14726 14727 14729 14730 14731 14732 14734 14735 15561
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-23 11:25 PDT by Holger Freyther
Modified: 2007-11-29 17:20 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Freyther 2007-07-23 11:25:24 PDT
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.
Comment 1 Holger Freyther 2007-07-23 13:14:35 PDT
Add the Gtk keyword, even to the curl bugs.
Comment 2 Alp Toker 2007-10-23 12:46:04 PDT
The GTK+ port is in constant development and will never be completed.
Comment 3 Holger Freyther 2007-10-24 00:52:18 PDT
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?
Comment 4 Alp Toker 2007-11-29 17:20:56 PST
(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.