Skip to main content

Bug Tracker

Side navigation

#2037 closed bug (fixed)

Opened December 11, 2007 06:39AM UTC

Closed February 06, 2008 05:18AM UTC

Last modified March 15, 2012 07:28PM UTC

using innerHTML can cause css display errors in Opera

Reported by: davidserduke Owned by:
Priority: minor Milestone: 1.2.2
Component: core Version: 1.2.1
Keywords: opera display innerHTML Cc:
Blocked by: Blocking:

There are times when setting innerHTML can cause the css display value to be incorrect in Opera. This is a rather convoluted issue and one specific case has been identified and is shown in the attached test case.

Basically, when a div structure like this exists

<style type="text/css">
  #hid { display:none; }
<div id="container" style="display:none;">
    <div id="hid">hidden</div>

and you set the innerHTML (yes you set it to itself):

$("#container")[0].innerHTML = $("#container")[0].innerHTML;

it can cause the display value from .css() to give improper results on the inner div. In this case, #hid should be display:none but instead it returns display:block.

There are many things that appear to be required so far to cause the bug including the #container div must be display:none or an ancestor must be. There must be a div between the #container and the #hid. The #hid must be display:none through a cascade in the stylesheet and cannot be style="display:none;". And, of course, it only happens in Opera. There may be other criteria or cases too but this is the only one I've found so far.

Interestingly there is a way to fix it as well by doing

var elem = $("#hid")[0];
var save =; = "block"; = save;

Clearly this should just set the display to block then immediately reset to the original value. It has the consequence of "fixing" the Opera problem though such that the .css() value becomes "none" again as it should be.

No one has reported this bug in a real-life instance. It was found in the test suite which is constantly reseting the innerHTML of the test area thus giving the problem a chance to surface which it did. At this time it is not clear what the best fix is so we are opening a ticket for it.

Attachments (3)
  • 2037.diff (0.5 KB) - added by davidserduke December 17, 2007 01:14AM UTC.


  • jquery_test.html (1.5 KB) - added by davidserduke December 11, 2007 06:42AM UTC.

    test case

  • opera-performance-fix.diff (0.6 KB) - added by Junyor February 04, 2008 04:02PM UTC.

    Alternative fix

Change History (6)

Changed December 17, 2007 02:03AM UTC by davidserduke comment:1

resolution: → fixed
status: newclosed

Fixed in [4196].

Changed January 31, 2008 12:05AM UTC by dvessel comment:2

resolution: fixed
status: closedreopened

Hello, I'm coming from Drupal and we are trying to get jQuery 1.2.3 in before release. I tracked a major slowdown in two instances do to this change. It's triggered when .offset() is used.

Would there be another way to fix this problem without the performance hit? This affects Opera 9.2.5 in both Mac and Windows.

Changed February 04, 2008 04:02PM UTC by Junyor comment:3

I've attached an alternative patch that fixes the reported issue and avoids the performance problems seen in Drupal 6.

Changed February 04, 2008 04:05PM UTC by Junyor comment:4

The fix was found by David Bloom ( with help from fearphage (

Changed February 04, 2008 09:13PM UTC by Junyor comment:5

Note: Opera's bug is fixed in Kestrel (AKA Opera 9.5), so the work-around won't be necessary there. However, the work-around I proposed should cause no performance problems.

Changed February 06, 2008 05:18AM UTC by john comment:6

resolution: → fixed
status: reopenedclosed

Fixed in SVN rev [4660].