Created attachment 177995 [details] Patch

Created attachment 177996 [details] Patch

(In reply to comment #2) > Created an attachment (id=177996) [details] > Patch For the record it is enabled on other ports for some days : Mac, Qt, EFL and GTK. Also as per discussion http://lists.webkit.org/pipermail/webkit-dev/2012-December/023064.html where we decided that when it's ready we'll remove the feature flag (as it is not a major feature). I believe that it's time for it to run on Chromium as well so I can look the bots and remove the feature flag if no problems show up. It is tracked by https://bugs.webkit.org/show_bug.cgi?id=37514

I'll defer to Ojan and/or Tony on this one. They likely have more context here.

(In reply to comment #4) > I'll defer to Ojan and/or Tony on this one. They likely have more context here. I would also need to rebase a few files on Chromium expected files just as http://trac.webkit.org/changeset/136844 and http://trac.webkit.org/changeset/136847. There were broken expected result anyway. Any pointers on how I can do that on all supported Chromium platforms?

> Any pointers on how I can do that on all supported Chromium platforms? Practically speaking, you'll need to land your patch first and then use garden-o-matic.

Comment on attachment 177996 [details] Patch Attachment 177996 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/15174364 New failing tests: ietestcenter/css3/bordersbackgrounds/background_position_three_four_values.htm svg/hixie/intrinsic/003.html css2.1/20110323/replaced-intrinsic-003.htm

Comment on attachment 177996 [details] Patch Clearing flags on attachment: 177996 Committed r136970: <http://trac.webkit.org/changeset/136970>

All reviewed patches have been landed. Closing bug.