The inspector shows some visible elements as invisible

RESOLVED INVALID

Status

DevTools
Inspector
RESOLVED INVALID
6 years ago
12 days ago

People

(Reporter: Ehsan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

STR:

1. Go to dartlang.org.
2. Use the inspector to highlight the code input area.
3. Expand the tree to find a div with class "db-scroll-x-container".  That div and its children are visible on the screen (they contain the code you see in that area) but the Inspector shows them grayed out.

Comment 1

6 years ago
(In reply to Ehsan Akhgari [:ehsan] from comment #0)
> STR:
> 
> 1. Go to dartlang.org.
> 2. Use the inspector to highlight the code input area.
> 3. Expand the tree to find a div with class "db-scroll-x-container".  That
> div and its children are visible on the screen (they contain the code you
> see in that area) but the Inspector shows them grayed out.

I can't find this node.

Comment 2

6 years ago
Ok - the syntax highlighter script was not loading for some reasons. It works now.

The size of this element is indeed 0x0. Its children are all absolute positioned, so this function:
http://mxr.mozilla.org/mozilla-central/source/browser/devtools/highlighter/domplate.jsm#986
marks them as hidden.

I think we should just revisit this function and just mark an element as hidden if the element is display:none or visibility:collapse.
(Reporter)

Comment 3

6 years ago
s:/visibility:collapse/visibility:hidden/.  Yes, that makes a lot of sense.

Comment 4

6 years ago
(In reply to Paul Rouget [:paul] from comment #2)
> I think we should just revisit this function and just mark an element as
> hidden if the element is display:none or visibility:collapse.

Yeah, I agree.

Comment 5

6 years ago
visibility:collapse AND hidden
Closing as invalid as this is now more than 3 years old and the way the inspector shows hidden nodes has changed completely since then.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID

Updated

12 days ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.