When displaying M12 Release Notes in Build 11210, there are several instances of nonbreaking spaces showing up as "nbsp:" This doesn't happen when viewing the M12 release notes in 4.7.

Confirmed in 2000011110 Linux RedHat 6.0. Here's a page that exhibits this behavior (scroll down to the section "Installation Instructions - Win32"): http://www.mozilla.org/projects/seamonkey/release-notes/m12-detail.html#read_this In Mozilla the source code "&nbsp:" displays as "&nbsp:", but in NS4.7 it displays as " :" (a space, then a colon). Note that the source code of this page actually has "&nbsp:" in it, not " " which the page authors presumably intended. Thus this is either a browser parity bug or no bug at all (if Mozilla is not expected to handle this kind of faulty code with the leniency of NS4.7).

Actually, I ran through a little extended test and found that entities such as   " & é à (and presumably all) can be auto-terminated by any ascii punctuation mark *except* for: dash - colon : underscore _ I suspect that this may be related to parser requirements for XML. So, as opposed to letting this linger under nobody@mozilla.org, I'll pass this to someone who would know. harishd : simple question: is the above exclusion of "_:-" from the 'malformed entity' parsing _by_design_? If so ... uh, nevermind :-]. Just close this bug.

Hmmm, although since : and ; are on the same key for typing, mistyping : for ; would be one of the more common typos of  

Adding Vera to the cc: list. She is the author of the release notes. I don't believe anything in her html coding would cause this to happen.

The spec. recommends the use of ';' but does not enforce it. Therefore, Nav.4.x behavior seems to be acceptable. Could be a legit bug after all.

When I was first alerted to this (several weeks ago), I checked my HTML thinking it would be a simple correction. I could not find any places where I had made such a typo. Now I do see them in the code, which seems pretty mysterious. I'll made the correction and update the release notes, but I do wonder what's going on here. Also, this problem doesn't occur when the release notes are displayed via the 4.x browser.

Fixed by makeing ';' optional [ per spec ] in entities.

tested, marking verified (win95_