Beginning on October 25th, 2016, Persona will no longer be an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 5723 - parser strip out Unicode U+xx00 from html attribute
: parser strip out Unicode U+xx00 from html attribute
Product: Core
Classification: Components
Component: HTML: Parser (show other bugs)
: Trunk
: All All
: P3 major (vote)
: M7
Assigned To: rickg
: gem
: Andrew Overholt [:overholt]
Depends on:
Blocks: 7228
  Show dependency treegraph
Reported: 1999-04-29 14:01 PDT by Frank Tang
Modified: 1999-06-16 05:05 PDT (History)
3 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description Frank Tang 1999-04-29 14:01:28 PDT
I find this problem when I try to fix the form submission for non ISO-8859-1
character set.
1. Select "View:Default Character Set" to "Shift_JIS"
2. Set a break point in SetAttribute function (static) in nsHTMLContentSink.cpp
3. Go to the above url.
4. You will find out all those ALTTEXT which should have 4 characters only have
two characters. All the characters in U+xx00 (for example U+6700 ) are strip off
by Tokenizer.

Note: you don't need to use Japanese system or even install Japanese font to
debug this. Just look at your debugger

I have one time trace back to parser code, and I am sure the problem is in the
parser. Maybe tokenizer.

all the U+xx00 characters have problem. Not sure about other characters.
Comment 1 Frank Tang 1999-04-30 15:01:59 PDT
change priority to p2.
Comment 2 rickg 1999-04-30 15:56:59 PDT
This is a legitimate bug, and is fixed with nsString2. As soon as that becomes
the defacto string, this will go away.
Comment 3 rickg 1999-05-14 16:05:59 PDT
Handing this back to you to keep track of. See my earlier comments.
Comment 4 bobj 1999-05-14 16:24:59 PDT
Rick said he will land nsString2 shortly after M6, so moving this to M7.

Rick, if you provide QA with an nsString2 enabled binary, maybe they can see
if this really fixes the problem.
Comment 5 Frank Tang 1999-06-01 22:40:59 PDT
It is fixed in this case. Reassign it back to rickg but mark it fix
Comment 6 gem 1999-06-16 05:05:59 PDT

Note You need to log in before you can comment on or make changes to this bug.