Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tampermonkey broke Firefox's built in XML document viewer again #1609

Closed
grumble0 opened this issue Oct 5, 2022 · 6 comments
Closed

Tampermonkey broke Firefox's built in XML document viewer again #1609

grumble0 opened this issue Oct 5, 2022 · 6 comments

Comments

@grumble0
Copy link

grumble0 commented Oct 5, 2022

Go to https://www.w3schools.com/xml/cd_catalog.xml

Expected Behavior

XML files opened in Firefox should display the XML contents. For the cd_catalog.xml example, should display a page that starts with (not possible to show styling in github):

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<CATALOG>
<CD>
<TITLE>Empire Burlesque</TITLE>
<ARTIST>Bob Dylan</ARTIST>
<COUNTRY>USA</COUNTRY>
<COMPANY>Columbia</COMPANY>
<PRICE>10.90</PRICE>
<YEAR>1985</YEAR>
</CD>
<CD>
<TITLE>Hide your heart</TITLE>
<ARTIST>Bonnie Tyler</ARTIST>

Actual Behavior

XML tags are stripped and only the element contents are displayed. For the cd_catalog.xml example the page starts with:

Empire Burlesque Bob Dylan USA Columbia 10.90 1985 Hide your heart Bonnie Tyler

Specifications

Firefox 105.0.2
TM v4.18.0

Script

No scripts required.

Notes

Perhaps similar to #1480 although the sandbox mode workaround there does not work for this issue.
Downgrading to TM v4.17.6161 fixes the issue.

@derjanb
Copy link
Member

derjanb commented Oct 5, 2022

although the sandbox mode workaround there does not work for this issue

Have you saved the settings after switching to "JavaScript+DOM" or "Force JavaScript" mode?

@grumble0
Copy link
Author

grumble0 commented Oct 5, 2022

although the sandbox mode workaround there does not work for this issue

Have you saved the settings after switching to "JavaScript+DOM" or "Force JavaScript" mode?

No! Sorry, I didn't see the Save button at the bottom of each section. I expected any Save button to be at the top or bottom of the page, didn't see one, so assumed the setting was applied immediately.

Retested with saving... these Sandbox modes fix the bug:

  • Force JavaScript
  • JavaScript+DOM
  • Force DOM

@derjanb
Copy link
Member

derjanb commented Oct 5, 2022

No problem.

Closing as duplicate of #1480

@derjanb derjanb closed this as completed Oct 5, 2022
@Kyogre
Copy link

Kyogre commented Jun 6, 2023

Same for wsdl links in v4.18.1. Setting Sandbox Mode to JavaScript+DOM in advanced config mode fixed the problem.

@derjanb
Copy link
Member

derjanb commented Jun 6, 2023

Can you point me to a wsdl link?

Maybe fixed in 4.19.0 which is in review since 13 days.

@Kyogre
Copy link

Kyogre commented Jun 6, 2023

Yeah, it is successfully fixed in beta 4.19 with default sandbox. I already tested. I just realized that inside wsdl page there is just xml scheme 😉
Example wsdl link.
Other examples here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants