Closed
Bug 110558
Opened 24 years ago
Closed 16 years ago
Some of the unicode characters in 0x4e00 - 0x4eff got display screwed up
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: amyy, Assigned: nhottanscp)
References
()
Details
(Keywords: intl, regression)
Attachments
(2 files)
Reproduce on: 11-16 trunk build, 10-31-08 trunk build
Not reproduce: 10-30-14 trunk build.
Steps to reproduce:
1. Launch browser and go:
http://people.netscape.com/ftang/demo/ncr.cgi?r=0x4&c=0xe
2. You will find some of those characters are display looks like "\" - see
screen shot A.
3. Move the mouse on the top of those characters or move vertical scroll bar up
and down quickly.
4. You will find those characters will change - see screen shot B.
On 10-30-14 trunk build, those characters are display as "?".
Reporter | ||
Comment 1•24 years ago
|
||
Reporter | ||
Comment 2•24 years ago
|
||
Reporter | ||
Updated•24 years ago
|
Keywords: intl,
regression
QA Contact: teruko → ylong
Summary: Some of the unicode characters in 0x4e00 - 0x4eff got display screwed up → Some of the unicode characters in 0x4e00 - 0x4eff got display screwed up
Reporter | ||
Comment 3•24 years ago
|
||
--- roy using ylong's account.
I believe this is related to http://bugzilla.mozilla.org/show_bug.cgi?id=90804
assiging to ftang.
Assignee: yokoyama → ftang
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.8
Comment 4•24 years ago
|
||
It looks it is now fixed by someone else.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 5•24 years ago
|
||
I still see it on 01-03 trunk build on Mac OS X.
Re-open for now...
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Updated•24 years ago
|
Status: REOPENED → ASSIGNED
Comment 7•23 years ago
|
||
nhotta- can you take a look at it?
Assignee: ftang → nhotta
Status: ASSIGNED → NEW
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.9 → mozilla1.0
Assignee | ||
Comment 8•23 years ago
|
||
qawanted, I would like to know if this is a specific problem for that test page
or more generic problem which could happen in other existing pages.
Keywords: qawanted
Comment 9•23 years ago
|
||
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any
questions or feedback about this to adt@netscape.com. You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 10•23 years ago
|
||
I guess there's no font for those chars that show up as \-like glyphs. With the
patch from bug 111728 those chars show up as question marks. When copied to
TextEdit, only Last Resort Unicode range placeholders are displayed.
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.2alpha → ---
Comment 11•16 years ago
|
||
marking wfm because the testcase is gone and the bug doesn't contain enough information without it
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•