RESOLVED FIXED 83923
Track rem unit usage in StyleSheetInternal
https://bugs.webkit.org/show_bug.cgi?id=83923
Summary Track rem unit usage in StyleSheetInternal
Antti Koivisto
Reported 2012-04-13 11:40:26 PDT
Currently CSSParser sets usesRemUnits flag directly to Document. It should be set to the stylesheet instead so parser does not need to know about the document. This also avoids setting the flag unnecessarily when the stylesheet is not used.
Attachments
patch (5.76 KB, patch)
2012-04-13 11:43 PDT, Antti Koivisto
webkit.review.bot: commit-queue-
Archive of layout-test-results from ec2-cr-linux-03 (6.33 MB, application/zip)
2012-04-13 13:35 PDT, WebKit Review Bot
no flags
Antti Koivisto
Comment 1 2012-04-13 11:43:33 PDT
Andreas Kling
Comment 2 2012-04-13 11:55:30 PDT
Comment on attachment 137116 [details] patch r=me
Antti Koivisto
Comment 3 2012-04-13 12:23:05 PDT
Comment on attachment 137116 [details] patch This needs to deal with inline style too
Andreas Kling
Comment 4 2012-04-13 12:25:59 PDT
(In reply to comment #3) > (From update of attachment 137116 [details]) > This needs to deal with inline style too Eep. Indeed. The easy way would be to simply have Document check the uses-rem-unit bit on its elementSheet() as well, but that would take us one step further away from killing elementSheet().
WebKit Review Bot
Comment 5 2012-04-13 13:35:42 PDT
Comment on attachment 137116 [details] patch Attachment 137116 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/12393979 New failing tests: fast/css/rem-dynamic-scaling.html
WebKit Review Bot
Comment 6 2012-04-13 13:35:48 PDT
Created attachment 137137 [details] Archive of layout-test-results from ec2-cr-linux-03 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-03 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Antti Koivisto
Comment 7 2012-04-13 14:24:00 PDT
http://trac.webkit.org/changeset/114168 (with a fix for the failing test)
Note You need to log in before you can comment on or make changes to this bug.