Closed
Bug 284228
Opened 20 years ago
Closed 19 years ago
Crash with absolute positioning of link toolbar [@ nsHTMLReflowState::CalculateHypotheticalBox() ]
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 253479
People
(Reporter: xanthor+bz, Unassigned)
References
Details
(Keywords: crash)
Crash Data
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b) Gecko/20050217
Mozilla crashes when trying to display the link toolbar which has been
absolute-positioned with userChrome.css
Reproducible: Always
Steps to Reproduce:
1. Write in your userChrome.css :
#linktoolbar {position : absolute; bottom : 15px}
or
#linktoolbar>.toolbar-holder {position : absolute; bottom : 15px}
2. Launch Mozilla
3. View > Show Hide > Site Navigation Bar > Show Always
Actual Results:
Crash
Expected Results:
I don't know really (about the position of the link toolbar), but no crash.
TB3694875E TB3985745K TB3968035E TB3968067K
Tested with different themes.
(I wrote those CSS in order to put the linktoolbar at the bottom of the page. If
someone know how to do so, or to put it in the status bar like with the Fx
extension, or in the top like in attachment 138618 [details], please tell me ;¬])
Comment 1•20 years ago
|
||
TB3694875E (other stacks look similar):
nsHTMLReflowState::CalculateHypotheticalBox()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsHTMLReflowState.cpp,
line 609]
nsHTMLReflowState::InitAbsoluteConstraints()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsHTMLReflowState.cpp,
line 987]
nsHTMLReflowState::InitConstraints()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsHTMLReflowState.cpp,
line 1853]
nsHTMLReflowState::Init()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsHTMLReflowState.cpp,
line 337]
nsHTMLReflowState::nsHTMLReflowState()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsHTMLReflowState.cpp,
line 263]
nsFrame::BoxReflow()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsFrame.cpp,
line 5302]
nsFrame::RefreshSizeCache()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsFrame.cpp,
line 4868]
nsFrame::GetAscent()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsFrame.cpp,
line 5075]
nsSprocketLayout::GetAscent()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsSprocketLayout.cpp,
line 1551]
nsBoxFrame::GetAscent()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsBoxFrame.cpp,
line 848]
nsSprocketLayout::Layout()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsSprocketLayout.cpp,
line 260]
nsBoxFrame::DoLayout()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsBoxFrame.cpp,
line 87]
nsIFrame::Layout()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsBox.cpp,
line 803]
nsStackLayout::Layout()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsStackLayout.cpp,
line 667]
nsBoxFrame::DoLayout()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsBoxFrame.cpp,
line 87]
nsIFrame::Layout()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsBox.cpp,
line 803]
nsBoxFrame::Reflow()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsBoxFrame.cpp,
line 853]
nsRootBoxFrame::Reflow()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/xul/base/src/nsRootBoxFrame.cpp,
line 239]
nsContainerFrame::ReflowChild()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsContainerFrame.cpp,
line 966]
ViewportFrame::Reflow()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/generic/nsViewportFrame.cpp,
line 251]
IncrementalReflow::Dispatch()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/base/nsPresShell.cpp,
line 52]
PresShell::ProcessReflowCommands()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/base/nsPresShell.cpp,
line 6250]
ReflowEvent::HandleEvent()
HandlePLEvent()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/layout/base/nsPresShell.cpp,
line 6100]
PL_HandleEvent()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/threads/plevent.c,
line 698]
PL_ProcessPendingEvents()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/threads/plevent.c,
line 633]
nsEventQueueImpl::ProcessPendingEvents()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/threads/nsEventQueue.cpp,
line 417]
libwidget_gtk.so + 0xbd75 (0x410fbd75)
libwidget_gtk.so + 0xb92d (0x410fb92d)
libglib-1.2.so.0 + 0xea56 (0x403c9a56)
libglib-1.2.so.0 + 0x1003d (0x403cb03d)
libglib-1.2.so.0 + 0x104f4 (0x403cb4f4)
libglib-1.2.so.0 + 0x10724 (0x403cb724)
libgtk-1.2.so.0 + 0xa025f (0x402d825f)
libwidget_gtk.so + 0xbf16 (0x410fbf16)
nsAppStartup::Run()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp,
line 208]
main1()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1301]
main()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1814]
libc.so.6 + 0x15dc6 (0x404f1dc6)
Bug 253479 has same signature - maybe is related, but it's filled for fixed
position.
Severity: normal → critical
Keywords: crash
Summary: Crash with absolute positioning of link toolbar → Crash with absolute positioning of link toolbar [@ nsHTMLReflowState::CalculateHypotheticalBox() ]
Comment 2•20 years ago
|
||
Yep, same issue. Positioning is not supported in XUL, basically. Marking
dependent for now, but I suspect a fix for bug 253479 will fix this one too.
Depends on: 253479
Updated•20 years ago
|
Version: unspecified → Trunk
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Reporter | ||
Comment 4•19 years ago
|
||
Still crashes with SeaMonkey 1.0a
Comment 5•19 years ago
|
||
Please test again now bug 253479 is fixed. Please test with 20051221 trunk builds or later.
Comment 6•19 years ago
|
||
Xanthor, is this still an issue?
Reporter | ||
Comment 7•19 years ago
|
||
Sorry !
It's fixed.
Verified with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060319 SeaMonkey/1.5a
Thanks ;¬)
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
*** This bug has been marked as a duplicate of 253479 ***
Resolution: FIXED → DUPLICATE
Updated•13 years ago
|
Crash Signature: [@ nsHTMLReflowState::CalculateHypotheticalBox() ]
You need to log in
before you can comment on or make changes to this bug.
Description
•