Closed Bug 633207 Opened 13 years ago Closed 13 years ago

Implement the progress element enough to ship


(Core :: DOM: Core & HTML, defect)

Not set



Tracking Status
firefox6 - ---


(Reporter: mounir, Assigned: mounir)




(Keywords: html5, meta)

      No description provided.
Depends on: 633209
Depends on: 568825
Depends on: 633913
You can try the <progress> element with a preview build here:

Note that you might have rendering weirdness on MacOS X and Windows.
Depends on: 634086
Depends on: 634088
Depends on: 634549
Depends on: 634551
Keywords: html5
Depends on: 638176
Depends on: 638540
Depends on: 640953
Depends on: 641517
Depends on: 641905
Depends on: 641942
Depends on: 642127
Depends on: 642667
Depends on: 644361
Depends on: 559773
Build with working implementation for <progress> (only horizontal progress bars) can be found here:
All patches except the support of vertical progress bars are ready to be landed. Should I proceed and (maybe) ship without vertical progress bars support or should I wait for that?
I do not believe it really matters given that Opera do not support vertical progress bars (last I've check) and Webkit did support it but do not seem to support it anymore (mentions have been removed from the doc and I can't have it working anymore).
Actually, even if we want to have vertical support, I would prefer to land what we have and disable it if needed.

I'm not sure what's the procedure here. Do I have to ask for a green light?
If other browsers are shipping without it, it sounds perfectly reasonable to do the same.  It won't worsen the fact that authors have to consider that authors will have to consider what happens on browsers that support <progress> but don't support the vertical orientation.
Depends on: 655313
Depends on: 655960
Depends on: 656909
IIRC, new features should use a tracking flag.
Blocks: 658963
Depends on: 661113
No longer depends on: 640953
Closed: 13 years ago
Keywords: meta
Resolution: --- → FIXED
Target Milestone: --- → mozilla6
Depends on: 686913
You need to log in before you can comment on or make changes to this bug.