Bold/unbold highlighted text leaves screen debris

VERIFIED WORKSFORME

Status

()

P3
normal
VERIFIED WORKSFORME
19 years ago
17 years ago

People

(Reporter: gerv, Assigned: cmanske)

Tracking

Trunk
x86
Windows 95
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

From Bugzilla Helper:
User-Agent: Mozilla/4.7 [en] (Win95; U)
BuildID:    2000-03-17

If you add some text and bold and then unbold it when it is selected, the end of 
the bold text remains in the "gap" between the boldened length and the 
unboldened length.

Reproducible: Always
Steps to Reproduce:
1. Open Composer
2. Debug | Insert Text
3. Select all text with the mouse
4. Press the B toolbar button twice
5. Look at the end of the relevant line. 

Actual Results:  There is screen debris left by the longer bold form of the 
text. It is repainting the area the text occupies after unboldening, rather than 
before.

Expected Results:  Unboldened correctly; text remains selected.

Doesn't happen if text is italicised.

Only happens if selection goes to end of line.

Comment 1

19 years ago
I don't see this on Macintosh.  Has it been fixed?  Can anyone reproduce this?
I can reproduce on 2000032108 W95.

Gerv

Comment 3

19 years ago
Charley--Can you look into this? Not sure if it's our bug or a view manager bug or ?
Assignee: brade → cmanske
Target Milestone: --- → M15
(Assignee)

Comment 4

19 years ago
This is a layout repaint problem. After changing the line from bold to normal,
the frame is reduced in size, but the rect that comprises the difference 
between the old frame and new frame is not repainted. We are doing
straightforward DOM node manipulation to remove the <b> node.
Note that this is a perfectly good test case -- we don't have time to figure
out scripts for viewer.exe this late in the game.
Assignee: cmanske → troy

Comment 5

19 years ago
This is ridiculous. I have no idea what set of DOM operations the editor is 
doing, and trying to debug this without a simple test case is like trying to 
find a needle in a hay stack
Assignee: troy → cmanske
(Assignee)

Comment 6

19 years ago
Created attachment 7142 [details]
Simple JS example of removing a bold attribute node
(Assignee)

Comment 7

19 years ago
Troy: It is obviously reasonable to ask for debugging help, like were to put
break points, etc. I've supplied a test case anyway, although
I don't see the problem happening in today's build, but I'll keep it open for
a couple of days to make sure it's really dead.
(Assignee)

Comment 8

19 years ago
This has been working ok for the past 3 days, so let's close it
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WORKSFORME

Comment 9

19 years ago
verified in 4/4 build.
Status: RESOLVED → VERIFIED
Reopening, as this is still broken in 2000-04-16.

Gerv
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---

Updated

19 years ago
Target Milestone: M15 → M16
(Assignee)

Comment 11

19 years ago
I don't see any problem in my 4/19 debug build.
Sujay, Akkana, and Kathy: do you see any problem?
Target Milestone: M16 → M17

Comment 12

19 years ago
I don't see this bug in today's debug build on Linux.
Nope, it's fixed again as of 20000419 (though it's broke in M15). Marking 
WORKSFORME again.

Gerv
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago19 years ago
Resolution: --- → WORKSFORME

Comment 14

19 years ago
verified in 4/20 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.