Add a pseudo-class to access indeterminate <progress> elements

RESOLVED FIXED in mozilla6

Status

()

Core
DOM: Core & HTML
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: mounir, Assigned: mounir)

Tracking

({dev-doc-complete, html5})

Trunk
mozilla6
dev-doc-complete, html5
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

7 years ago
According to the specs, a progress element can be indeterminate. It might be interesting to let the authors access indeterminate progress elements given that they might want to style them differently.
(Assignee)

Comment 1

7 years ago
Created attachment 512129 [details] [diff] [review]
Patch v1
Attachment #512129 - Flags: review?(jonas)
For what it's worth, this is going to conflict with the various patches in bug 	313351, and bug 598833.  I can handle merging if this lands first, I guess, but just wanted to give you a heads-up.
And wait.  Why do you need that AfterSetAttr gunk?
(Assignee)

Comment 4

7 years ago
(In reply to comment #3)
> And wait.  Why do you need that AfterSetAttr gunk?

Eh, I don't indeed: indeterminate state only depends on one attribute's value. This should make the merge issue smaller. Thanks for the noticing ;)
(Assignee)

Comment 5

7 years ago
Created attachment 512147 [details] [diff] [review]
Patch v1.1

Updated patch. Boris, you won the right to review it :)
Attachment #512129 - Attachment is obsolete: true
Attachment #512147 - Flags: review?(bzbarsky)
Attachment #512129 - Flags: review?(jonas)
Comment on attachment 512147 [details] [diff] [review]
Patch v1.1

s/determinated/determined/ and looks good.  And yeah, now you're only conflicting with code I haven't written yet.  ;)
Attachment #512147 - Flags: review?(bzbarsky) → review+
(Assignee)

Updated

7 years ago
Blocks: 598833
(Assignee)

Updated

7 years ago
Whiteboard: [can land][post-2.0]
(Assignee)

Updated

7 years ago
Whiteboard: [can land][post-2.0]
(Assignee)

Updated

7 years ago
Whiteboard: [ready to land][waits for dependencies]
(Assignee)

Updated

7 years ago
Blocks: 634088
(Assignee)

Comment 7

7 years ago
I wonder if we shouldn't use :-moz-indeterminate instead of :indeterminate here.
(Assignee)

Comment 8

7 years ago
I've open a bug against HTML specs to have it specified:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12210

Though, I should probably send an email somewhere to ask for a better specification of the indeterminate pseudo-class in CSS. I wonder if CSS3-UI couldn't simply override what Selectors say (it doesn't really say anything actually, the only specs is a Note....).
(Assignee)

Comment 9

7 years ago
David, what is your feeling about comment 7? Boris is ok to not prefix it (according to our IRC conversation).
(Assignee)

Comment 10

6 years ago
Pushed:
http://hg.mozilla.org/mozilla-central/rev/89d4c7fd4d0d
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [ready to land][waits for dependencies]
Target Milestone: --- → mozilla6

Updated

6 years ago
Depends on: 655860
Backed out in http://hg.mozilla.org/mozilla-central/rev/dd9ba28d2bd9 to resolve bug 655860.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 12

6 years ago
The regression wasn't caused by these patches. Re-landed:
http://hg.mozilla.org/mozilla-central/rev/91fa0c94e6db
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
I'm ok with unprefixed.
(Assignee)

Updated

6 years ago
No longer depends on: 655860
Documented:

https://developer.mozilla.org/En/CSS/:indeterminate
https://developer.mozilla.org/en/HTML/Element/progress

Also listed on Firefox 6 for developers.
Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.