We’re currently setting this when the parent of the input is a XUL element, which targets very well XUL <textbox> where the input is guaranteed to be a child of a XUL moz-input-box. However, with the recent conversions from <textbox> to HTML inputs, the parent element of the input can pretty much be anything, meaning the check is not as solid. Here’s where the flag is set: https://searchfox.org/mozilla-central/rev/b6f088f2f68d2a8ae0b49d6c8fbd7cbd3a65fa5b/dom/html/HTMLInputElement.cpp#2620 I think it would probably make sense here to either: * instead check that the root element is XUL * decide that we don’t want any special behavior for XUL documents and remove the related code For reference, here’s where the special behavior is implemented: https://searchfox.org/mozilla-central/rev/b6f088f2f68d2a8ae0b49d6c8fbd7cbd3a65fa5b/dom/html/nsTextEditorState.cpp#2330
Bug 1586628 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We’re currently setting this when the parent of the input is a XUL element, which targets very well XUL <textbox> since the input is guaranteed to be a child of a XUL moz-input-box. However, with the recent conversions from <textbox> to HTML inputs, the parent element of the input can pretty much be anything, meaning the check is not as solid. Here’s where the flag is set: https://searchfox.org/mozilla-central/rev/b6f088f2f68d2a8ae0b49d6c8fbd7cbd3a65fa5b/dom/html/HTMLInputElement.cpp#2620 I think it would probably make sense here to either: * instead check that the root element is XUL * decide that we don’t want any special behavior for XUL documents and remove the related code For reference, here’s where the special behavior is implemented: https://searchfox.org/mozilla-central/rev/b6f088f2f68d2a8ae0b49d6c8fbd7cbd3a65fa5b/dom/html/nsTextEditorState.cpp#2330