Open Bug 771565 Opened 12 years ago Updated 2 years ago

Setting or removing a class that triggers an :after selector on a parent of a SELECT element on focus breaks interaction.

Categories

(Core :: Layout: Form Controls, defect)

Product:
Core
Component:
Layout: Form Controls
Version:
13 Branch
Platform:
x86_64
Windows 7
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: bergius, Unassigned)

Details

(Whiteboard: DUPEME) 

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
Build ID: 20120614114901

Steps to reproduce:

http://jsfiddle.net/bergius/8uHe4/2/

A container contains a SELECT. On SELECT focus, I set a class on the container. An :after selector is applied.

See the fiddle for an example. It contains some additional logic that helps demonstrate the issue.


Actual results:

The SELECT is closed (appears to not open at all, but applying the class after a delay shows that the selector causes it to close when applied).


Expected results:

The SELECT's state should not be affected by the CSS.
Component: Untriaged → DOM: CSS Object Model
Product: Firefox → Core
What happens is that the select opens but then the entire rendering object is recreated, and the open state is not preserved.
Component: DOM: CSS Object Model → Layout: Form Controls
Whiteboard: DUPEME
Summary: Setting or removing a class that triggers an :after selector on a SELECT element on focus breaks interaction. → Setting or removing a class that triggers an :after selector on a parent of a SELECT element on focus breaks interaction.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.