Update semantics for selection in response to changing value in input/textarea |
|||
Issue descriptionThe spec was recently changed in https://github.com/whatwg/html/pull/2437. See the new spec at: - https://html.spec.whatwg.org/multipage/forms.html#dom-input-value-value - https://html.spec.whatwg.org/multipage/forms.html#dom-textarea-value Web platform tests are available at http://w3c-test.org/html/semantics/forms/textfieldselection/selection-after-content-change.html
,
Apr 28 2017
Note the tests were slightly updated so you're failing more now; probably same root cause though. Mozilla is shipping this change in https://bugzilla.mozilla.org/show_bug.cgi?id=1357206 and is a little worried about compat fallout, so I think it would be good to prioritize this. As such I'll update to P2. I recognize we might not be able to get to it in time for M60 since tkent@ is a busy person and also unavailable until May 8 per his sidebar flair.
,
May 16 2017
,
May 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7a3533d54795261d46e4e16d5a1bc5c07ecb087f commit 7a3533d54795261d46e4e16d5a1bc5c07ecb087f Author: tkent <tkent@chromium.org> Date: Tue May 16 06:07:08 2017 INPUT element: Do not update selectionStart/selectionEnd on |value| IDL setter if the new value is same as the old value. The HTML standard was updated recently to clarify this behavior. The new behavior matches to TEXTAREA element, and Firefox 55. BUG= 712352 Review-Url: https://codereview.chromium.org/2884603002 Cr-Commit-Position: refs/heads/master@{#472028} [delete] https://crrev.com/8a949f82ddc941825c2b3f6529e6ca95f7f7ed0a/third_party/WebKit/LayoutTests/external/wpt/html/semantics/forms/textfieldselection/selection-after-content-change-expected.txt [modify] https://crrev.com/7a3533d54795261d46e4e16d5a1bc5c07ecb087f/third_party/WebKit/Source/core/html/HTMLTextAreaElement.cpp [modify] https://crrev.com/7a3533d54795261d46e4e16d5a1bc5c07ecb087f/third_party/WebKit/Source/core/html/forms/TextFieldInputType.cpp
,
May 16 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dominicc@chromium.org
, Apr 18 2017Owner: tkent@chromium.org
Status: Assigned (was: Untriaged)