61190 2011-05-20 08:33:09 -0700 fast/dom/HTMLFormElement/associated-elements-after-index-assertion-fail1.html failing on Windows since r86936 2011-05-20 13:03:05 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All Windows 7 RESOLVED FIXED http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r86936%20(13054)/fast/dom/HTMLFormElement/associated-elements-after-index-assertion-fail1-pretty-diff.html LayoutTestFailure, PlatformOnly, Regression P2 Normal --- 1 webkit.review.bot webkit.review.bot jberlin morrita tkent oldest_to_newest 407110 0 webkit.review.bot 2011-05-20 08:33:09 -0700 HTMLFormElement/associated-elements-after-index-assertion-fail1.html failing on Windows since r86936 Requested by jessieberlin on #webkit. 407114 1 jberlin 2011-05-20 08:37:11 -0700 http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r86936%20(13054)/results.html http://build.webkit.org/builders/Windows%207%20Release%20%28Tests%29/builds/13053 407135 2 tkent 2011-05-20 09:02:02 -0700 Does Windows port have ENABLE_PROGRESS_TAG? 407140 3 tkent 2011-05-20 09:07:01 -0700 (In reply to comment #2) > Does Windows port have ENABLE_PROGRESS_TAG? Well, the answer is "NO". http://build.webkit.org/builders/Windows%20Release%20%28Build%29/builds/16621/steps/compile-webkit/logs/stdio So, this test result change is correct because the style definition for <progress> in html.css is enabled only for ports with ENABLE_PROGRESS_TAG by r86936. 407156 4 tkent 2011-05-20 09:22:03 -0700 I added it to win/Skipped rather than adding new test expectation because adding <progress> support for Windows is the right solution. https://trac.webkit.org/changeset/86962 407286 5 jberlin 2011-05-20 13:03:05 -0700 Thanks Kent!