InnerHTML causes infinite iteration

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: jamesl, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-1-30], URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090723 Minefield/3.6a1pre (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090723 Minefield/3.6a1pre (.NET CLR 3.5.30729)

When attempting to set innerHTML on a DOM object, it causes an infinite iteration, leading to the JavaScript stop dialog to appear. Only happens when sending long variables to innerHTML it seems.

Reproducible: Always

Steps to Reproduce:
1.Create a DIV object.
2.Using JavaScript, create a var with a very large set of [li] in a [ul].
3.Using JavaScript, set the innerHTML of the DIV object to the variable.
Actual Results:  
The script finishes successfully, but continues to iterate for no reason.

Expected Results:  
As the actual results, with the iteration ending.

This is a background iteration, as part of innerHTML.
(Reporter)

Comment 1

9 years ago
Forgot to mention, it works in Firefox 3 fine. It seems to be a problem within the latest trunk only.
Does this still happen with 3.6 final or current trunk?
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.