Summary: | HTMLInputElement's value change does not trigger spellchecker | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Grzegorz Czajkowski <g.czajkowski> | ||||
Component: | HTML Editing | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | darin, rniwa | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=236937 | ||||||
Attachments: |
|
Description
Grzegorz Czajkowski
2014-12-10 01:36:58 PST
I am wondering whether it is something that we want to fix or it has been done by purpose? It looks like we have inconsistency as execCommand(InsertText, ...) does spell check but input.value call does not. Yes, this was originally done on purpose. The idea is that setting a value from script is not the same thing as typing. Whether this should be changed or not is a judgement call that requires more information. Do websites depend on one behavior or the other? Is there a standard for this? Do other web browsers consistently do this in a way that is different from what WebKit-based browsers do it? |