UNCONFIRMED 90156
[WK2] platform/mac/editing/spelling/autocorrection-blockquote-crash.html fails
https://bugs.webkit.org/show_bug.cgi?id=90156
Summary [WK2] platform/mac/editing/spelling/autocorrection-blockquote-crash.html fails
Andreas Kling
Reported 2012-06-28 03:57:25 PDT
This test is failing on Mac/WK2 bots since its introduction in <http://trac.webkit.org/changeset/121299> --- /Volumes/Data/slave/lion-debug-tests-wk2/build/layout-test-results/platform/mac/editing/spelling/autocorrection-blockquote-crash-expected.txt +++ /Volumes/Data/slave/lion-debug-tests-wk2/build/layout-test-results/platform/mac/editing/spelling/autocorrection-blockquote-crash-actual.txt @@ -1,13 +1,13 @@ This test checks that markers are correct when auto correcting in the blockquote. If you type "n" and " ", there should be blue dots under information, but is off by one. Note, this test can fail due to user specific spell checking data. If the user has previously dismissed 'notational' as the correct spelling of 'notationl' several times, the spell checker will not provide 'information' as a suggestion anymore. To fix this, remove all files in ~/Library/Spelling. -PASS internals.hasAutocorrectedMarker(document, 0, 1) is true +FAIL internals.hasAutocorrectedMarker(document, 0, 1) should be true. Was false. PASS successfullyParsed is true TEST COMPLETE would this -testinformation +test infomation make a difference?
Attachments
Andreas Kling
Comment 1 2012-06-28 10:15:33 PDT
Alexey Proskuryakov
Comment 2 2014-11-12 12:14:37 PST
The was not actually fixed (the commit only skipped the test), and the test fails for me locally: -PASS internals.hasAutocorrectedMarker(5, 10) is true +FAIL internals.hasAutocorrectedMarker(5, 10) should be true. Was false. PASS document.querySelectorAll("blockquote").length is 1 -PASS document.querySelector("blockquote").innerText.indexOf("notational") is 18 +FAIL document.querySelector("blockquote").innerText.indexOf("notational") should be 18. Was -1. PASS successfullyParsed is true
Note You need to log in before you can comment on or make changes to this bug.