Summary: | [Win] fast/multicol/hit-test-above-or-below.html fails | ||
---|---|---|---|
Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | ahmad.saleem792, bfulgham, bweinstein, kadam, mitz, simon.fraser |
Priority: | P3 | Keywords: | LayoutTestFailure, Qt, QtTriaged |
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Linux |
Description
Csaba Osztrogonác
2010-03-10 08:36:24 PST
Tomorrow I'm going to fix this bug. I skipped this test until fix to make Qt bot green again: http://trac.webkit.org/changeset/55782 I wonder if this is due to the non-Mac text selection behavior some ports implement. This test fails on Windows as well (in the same way) - Skipped in r56634. Is Anybody working this bug? Now This test is working on Qt WK2, but still fails on Qt WK1. Diff is here: --- /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/fast/multicol/hit-test-above-or-below-expected.txt +++ /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/fast/multicol/hit-test-above-or-below-actual.txt @@ -11,9 +11,9 @@ Character at 150, 275 is d as expected. Character at 350, 275 is j as expected. Character at 550, 275 is m as expected. -Character at 750, 275 is null as expected. +FAIL: Character at 750, 275 is m. Expected null. Character at 150, 475 is d as expected. Character at 350, 475 is j as expected. Character at 550, 475 is m as expected. -Character at 750, 475 is null as expected. +FAIL: Character at 750, 475 is m. Expected null. I added to Qt WK1 TestExpectations. (only) Committed r131051: <http://trac.webkit.org/changeset/131051> === Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines. This is still a failure for the Win port. We don't have any platform specific expectation for this test and AppleWin port is gone. So Marking this as 'RESOLVED CONFIGURATION CHANGED'. |