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

error viewing xml files #393

Open
rbro opened this issue Jan 31, 2022 · 2 comments
Open

error viewing xml files #393

rbro opened this issue Jan 31, 2022 · 2 comments

Comments

@rbro
Copy link

rbro commented Jan 31, 2022

I am running into an issue where if I have Livemarks enabled, if I try viewing certain xml files, Firefox flags them as invalid xml even though they are valid. I am running Firefox 96.0.3 and Livemarks 3.4.

I'm not able to share the xml files, but I've been trying to narrow it down to something reproducible. Please let me know if the below helps, or if there is something I can do locally to try to help narrow it down:

  • the problem only happens accessing the xml file over http or https. It doesn't happen if I drag the xml file into Firefox and view it locally.
  • it's intermittent in that if I keep refreshing the same URL, Firefox will render the xml file sometimes and other times flag it as invalid (with differing reasons).
  • if I disable Livemarks, then the issue doesn't occur.

When it happens, Firefox displays an error like:

Location: https://server/test/test.xml
Line Number 1644, Column 7:

------^

or

Location: https://server/test/test.xml
Line Number 124, Column 19:
      <Category>N</Categction>N</Section>
-------------------

In the last example, I don't have a node called "Categction" in my file. It's almost like it combined parts of the "Category" and "Section" names into the same node.

Thanks for any help you can provide.

@evilpie
Copy link
Collaborator

evilpie commented Jan 31, 2022

I would suggest you disable the Feed preview feature. Go to the addon options page. Click on "More options" and disable feed preview.

@rbro
Copy link
Author

rbro commented Jan 31, 2022

Yes, that fixed it - thanks!

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

No branches or pull requests

2 participants