Closed
Bug 6659
Opened 26 years ago
Closed 25 years ago
character entities do not display in window titles
Categories
(Core :: DOM: HTML Parser, defect, P3)
Core
DOM: HTML Parser
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: cpratt, Assigned: rickg)
References
()
Details
Attachments
(1 file)
127 bytes,
text/html
|
Details |
build id: 1999051708
platform: windows nt
if you view the following html in apprunner, you just get a lot of "&&;" in the
window title where the characters are supposed to be:
<html>
<head><title>This contains ßä€ a few weird
characters</title></head>
<body></body>
</html>
Expected result: you see the proper characters instead of "&&;".
I just tried this on Mac and Windows and both display the text properly if the
characters are in the body but both display garbage if the &euro is in the title
string. The problem also occurs in viewer so it is either a parser or widget bug.
Reassiging to the widget module owner
Updated•26 years ago
|
Assignee: karnaze → rickg
Comment 3•26 years ago
|
||
This is not a form control widget problem. I'm not sure who owns nsBrowserWindow
(or equavalent) these days. Rick, please reassign as appropriate.
Sorry I picked the wrong component. I ment to select "xp toolkit/widget" who I
assume owns nsWindowMac/Win/GTK. Lets try again
Updated•26 years ago
|
Assignee: trudelle → danm
Comment 5•26 years ago
|
||
reassigning to danm
Comment 8•25 years ago
|
||
I've checked 1999-07-30-11 on win98 and it doesn't display as &&; but
it isn't correct eighter.
The effect is different with view source.
(That was bug 9283 now marked as duplicate)
E.g.:
<title>Entitás teszt</title>
in browser window:
Entitá;s teszt - Mozilla
in view source window:
EntitMozilla
Comment 9•25 years ago
|
||
I didn't pull the source, I'm just surfing it with lxr (which rulez btw).
It looks like there's a bug in SkippedContent collection.
It is used at other places too, like the plaintext or xmp tag, so
<xmp>entitás</xmp>
is displayed as
entitá;s
(the extra ; is there)
Comment 10•25 years ago
|
||
I forgot to say I got the above hint from
http://lxr.mozilla.org/seamonkey/source/htmlparser/src/CNavDTD.cpp
see also:
http://lxr.mozilla.org/seamonkey/search?string=SkippedContent
So this should be a _parser_ bug.
Please (re)assign it accordingly.
Reporter | ||
Comment 11•25 years ago
|
||
Assignee: danm → rickg
Status: ASSIGNED → NEW
Component: XP Toolkit/Widgets → Parser
OS: Windows NT → All
Hardware: PC → All
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 12•25 years ago
|
||
Fixed rather than deferred, since it was such a brain-dead bug. The entity
handling code recently changed, where the ending semi was no longer removed. The
skipped content code was never told about it. Oops. Fixing this was accomplished
by removing 1 line of code.
Comment 13•25 years ago
|
||
big favour: can you verify, chris?
Reporter | ||
Comment 14•25 years ago
|
||
Verified using the '1999070614' build (actually an August 13, 1999 build) on
Windows 98. phillip, it's fixed on Linux, yes?
You need to log in
before you can comment on or make changes to this bug.
Description
•