XHTML error

[jmdeldin@…]

Hi,

I've been unable to access the MacPorts website due to the following error in Firefox 3.5 and Safari 4:

XML Parsing Error: not well-formed
Location: http://www.macports.org/
Line Number 19, Column 314:

I think if you change the HTML comments in the script tags to CDATA tags, it'll work:

<script ...>
<![CDATA[
// js
]]>
</script>

Or if the scripts are located in files, it should work too.

[jmdeldin@…]

Cc Me!

[blb@…]

Have you done anything to your browsers, or use a proxy that may change things? ​http://www.macports.org/ loads fine for me in Safari 4.0.2 as well as Firefox (Minefield) 3.6a1pre.

[ryandesign (Ryan Carsten Schmidt)]

​http://www.macports.org/ does not have any script tags that include inline JavaScript code. There are only two script tags, which include mootools.v1.11.js and language.js. What inline JavaScript code do you see in the page, and what do you see at line 19, column 314?

[jmdeldin@…]

Well, this is embarrassing. I force-reloaded in Firefox, and it's fine. I think Firebug might have been responsible for inlining the JS. However, in Safari 4.0.1, I'm getting this error after resetting Safari and emptying the cache:

This page contains the following errors:
error on line 19 at column 314: Comment must not contain '--' (double-hyphen)
Below is a rendering of the page up to the first error.

The XHTML source is ​here, and the JS is inline. I don't have any Safari input managers installed, so I'm not sure what's going on. I don't know - is there a "harder" reset for Safari? I'll see if the 4.0.2 update fixes anything.

Thanks, JM

[tobypeterson]

Going to close this as essentially "doing it wrong" - the page does not have inlined CSS/JS, you've got something wacky in your setup.

[blb@…]

Replying to jmdeldin@…:

The XHTML source is ​here, and the JS is inline. I don't have any Safari input managers installed, so I'm not sure what's going on. I don't know - is there a "harder" reset for Safari? I'll see if the 4.0.2 update fixes anything.

Thanks, JM

Note that if I do a View Source in Safari, the result is much simpler than what you're showing there...

[jmdeldin@…]

Replying to toby@…:

[...] you've got something wacky in your setup.

Agreed. Not sure what, but Firefox is my primary browser, so it's no big deal now that I can access the non-Trac pages.

Thanks for the assistance and sorry about the report.