138120 - [RR/RCF]elements flagged as .style.display = "none"; not staying hidden [inline]

Status: RESOLVED FIXED

(Core :: CSS Parsing and Computation, defect)

Description

[David Snyder]

This bug was originally reported in 111363, then marked as a duplicate of the
recently resolved 99344.

Scott Stevenson's original testcase in 111363 no longer exhibits this bug - but
the original bug still shows up on my website.

I have made an effort to chop out as much as my code as I can.  Elements are
created using the createElement/appendChild.  This stripped code is uploaded
appended to this bug.

To see the bug, mouse over both items, you'll see they simply change color as
they should.  Next, click on one of them, now click on the other one.  Now move
your mouse on the deselected item - the "Printer Friendly" text will be shown. 
This should ONLY appear when the item is selected/clicked!

One way to break the bug is to not set the DIV style.display attribute as "none"
on creation (line 54).

Comment 1

[David Snyder]

Attachment: Sample code that shows the bug

This is some sample code that triggers the bug.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

One guess is that this could be the result of failure to remove content from the
undisplayed map when it is displayed.  See bug 136728.  That's just a guess, though.

Comment 3

[David Snyder]

Just ran my testcase out with the latest nightly on my Linux box (RedHat 7.2)
and the problem exists here as well.

Maybe a chance the bugs are related as you said. *shrug*

Thanks all!  If there is anything more I can provide or do to help let me know.

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This testcase triggers the assertions about neither a frame nor an undisplayed
map entry in the patch ofr bug 136704.

Comment 5

[Scott Gifford (old account)]

This bug also seems to manifest itself in:

    http://www.northern.ca/projects/xspell/XSpellClient.html

Comment 6

[Boris Zbarsky [:bzbarsky]]

Patch in bug 158230 fixes this!

Comment 7

[Boris Zbarsky [:bzbarsky]]

Fixed by fix to bug 158230

Comment 8

[Boris Zbarsky [:bzbarsky]]

David, you may want to keep an eye on bug 171830.  I'm making sure that that
patch does not break this testcase, but if you have any more complicated inline
style tests I'd love to be pointed at them...