Bug 61190
| Summary: | fast/dom/HTMLFormElement/associated-elements-after-index-assertion-fail1.html failing on Windows since r86936 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | WebKit Review Bot <webkit.review.bot> |
| Component: | DOM | Assignee: | WebKit Review Bot <webkit.review.bot> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | jberlin, morrita, tkent |
| Priority: | P2 | Keywords: | LayoutTestFailure, PlatformOnly, Regression |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | Windows 7 | ||
| URL: | 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 | ||
WebKit Review Bot
HTMLFormElement/associated-elements-after-index-assertion-fail1.html failing on Windows since r86936
Requested by jessieberlin on #webkit.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jessie Berlin
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
Kent Tamura
Does Windows port have ENABLE_PROGRESS_TAG?
Kent Tamura
(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.
Kent Tamura
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
Jessie Berlin
Thanks Kent!