:active state is not removed when clicking on a pseudo element

NEW
Unassigned

Status

()

Core
Event Handling
4 years ago
4 years ago

People

(Reporter: Kyle Evans, Unassigned)

Tracking

30 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8442221 [details]
index.html

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243

Steps to reproduce:

The :active state on a parent element is not removed after clicking on a pseudo element that is attached to a child element.

Steps to reproduce:
1) Create a parent element with the an active :before pseudo element with "content: '';" property.
2) Set the background color to the parent element to red when :active
3) Create a child element with a :before pseudo element.
4) Click on the pseudo element attached to the child.



Actual results:

The background remains red after clicking.  The :active state is not being removed.


Expected results:

The red background should be removed.  The :active state should no longer apply to the element.
(Reporter)

Comment 1

4 years ago
Potential workaround:

Removing the "content: '';" from the :before pseudo element attached to the outermost element fixes the issue.  I get the impression however that the 'content' property is for some reason required.  It's either required for some browsers or there's a large number of sites with a superfluous "content: '';" property on pseudo elements.
(Reporter)

Comment 2

4 years ago
Sorry my previous workaround while works is entirely useless because omitting the "content" property altogether makes the pseudo element on the outer element not exist at all.
(Reporter)

Updated

4 years ago
Component: Untriaged → Layout: View Rendering
Product: Firefox → Core
The issue is presumably that entering the :active state reframes in this case (due to the bug:active:before rule), and then we end up not existing it correctly in the ESM....
Status: UNCONFIRMED → NEW
Component: Layout: View Rendering → Event Handling
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.