Bug 61190 - fast/dom/HTMLFormElement/associated-elements-after-index-assertion-fail1.html failing on Windows since r86936
Summary: fast/dom/HTMLFormElement/associated-elements-after-index-assertion-fail1.html...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All Windows 7
: P2 Normal
Assignee: WebKit Review Bot
URL: http://build.webkit.org/results/Windo...
Keywords: LayoutTestFailure, PlatformOnly, Regression
Depends on:
Blocks:
 
Reported: 2011-05-20 08:33 PDT by WebKit Review Bot
Modified: 2011-05-20 13:03 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description WebKit Review Bot 2011-05-20 08:33:09 PDT 
HTMLFormElement/associated-elements-after-index-assertion-fail1.html failing on Windows since r86936
Requested by jessieberlin on #webkit.
Comment 2 Kent Tamura 2011-05-20 09:02:02 PDT 
Does Windows port have ENABLE_PROGRESS_TAG?
Comment 3 Kent Tamura 2011-05-20 09:07:01 PDT 
(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.
Comment 4 Kent Tamura 2011-05-20 09:22:03 PDT 
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
Comment 5 Jessie Berlin 2011-05-20 13:03:05 PDT 
Thanks Kent!