Open
Bug 1455565
Opened 6 years ago
Updated 2 years ago
Alias ::-webkit-progress-value to ::-moz-progress-bar
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Core
CSS Parsing and Computation
Tracking
()
NEW
Webcompat Priority | P3 |
People
(Reporter: e7358d9c, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webcompat:revisit])
The two pseudo-elements seem to do essentially the same thing, and since we’re now implementing some -webkit- prefixed features for webcompat, this seems like it should be somewhat easy to do. ## Documentation on MDN: - https://developer.mozilla.org/docs/Web/CSS/::-moz-progress-bar - https://developer.mozilla.org/docs/Web/CSS/::-webkit-progress-value
Comment 1•6 years ago
|
||
I think we should only implement this if we know there are compat issues from not having it, and only then once it's been added to the Compat spec.
Comment 2•6 years ago
|
||
(In reply to Cameron McCormack (:heycam) from comment #1) > I think we should only implement this if we know there are compat issues > from not having it, and only then once it's been added to the Compat spec. Agree. This hasn't come up for us yet (that we know about anyways).
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Flags: webcompat?
Updated•5 years ago
|
Whiteboard: [webcompat:revisit]
Comment 3•5 years ago
|
||
See bug 1547409. Moving webcompat whiteboard tags to project flags.
Webcompat Priority: --- → ?
Webcompat Priority: ? → revisit
Updated•5 years ago
|
Flags: webcompat?
Updated•5 years ago
|
Updated•2 years ago
|
Webcompat Priority: revisit → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•