Closed Bug 1202433 Opened 9 years ago Closed 9 years ago

Inspector doesn't display ::before and ::after pseudoelements if they are set to elements with pseudoclass

Categories

(DevTools :: Inspector, defect)

defect
Not set
normal

Tracking

(firefox43 affected)

RESOLVED DUPLICATE of bug 1034110
Tracking Status
firefox43 --- affected

People

(Reporter: arni2033, Unassigned)

References

()

Details

(Whiteboard: DUPEME)

Attachments

(1 file)

STR_1:   (Win7_64, Nightly 43, 32bit, ID 20150905030205, new profile, safe mode)
1. Open this "data:" url or URL from the form above
data:text/html,<style>div{ height:100px; width:100px; background:gray; } div:hover::after{ content: "after_pseudoelement"; }</style><div><span>
2. Open devtools->Inspector, click <body> element
3. Expand <body> element's children list, expand <div> element's children list
4. Hover mouse over gray square on the page

Result:       No "::after" child of <div> element in markup-view
Expectations: Markup-view should display the pseudoelement as <div> element's child

STR_2
1. Open this "data:" url or URL from the form above
data:text/html,<style>div{ height:100px; width:100px; background:gray; } div:hover::after{ content: "after_pseudoelement"; }</style><div><span>
2. Hover mouse over gray square on the page
3. Right-click gray square [don't move mouse]
4. Use Up and Down keys to select menuitem "Inspect Element"
5. Wait for Inspector to load and then move mouse out of the gray area

Result:       Markup-view displays the pseudoelement as <div> element's child
Expectations: Markup-view shouldn't display the pseudoelement
We unfortunately don't yet have events on the markup-view backend that tells us when pseudo-elements are created or removed.
Brian, could you confirm this bug report is related to this? Should it be closed as duplicate?
Flags: needinfo?(bgrinstead)
(In reply to Patrick Brosset [:pbrosset] [:pbro] from comment #1)
> We unfortunately don't yet have events on the markup-view backend that tells
> us when pseudo-elements are created or removed.
> Brian, could you confirm this bug report is related to this? Should it be
> closed as duplicate?

Yes, this would also be fixed by Bug 1034110.  The problem is we don't get a normal MutationObserver event for the ::after element being created / destroyed.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(bgrinstead)
Resolution: --- → DUPLICATE
Has STR: --- → yes
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: