Crash involving position:absolute <html:div> in XUL document

RESOLVED WORKSFORME

Status

()

--
critical
RESOLVED WORKSFORME
13 years ago
9 years ago

People

(Reporter: also, Unassigned)

Tracking

({crash})

Trunk
x86
Windows 2000
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051109 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051109 Firefox/1.6a1

XUL:
<window id="XXX"
	xmlns:html="http://www.w3.org/1999/xhtml"
	xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">

<html:div id="TESTID">?</html:div>

</window>

CSS:
#TESTID
{	display:none;
	position:absolute;
}

JS:
	obj=document.getElementById("TESTID");
	obj.style.display="block";

crash


Reproducible: Always
Do you have a Talkback ID for the crash?
Assignee: nobody → general
Component: General → DOM: Level 0
Keywords: crash
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → Trunk
(Reporter)

Comment 2

13 years ago
(In reply to comment #1)
> Do you have a Talkback ID for the crash?
> 

I don't know what's a Talkback ID.
Firefox opens a dialog with:
---
firefox.exe has generated errors and will be closed by Windows.
....
An error log is being created.
---
I don't even find the error_log or any information where it should be.
It is not in the program environment nor in my users_env.

Comment 3

13 years ago
Will probably be fixed by the fix for bug 253479.
Depends on: 253479
Summary: <html:div id="TESTID">?</html:div> → Crash involving position:absolute <html:div> in XUL document
Please test again now bug 253479 is fixed. Please test with 20051221 trunk
builds or later.
Assignee: general → nobody
QA Contact: ian → general

Comment 5

9 years ago
Is this still valid?
No, probably fixed by bug 253479.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.