Closed
Bug 615475
Opened 15 years ago
Closed 15 years ago
Crash [@ nsTextFrame::GetTrimmedOffsets] [@ GetTrimmableWhitespaceCount] with a11y, text wrapping
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
mozilla2.0b11
Tracking | Status | |
---|---|---|
blocking2.0 | --- | final+ |
People
(Reporter: jruderman, Assigned: surkov)
References
Details
(Keywords: crash, testcase, Whiteboard: [softblocker])
Crash Data
Attachments
(2 files)
1. Enable accessibility, e.g. by pasting the following into the js console:
Components
.classes["@mozilla.org/accessibilityService;1"]
.getService(Components.interfaces.nsIAccessibleRetrieval);
2. Load the testcase.
Result: Crash [@ GetTrimmableWhitespaceCount]
Reporter | ||
Comment 1•15 years ago
|
||
Reporter | ||
Comment 2•15 years ago
|
||
bp-ca88219e-68f1-4dd8-ad4e-baf512101129 [@ nsTextFrame::GetTrimmedOffsets]
Summary: Crash [@ GetTrimmableWhitespaceCount] with a11y, text wrapping → Crash [@ nsTextFrame::GetTrimmedOffsets] [@ GetTrimmableWhitespaceCount] with a11y, text wrapping
Reporter | ||
Comment 3•15 years ago
|
||
This may account for a topcrash, bug 612098.
Reporter | ||
Updated•15 years ago
|
blocking2.0: --- → ?
Assignee | ||
Comment 4•15 years ago
|
||
(In reply to comment #3)
> This may account for a topcrash, bug 612098.
I think these crashed should go away after bug 498015.
![]() |
||
Updated•15 years ago
|
blocking2.0: ? → final+
![]() |
||
Comment 5•15 years ago
|
||
Feel free to cc Alexander and I on bug 377438 if it will help. I agree regarding bug 498015, and I've bumped the priority there. I think it should be our top priority.
![]() |
||
Updated•15 years ago
|
Assignee: nobody → surkov.alexander
Updated•15 years ago
|
Whiteboard: [softblocker]
![]() |
||
Comment 6•15 years ago
|
||
Fixed via bug 498015?
Assignee | ||
Comment 7•15 years ago
|
||
(In reply to comment #6)
> Fixed via bug 498015?
no
![]() |
||
Comment 8•15 years ago
|
||
I wonder if there is some way to detect when it is unsafe for nsCSSFrameConstructor::ContentRemoved to call into us?
![]() |
||
Comment 9•15 years ago
|
||
(Or when it is unsafe for us to get rendered text)
Assignee | ||
Comment 10•15 years ago
|
||
I think a11y should cache rendered text instead
1) we can be sure AT won't call us when unsafe what may result in crashes like this
2) it allows us to make correct the text change events
![]() |
||
Comment 11•15 years ago
|
||
Yes.
Jamie, how crucial is it that you get the text for text remove events?
![]() |
||
Comment 12•15 years ago
|
||
(In reply to comment #10)
> I think a11y should cache rendered text instead
You filed bug 626660 for this right?
Depends on: 626660
Assignee | ||
Comment 13•15 years ago
|
||
(In reply to comment #12)
> (In reply to comment #10)
> > I think a11y should cache rendered text instead
>
> You filed bug 626660 for this right?
Correct
Assignee | ||
Comment 14•15 years ago
|
||
fixed by bug 630001 part1.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b11
Updated•14 years ago
|
Crash Signature: [@ nsTextFrame::GetTrimmedOffsets]
[@ GetTrimmableWhitespaceCount]
You need to log in
before you can comment on or make changes to this bug.
Description
•