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)

Product:
Core
Component:
CSS Parsing and Computation
Type:
enhancement

Tracking

()

Project Flags:
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
Depends on: 1265639
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.
(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).
Priority: -- → P3
Flags: webcompat?
Whiteboard: [webcompat:revisit]

See bug 1547409. Moving webcompat whiteboard tags to project flags.

Webcompat Priority: --- → ?
Flags: webcompat?
Webcompat Priority: revisit → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.