Closed
Bug 127129
Opened 23 years ago
Closed 23 years ago
The above page is displayed many blank areas
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
FIXED
mozilla1.0
People
(Reporter: amyy, Assigned: shanjian)
References
()
Details
(Keywords: intl, regression)
Attachments
(3 files)
89.88 KB,
image/png
|
Details | |
16.92 KB,
text/html
|
Details | |
1.06 KB,
patch
|
ftang
:
review+
alecf
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
Go to the page: http://law.china.com/zh_cn/zt/alpc/10002958/20020116/10192949.html Many areas are displayed blank in this page. This is a regression problem, it happened sometime between 02-12 and 02-18 trunk build.
Reporter | ||
Comment 1•23 years ago
|
||
-> nsbeta1, regression It happens on both RH7.1JA and 6.2JA.
QA Contact: ruixu → ylong
Reporter | ||
Updated•23 years ago
|
Summary: The page displayed many blank areas in the page above → The above page is displayed many blank areas
Reporter | ||
Comment 2•23 years ago
|
||
Assignee | ||
Comment 3•23 years ago
|
||
The problem does not happen with 2/12 nightly build, but 2/13 build has this problem. reassign to myself. frank, we should nominate this one as nsbeta1+.
Assignee: yokoyama → shanjian
Reporter | ||
Comment 4•23 years ago
|
||
Assignee | ||
Comment 5•23 years ago
|
||
Add brian to cc list.
There is at least one <table> tag with "height" attribute inside. Sothis bug might be a duplicate of bug 126742. Could someone with required fonts installed remove the above attribute and then check if the page renders as expected?
Assignee | ||
Comment 7•23 years ago
|
||
I debugged into the X font code and inside debug everythings runs fine even to the point to DrawString. Analysis of the checkins between 2/12 and 2/13 also seems suggesting that it is not a X font problem. NS_FONT_DEBUG does not reveal anything useful. Since the problem is most likely caused by a patch in other area, and I do not find any clue about which part might be the cause, it is reasonable to me to further check and hopefully identify the problematic checkin.
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•23 years ago
|
||
This is a regression caused by frank's fix for bug 101998. I saw all the character has been converted to unicode correctly in my debug session, that made me belive the patch was irrevant to this problem. I just realized that we need to convert from unicode to GB2312GL before the glyph can be found, and one file touched by 101998 changed the behavior. Patch will follow soon.
Assignee | ||
Comment 9•23 years ago
|
||
Assignee | ||
Comment 10•23 years ago
|
||
frank, could you review my patch? When converting from unicode to GB2312GL, we need to clear 8bit. That is skipped in your patch for 101998.
Comment 12•23 years ago
|
||
Comment on attachment 71551 [details] [diff] [review] patch r=ftang. That make sense
Attachment #71551 -
Flags: review+
Assignee | ||
Comment 13•23 years ago
|
||
alec, could you sr? thanks.
Comment 14•23 years ago
|
||
Comment on attachment 71551 [details] [diff] [review] patch sr=alecf
Attachment #71551 -
Flags: superreview+
Comment 15•23 years ago
|
||
Comment on attachment 71551 [details] [diff] [review] patch a=asa (on behalf of drivers) for checkin to the 1.0 trunk
Attachment #71551 -
Flags: approval+
Assignee | ||
Comment 16•23 years ago
|
||
fix checked in to trunk.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 17•23 years ago
|
||
Verified fixed on 03-06 trunk build / RH7.2.
Status: RESOLVED → VERIFIED
Comment 18•23 years ago
|
||
btw, will the patch be checked in to 0.9.9? this bug doesn't have target milestone set...
Reporter | ||
Comment 20•23 years ago
|
||
*** Bug 130479 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 21•22 years ago
|
||
*** Bug 130001 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 22•22 years ago
|
||
*** Bug 130173 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 23•22 years ago
|
||
*** Bug 138335 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•