Drop XMLDocument.load() support
Categories
(Core :: DOM: Core & HTML, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: ian, Assigned: ehsan.akhgari)
References
(Blocks 1 open bug)
Details
(4 keywords)
Attachments
(2 files, 1 obsolete file)
![]() |
||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
![]() |
||
Comment 3•19 years ago
|
||
Reporter | ||
Comment 4•19 years ago
|
||
Comment 5•19 years ago
|
||
![]() |
||
Comment 6•19 years ago
|
||
Reporter | ||
Comment 7•19 years ago
|
||
Updated•12 years ago
|
![]() |
||
Comment 9•7 years ago
|
||
Comment 10•7 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 11•6 years ago
|
||
![]() |
||
Comment 12•6 years ago
|
||
![]() |
||
Comment 13•6 years ago
|
||
Assignee | ||
Comment 14•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 15•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 16•6 years ago
|
||
Comment 17•6 years ago
|
||
bugherder |
Assignee | ||
Comment 19•6 years ago
|
||
(In reply to :Ms2ger (he/him; ⌚ UTC+1/+2) from comment #18)
Followup for actual removal, please.
Comment 20•6 years ago
|
||
Assignee | ||
Comment 21•6 years ago
|
||
(In reply to ExE Boss from comment #20)
Thanks for helping with the docs update. Is it possible to avoid publicizing these pref names? They're not really intended for users to set them. They exist for us to be able to set them as part of an emergency hotfix release if it turns out that these changes break an important website.
Thanks!
Comment 22•6 years ago
|
||
(In reply to :Ehsan Akhgari from comment #21)
(In reply to ExE Boss from comment #20)
Thanks for helping with the docs update. Is it possible to avoid publicizing these pref names? They're not really intended for users to set them. They exist for us to be able to set them as part of an emergency hotfix release if it turns out that these changes break an important website.
Thanks!
I’ll leave that decision up to the BCD owners listed in: mdn/browser‑compat‑data#3981 (comment).
Comment 23•6 years ago
|
||
I’ll leave that decision up to the BCD owners listed in: mdn/browser‑compat‑data#3981 (comment).
I'd be perfectly happy with removing the prefs from the compat data. I think it is good to publicize prefs when we are providing an experimental new feature behind a flag that we want devs to activate, play with, provide feedback, etc.
But this is not the case here — this is an old feature that is being disabled by beig put behind a disabled pref, so there is little value in it being played with and turned back on, except by the engineers in the event of a site compat issue.
So Exe-Boss, can you update your BCD PR as appropriate? Thanks.
Comment 24•6 years ago
|
||
(In reply to Chris Mills (Mozilla, MDN editor) [:cmills] from comment #23)
I’ll leave that decision up to the BCD owners listed in: mdn/browser‑compat‑data#3981 (comment).
I'd be perfectly happy with removing the prefs from the compat data. I think it is good to publicize prefs when we are providing an experimental new feature behind a flag that we want devs to activate, play with, provide feedback, etc.
But this is not the case here — this is an old feature that is being disabled by beig put behind a disabled pref, so there is little value in it being played with and turned back on, except by the engineers in the event of a site compat issue.
So ExE Boss, can you update your BCD PR as appropriate? Thanks.
Done in commit mdn/browser‑compat‑data@8905a43
.
Updated•6 years ago
|
Comment 25•6 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2019/xmldocument-load-and-xmldocument-async-have-been-removed/
Updated•6 years ago
|
Comment 26•6 years ago
|
||
Has this been reverted in 68.1 ESR? I found a default pref in my installation: dom.xmldocument.load.enabled = true and dom.xmldocument.async.enabled = true
![]() |
||
Comment 27•6 years ago
|
||
Has this been reverted in 68.1 ESR?
Yes. See bug 1569102.
Description
•