(In reply to Alessandro Castellani (:aleca) from comment #11) > * When interacting with the input the console returns: `JavaScript error: chrome://global/content/elements/textbox.js, line 93: TypeError: input is null` https://searchfox.org/mozilla-central/source/toolkit/content/widgets/textbox.js#224-229 Seems like the child input needs the `.textbox-input` class for this._input to be defined. > Any approximate timeline for when `<moz-input-box>` item will be removed? > I'd like to avoid working on a fix that won't last long. Whenever someone has time to work on bug 1586591, I'm not in a good position to know when this will be though. But honestly, even if it gets removed from m-c, this is a custom element you should be able to port over to comm-central easily.
Bug 1586743 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Alessandro Castellani (:aleca) from comment #11) > * When interacting with the input the console returns: `JavaScript error: chrome://global/content/elements/textbox.js, line 93: TypeError: input is null` https://searchfox.org/mozilla-central/source/toolkit/content/widgets/textbox.js#224-229 Seems like the child input needs the `.textbox-input` class for this._input to be defined. Not sure if that fixes the two other issues, but you might want to try that first ? > Any approximate timeline for when `<moz-input-box>` item will be removed? > I'd like to avoid working on a fix that won't last long. Whenever someone has time to work on bug 1586591, I'm not in a good position to know when this will be though. But honestly, even if it gets removed from m-c, this is a custom element you should be able to port over to comm-central easily.