WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
14725
[gtk] The WebKit Gtk+ port needs to be completed
https://bugs.webkit.org/show_bug.cgi?id=14725
Summary
[gtk] The WebKit Gtk+ port needs to be completed
Holger Freyther
Reported
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.
Attachments
Add attachment
proposed patch, testcase, etc.
Holger Freyther
Comment 1
2007-07-23 13:14:35 PDT
Add the Gtk keyword, even to the curl bugs.
Alp Toker
Comment 2
2007-10-23 12:46:04 PDT
The GTK+ port is in constant development and will never be completed.
Holger Freyther
Comment 3
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?
Alp Toker
Comment 4
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.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug