Closed Bug 32541 Opened 24 years ago Closed 24 years ago

"ASSERTION: Failed to update state" when scrolling

Categories

(Core :: XUL, defect, P1)

Product:
Core
Component:
XUL
Platform:
All
Linux
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: akkzilla, Assigned: saari)

Details

In the 3/20 debug build, I see the following assertion whenever I scroll down
(by dragging the scrollbar) in the editor:

###!!! ASSERTION: Failed to update state: 'NS_SUCCEEDED(rv)', file /builds/fri/m

nsInterfaceState::UpdateParagraphState is failing to find anchorNodeBlockParent
in the !isBlock case.
Turns out this code is Charley's.
Assignee: akkana → cmanske
Target Milestone: --- → M15
Something is really messed up! The root of the problem is that clicking on 
the scrollbar is pulling focus away from the editor window or changing
our selection to something very bad.
The "anchorNode" of the selection when the assertion occurs is a "XULElement"!
Assignee: cmanske → evaughan
Severity: normal → blocker
Component: Editor → XP Toolkit/Widgets
Hardware: PC → All
Ah, then it's probably related to the bug saari is working on.
Is this you saari?
Assignee: evaughan → saari
mjudge fixed scrollbars to not steal selection, but they may still be stealing 
focus, although I don't see that. Bryner is seeing things to support that with 
some of the nsEventStateManager variables, but I havn't looked into it deeply 
enough to verify yet.

I don't think the assertion in this bug has anything to do with me though.

The assertion is mine, but it's a side-effect of some problem with the 
scrollbars; see cmanske's comment above.

Hyatt and myself found something that may explain this; scrollbars got rearranged 
to be generated via XBL. When that happened, the syle rules for user-focus: 
ignore got out of synch, so the scrollbar could grab focus depending on where you 
clicked on it. As soon as Hyatt gets landing clearance from the Gecko tower, I'll 
update this bug.
Status: NEW → ASSIGNED
Priority: P3 → P1
Mass-moving most M15 bugs to M16
Target Milestone: M15 → M16
The change is in, are we still seeing the assertion?

I don't see the assertion in my current linux build with editor or any text
areas, so I'm going to mark it fixed. I'm pretty sure the style changes fixed this.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified in 4/11 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.