Closed
Bug 309445
Opened 19 years ago
Closed 19 years ago
Crash when dynamically adding position:fixed to xforms:action [@ nsSpaceManager::GetTranslation]
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Assigned: aaronr)
References
()
Details
(Keywords: testcase)
Attachments
(2 files)
See upcoming testcase.
It crashes current Mozilla trunk build with current trunk xforms.xpi installed,
for me when hovering over the text.
Reporter | ||
Comment 1•19 years ago
|
||
Talkback ID's I got: TB9572905Z and TB9572903M
Reporter | ||
Updated•19 years ago
|
Comment 2•19 years ago
|
||
Probably related to XTF.
We (I?) should convert xf:action to use XBL.
Reporter | ||
Comment 3•19 years ago
|
||
From talkback ID's:
nsSVGPointList::GetValueString
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/svg/content/src/nsSVGPointList.cpp,
line 235]
nsBlockFrame::Destroy
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/generic/nsBlockFrame.cpp,
line 291]
nsAbsoluteContainingBlock::IncrementalReflow
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/generic/nsAbsoluteContainingBlock.cpp,
line 387]
nsAbsoluteContainingBlock::ReflowingAbsolutesOnly
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/generic/nsAbsoluteContainingBlock.cpp,
line 242]
nsRootBoxFrame::QueryInterface
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsRootBoxFrame.cpp,
line 338]
IncrementalReflow::~IncrementalReflow
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/base/nsPresShell.cpp,
line 817]
PresShell::ProcessReflowCommands
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/base/nsPresShell.cpp,
line 6618]
PresShell::HandleDOMEventWithTarget
[c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/base/nsPresShell.cpp,
line 6267]
0x778b0c24
Comment 4•19 years ago
|
||
(In reply to comment #2)
> Probably related to XTF.
> We (I?) should convert xf:action to use XBL.
Why does the action element have any visual representation at all? I mean why do
we create a div for it?
Updated•19 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
(In reply to comment #4)
> (In reply to comment #2)
> > Probably related to XTF.
> > We (I?) should convert xf:action to use XBL.
>
> Why does the action element have any visual representation at all? I mean why do
> we create a div for it?
Put in by Olli as part of the xf:message implementation:
https://bugzilla.mozilla.org/show_bug.cgi?id=269428. Message manages its own
DIV w/o using this one, though.
Comment 6•19 years ago
|
||
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > Probably related to XTF.
> > > We (I?) should convert xf:action to use XBL.
> >
> > Why does the action element have any visual representation at all? I mean why do
> > we create a div for it?
>
> Put in by Olli as part of the xf:message implementation:
> https://bugzilla.mozilla.org/show_bug.cgi?id=269428. Message manages its own
> DIV w/o using this one, though.
Olli?
Comment 7•19 years ago
|
||
Updated•19 years ago
|
Summary: Crash when dynamically adding position:fixed to xforms:action → Crash when dynamically adding position:fixed to xforms:action [@ nsSpaceManager::GetTranslation]
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #2)
> > > > Probably related to XTF.
> > > > We (I?) should convert xf:action to use XBL.
> > >
> > > Why does the action element have any visual representation at all? I mean why do
> > > we create a div for it?
> >
> > Put in by Olli as part of the xf:message implementation:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=269428. Message manages its own
> > DIV w/o using this one, though.
>
> Olli?
Put in for hint, I believe.
Reporter | ||
Comment 9•19 years ago
|
||
Testcase doesn't crash anymore, marking WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•