RESOLVED FIXED 168423
[GTK] Test fast/shadow-dom/input-element-in-shadow.html is failing in the bots
https://bugs.webkit.org/show_bug.cgi?id=168423
Summary [GTK] Test fast/shadow-dom/input-element-in-shadow.html is failing in the bots
Carlos Garcia Campos
Reported 2017-02-16 05:00:55 PST
It's failing only because the result has the spell checker underline, while the the reference image doesn't. I don't know why the slot is spell checked and the input in the reference isn't, but we could make the test pass by using real words, since the contents are not important for this test.
Attachments
Patch (2.03 KB, patch)
2017-02-16 05:02 PST, Carlos Garcia Campos
no flags
Carlos Garcia Campos
Comment 1 2017-02-16 05:02:57 PST
Michael Catanzaro
Comment 2 2017-02-16 09:36:35 PST
I think you're changing the test to work around a real bug in our text checker. Entering a misspelled word should not trigger a spell checker underline until a separator character (space, period, etc.) is inserted, and this test does not insert such a separator character, so this test should not trigger the spell checker underline. On the other hand, this test is definitely not intended to test the text checker. I'll give Ryusuke a chance to review this since shadow DOM is his area, even if the change is trivial.
Ryosuke Niwa
Comment 3 2017-02-16 14:37:08 PST
Comment on attachment 301747 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=301747&action=review > LayoutTests/ChangeLog:10 > + by using real words, since the contents are not important for this test. Use "one", "two" instead of "abc", "def". That's because we use eventSender to type in text. Spellchecker only kicks in for user-typed text The fix is correct.
WebKit Commit Bot
Comment 4 2017-02-16 22:28:35 PST
Comment on attachment 301747 [details] Patch Clearing flags on attachment: 301747 Committed r212536: <http://trac.webkit.org/changeset/212536>
WebKit Commit Bot
Comment 5 2017-02-16 22:28:39 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.