Closed Bug 302462 Opened 19 years ago Closed 19 years ago

Support :valid, :invalid, :out-of-range, and :in-range pseudoclasses

Categories

(Core :: CSS Parsing and Computation, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: allan, Assigned: allan)

References

()

Details

(Keywords: css3, fixed1.8)

Attachments

(2 files, 3 obsolete files)

In bug 271720 there was an agreement on:
"So should we just have valid/in-range always be true and invalid/out-of-range
false for HTML elements?  And leave an XXX: for whoever implements Web Forms in
the future?"
(https://bugzilla.mozilla.org/show_bug.cgi?id=271720#c75)
Status: NEW → ASSIGNED
Attached patch Patch (obsolete) — Splinter Review
Here's a patch that implements the above, but I just looked at CSS3UI again,
and it actually says:
"An element that lacks data range limits or is not a form control is neither
:in-range nor :out-of-range."

?
Attachment #190818 - Flags: review?(bzbarsky)
Yeah, that's what dbaron said in bug 271720 as well.
(In reply to comment #2)
> Yeah, that's what dbaron said in bug 271720 as well.

Yes, aparently I cannot read... so what's the plan? Should we just add them to
CSS, so we can use them in XForms?
That sounds like the best plan for now, yes.
Attachment #190818 - Attachment is obsolete: true
Attachment #190818 - Flags: review?(bzbarsky)
Attached patch Patch wo HTML handling (obsolete) — Splinter Review
(In reply to comment #4)
> That sounds like the best plan for now, yes.

Ok, here's a patch for that then.
Attachment #190929 - Flags: superreview+
Attachment #190929 - Flags: review+
Attached patch Updated to current cvs (obsolete) — Splinter Review
Attachment #190929 - Attachment is obsolete: true
Attachment #194358 - Flags: review-
Attachment #194358 - Attachment is obsolete: true
Attachment #194359 - Flags: superreview?(bzbarsky)
Attachment #194359 - Flags: review?(bzbarsky)
Attachment #194359 - Flags: superreview?(bzbarsky)
Attachment #194359 - Flags: review?(bzbarsky)
Attached patch oh mySplinter Review
Attachment #194360 - Flags: superreview?(bzbarsky)
Attachment #194360 - Flags: review?(bzbarsky)
Attachment #194360 - Flags: superreview?(bzbarsky)
Attachment #194360 - Flags: superreview+
Attachment #194360 - Flags: review?(bzbarsky)
Attachment #194360 - Flags: review+
Fixed for 1.9a
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Attachment #194360 - Flags: approval1.8b4?
Comment on attachment 194360 [details] [diff] [review]
oh my

Too close to beta1 - will have to wait until the next release.
Attachment #194360 - Flags: approval1.8b4? → approval1.8b4-
(In reply to comment #10)
> (From update of attachment 194360 [details] [diff] [review] [edit])
> Too close to beta1 - will have to wait until the next release.	 
> 

Next release, as in 2006/2007?  Or next beta as in October?
For what it's worth, this is a very very safe patch.  If this is badly needed by
XForms, I would be quite comfortable taking this after beta1.
We would really like this, and have customers who have requested pseudo classes.
Flags: blocking1.8b5?
Comment on attachment 194360 [details] [diff] [review]
oh my

setting the approval request for doron (I think he's requesting approval to
land in beta2.)
Attachment #194360 - Flags: approval1.8b5?
Attachment #194360 - Flags: approval1.8b5? → approval1.8b5+
Flags: blocking1.8b5? → blocking1.8b5+
checked into branch (forgot to add r=/a= in the comment, oops)
Keywords: fixed1.8
Keywords: qawanted
Blocks: selectors3
No longer blocks: selectors3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: