Bug 93960

Summary: [Qt] Remove FontQt4, HAVE_QRAWFONT flag and the related dead code
Product: WebKit Reporter: Pierre Rossi <pierre.rossi>
Component: New BugsAssignee: Pierre Rossi <pierre.rossi>
Status: RESOLVED FIXED    
Severity: Normal CC: dglazkov, eric, hausmann, mifenton, noam, vestbo, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Pierre Rossi
Reported 2012-08-14 05:32:41 PDT
[Qt] Remove FontQt4, HAVE_QRAWFONT flag and the related dead code
Attachments
Patch (48.24 KB, patch)
2012-08-14 05:41 PDT, Pierre Rossi 		no flags
DetailsFormatted DiffDiff
Patch (48.17 KB, patch)
2012-08-14 06:05 PDT, Pierre Rossi 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Pierre Rossi
Comment 1 2012-08-14 05:41:35 PDT
Created attachment 158303 [details] Patch
Gyuyoung Kim
Comment 2 2012-08-14 05:46:59 PDT
Comment on attachment 158303 [details] Patch Attachment 158303 [details] did not pass efl-ews (efl): Output: http://queues.webkit.org/results/13494524
Build Bot
Comment 3 2012-08-14 05:56:34 PDT
Comment on attachment 158303 [details] Patch Attachment 158303 [details] did not pass mac-ews (mac): Output: http://queues.webkit.org/results/13492536
WebKit Review Bot
Comment 4 2012-08-14 06:00:58 PDT
Comment on attachment 158303 [details] Patch Attachment 158303 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13490556
Pierre Rossi
Comment 5 2012-08-14 06:05:16 PDT
Created attachment 158310 [details] Patch In my enthusiasm, it seems I had removed one PLATFORM(QT) too many in cross-port code...
WebKit Review Bot
Comment 6 2012-08-16 03:53:23 PDT
Comment on attachment 158310 [details] Patch Clearing flags on attachment: 158310 Committed r125766: <http://trac.webkit.org/changeset/125766>
WebKit Review Bot
Comment 7 2012-08-16 03:53:28 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.