Summary: | Has inconsistent font selection behavior compared with other GTK2 apps | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Hongzheng Wang <wanghz> | ||||
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | gustavo, kenneth, mrobinson, tonikitoo, xan.lopez | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
Hongzheng Wang
2009-05-24 23:57:08 PDT
Created attachment 32682 [details]
Patch to fix QuickTime/X11 namespace conflict
(In reply to comment #1) > Created an attachment (id=32682) [details] > Patch to fix QuickTime/X11 namespace conflict Also, epiphany guys cc'ed ps: patch looks unrelated and is in so bad shape (lack of commit message and explaination, lack of context, etc). Is this still an issue? A lot has changed with font selection. If you notice some inconsistency between Chromium/Firefox and WebKitGTK+, I'd be very interested to fix it. I see Chromium and Firefox selecting the same font that WebKitGTK+ does in the situation listed above. If this is not truly the case or there is some further issue, feel free to reopen this bug. I think it may be fixed now though. |