Opening xml files in palemoon

[thosrtanner]

I have an (admittedly rather largish) xml file that I tried to open in palemoon (and firefox) and it complains there's an error in the file. It is possibly triggered by this sequence

<playLists xmlns="http://www.mozilla.org/keymaster/gateke ... s.only.xul">

as the character position stated in the error is just at the end of that.

I've tried the same file in internet explorer, microsoft edge and on several validators and they can find nothing wrong with it.

Is there something wrong with that, or is Palemoon treating it specially?

[Moonchild]

Most likely: You're defining the name space as XUL, so Pale Moon will expect XUL compatible XML code. <playList> is not a valid XUL tag.

More info would be helpful (e.g. the file in question, and why you're trying to define it as XUL...)

[thosrtanner]

I have no idea why it's being defined as xul. It's an export of the xml configuration of the inforss extension, and I'm not altogether sure why some values are set the way they are... I take it that that xmlns bit is not a very good idea?

[adesh]

I have no idea why it's being defined as xul. It's an export of the xml configuration of the inforss extension, and I'm not altogether sure why some values are set the way they are... I take it that that xmlns bit is not a very good idea?

XUL is used to define UI for extensions for Firefox-like browsers including Pale Moon. Namespace (xmlns bit) tells what all tags you can use in your XML file. Since XUL has a special meaning for Firefox / Pale Moon, they are treating it specially and resulting in error. Internet Explorer knows absolutely nothing about XUL and hence it displays it as it is.

Problems aside, may I know what benefint are you expecting by opening it in a browser. You can't do much with XML files in a browser anyway, so it just might be better to open it in your favourite text editor.

[thosrtanner]

Problems aside, may I know what benefint are you expecting by opening it in a browser. You can't do much with XML files in a browser anyway, so it just might be better to open it in your favourite text editor.

Because the browser indents and line breaks, so the xml is more or less readable. My editor gives you what it is given which is a 32,000+ character line.

[thosrtanner]

Hmm. It appears that document.createElement is putting in the namespace, and then when the xml is being serialised it's being output. But I'm not sure how it's getting the namespace in there right now.

Addendum: Fixed the element creation