Open
Bug 1401793
Opened 7 years ago
Updated 2 years ago
XML pretty print viewer is too easily disabled by extensions
Categories
(Core :: XML, defect, P5)
Core
XML
Tracking
()
REOPENED
People
(Reporter: mkaply, Unassigned)
References
Details
If you have this extension installed: https://addons.mozilla.org/en-US/firefox/addon/check-this-by-metacert/?src=userprofile When you navigate to an XML file, it comes up blank instead of displaying the XML tree view. For instance: https://aus5.mozilla.org/update/6/Firefox/54.0.1/20170628075643/WINNT_x86-msvc-x64/en-US/release/Windows_NT%2010.0.0.0%20(x64)(noBug1296630v1)(nowebsense)/SSE3/default/default/update.xml I don't see any obvious errors on the console.
Updated•7 years ago
|
Component: WebExtensions: General → Add-ons
Product: Toolkit → Tech Evangelism
This bug and its duplicates have bounced between different components from XML to WebExtensions to Tech Evangelism but I think it is very much an XML issue. Extension content scripts are injected into XML pages by design and ideally extension authors would be more mindful of that but a lot of them will fail to test there so ultimately it falls back on the XML pretty printer to be more robust. Chrome's XML pretty printer is harder to disable than Firefox's, for example changing the style of elements via class attribute does not disable it while Firefox does. A similar story can be seen in Bug 1404933 Comment #0: > This bug[1] affects the Vimium-ff[2] extension, since we have to inject HTML > into the active document to show our UI. Note that this works as expected in > Chrome. Improving the compatibility of pretty print would go a long way to avoiding most issues with extensions. Also interesting to note that Firefox's Inspector only shows the root element while Chrome shows the full pretty print HTML source.
Component: Add-ons → XML
Product: Tech Evangelism → Core
Summary: MetaCert extension breaks the display of XML files → XML pretty print viewer is too easily disabled by extensions
Updated•7 years ago
|
Priority: -- → P5
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Comment 8•6 years ago
|
||
May I know why this is dup'd to bug 1437956? We simply change the technology to put the pretty print DOM; we will still opt out of it when DOM changes.
Flags: needinfo?(kmaglione+bmo)
Updated•6 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•6 years ago
|
Flags: needinfo?(kmaglione+bmo)
Comment 10•5 years ago
|
||
I think this is fixed with bug 1605657. Or at least it is fixed for LastPass. FF 74.0b4 works fine with LastPass enabled.
Example URL that didn't work in 73 and works in 74:
http://data.bn.org.pl/oai/bibs?verb=ListIdentifiers&metadataPrefix=marc21&from=2019-11-01T00:00:00Z&until=2019-12-10T00:00:00Z
Flags: needinfo?(mozilla)
Reporter | ||
Comment 11•5 years ago
|
||
I just tried with the latest nightly and this bug can still be recreated. Install the above extension and navigate to the XML and it is blank.
Flags: needinfo?(mozilla)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•