Closed
Bug 143656
Opened 22 years ago
Closed 21 years ago
[branch only]cut a longer exchange from firstChild.nodeValue
Categories
(Core :: Layout, defect, P4)
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: l0rd, Assigned: attinasi)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 In the page at http://members.tripod.de/ngtestpage/test.html I use firstChild.nodeValue. If I exchange the value by JavaScript of the div and the string was longer than the string before then the string was not complete displayed, it's so long than the string before. Reproducible: Always Steps to Reproduce: 1.exchange value with firstChild.nodeValue 2. 3. Actual Results: If I exchange the value of the div and the string was longer than the string before then the string was not complete displayed, it's so long than the string before. Expected Results: The exchanged value should displayed in the right width.
Comment 1•22 years ago
|
||
worksforme, linux trunk build 2002-05-10-21. I see the 5-character nodeValues render correctly.... Does this problem happen with rc2?
Comment 2•22 years ago
|
||
OK, confirmed that the trunk works fine but the branch gets this wrong... Over to layout -- the DOM is doing the right thing, since you can see the leftmost pixels of the other chars.
Assignee: jst → attinasi
Status: UNCONFIRMED → NEW
Component: DOM Content Models → Layout
Ever confirmed: true
QA Contact: desale → petersen
Summary: cut a longer exchange from firstChild.nodeValue → [branch only]cut a longer exchange from firstChild.nodeValue
Updated•22 years ago
|
Priority: -- → P4
Target Milestone: --- → Future
Comment 4•21 years ago
|
||
1.0 branch is basically dead; once 1.4 ships it _will_ be dead. wontfix, since the trunk is fine.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•