Remove support for XUL <editor> element
Categories
(Toolkit :: UI Widgets, task, P2)
Tracking
()
People
(Reporter: ntim, Unassigned)
References
(Blocks 1 open bug)
Details
Looks unused:
https://searchfox.org/mozilla-central/search?q=%3Ceditor&case=false®exp=false&path=
https://searchfox.org/mozilla-central/search?q=create.*Element.*%5C%28.*%22editor®exp=true&path=
Platform code:
https://searchfox.org/mozilla-central/search?q=nsGkAtoms%3A%3Aeditor&case=false®exp=false&path=
https://searchfox.org/mozilla-central/source/toolkit/content/widgets/editor.js
https://searchfox.org/mozilla-central/search?q=%3Ceditor&case=false®exp=false&path=test
https://searchfox.org/mozilla-central/rev/2a355e56c490768be676689de18629485c9d699b/xpcom/ds/StaticAtoms.py#398
For comm-central, I think using Looks like this will need porting the MozEditor CE to be ported, and the platform code to be kept or the MozEditor CE could potentially extend browser/iframe. This doesn't look trivial to port, so I guess it could be held off for now.<iframe>
instead should work.
Comment 1•5 years ago
|
||
Anything in particular that made you change your mind about <iframe> being a direct alternative?
Reporter | ||
Comment 2•5 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #1)
Anything in particular that made you change your mind about <iframe> being a direct alternative?
Editor is bound to a custom element: https://searchfox.org/mozilla-central/source/toolkit/content/widgets/editor.js
Iframe isn't. Also, there's some differences in terms of focus behaviour on the platform side.
I think you could try making editor a XUL <iframe is="editor-frame"> or <browser is="editor-browser"> and then port the CE to comm-central with the CE extending XULFrameElement.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•