You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugThis is definitely a bug, meaning it is unintended behavior. It likely needs an ellie and a test.has-ellieThis is a bug and has an ellie which demonstrates it.
If an element is in several states (:hover, :focus, :active), and it contains a set of attributes for each of these states (Element.mouseOver, Element.focused, Element.mouseDown), then one of the conflicting states will be selected randomly.
Steps to reproduce
Several elements are defined in the markup.
Elements use several identical pseudo-classes, for example, Element.mouseOver and Element.mouseDown.
Within the element, pseudo-classes are defined in different order.
Pairs of identical pseudo-classes affect the same attributes with the same values.
The elements will have 100% identical CSS classes, but they will be written to the intermediate stylesheet in a different order, and at the end, duplicates will also be removed. If several conflicting events occur (:hover, :focus, :active) according to CSS rules, the selector defined later will be applied.
Expected behavior
Ideal scenario: each element gets a set of unique classes that are applied in the order they are listed in the attribute list. Alternative scenario: the order of application of pseudo-classes is strictly fixed (:hover < :focus < :active).
Versions
OS: masOS Ventura 13.2.1
Browser: Chrome
Browser Version: 114.0.5735.198
Elm Version: 0.19.1 - latest
Elm UI Version: 1.1.8 - latest
The text was updated successfully, but these errors were encountered:
bugThis is definitely a bug, meaning it is unintended behavior. It likely needs an ellie and a test.has-ellieThis is a bug and has an ellie which demonstrates it.
Bug!
If an element is in several states (
:hover
,:focus
,:active
), and it contains a set of attributes for each of these states (Element.mouseOver
,Element.focused
,Element.mouseDown
), then one of the conflicting states will be selected randomly.Steps to reproduce
Element.mouseOver
andElement.mouseDown
.Ellie example
Causes of the bug
The elements will have 100% identical CSS classes, but they will be written to the intermediate stylesheet in a different order, and at the end, duplicates will also be removed. If several conflicting events occur (
:hover
,:focus
,:active
) according to CSS rules, the selector defined later will be applied.Expected behavior
Ideal scenario: each element gets a set of unique classes that are applied in the order they are listed in the attribute list.
Alternative scenario: the order of application of pseudo-classes is strictly fixed (
:hover
<:focus
<:active
).Versions
The text was updated successfully, but these errors were encountered: