Summary: | Support HTML5 :in-range and :out-of-range CSS selectors | ||
---|---|---|---|
Product: | WebKit | Reporter: | Peter Kasting <pkasting> |
Component: | Forms | Assignee: | Kent Tamura <tkent> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Enhancement | CC: | adele, Justin, mike, pkasting, tkent, webmaster |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#suffering-from-an-underflow | ||
Bug Depends on: | 28934, 29069, 29070, 29071 | ||
Bug Blocks: | 19264, 24703 |
Description
Peter Kasting
2009-07-20 11:41:56 PDT
On http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#rules-for-parsing-floating-point-number-values there's the algorithm to parse element's value and check whether or not it's a float number value. Is that somehow already implemented? (In reply to comment #1) > On > http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#rules-for-parsing-floating-point-number-values > there's the algorithm to parse element's value and check whether or not it's a > float number value. > > Is that somehow already implemented? WTF::strtod() in JavaScriptCore/wtf/dtoa.h might be useful. (In reply to comment #2) > WTF::strtod() in JavaScriptCore/wtf/dtoa.h might be useful. Thanks man, it's a good starting point. I'll split this bug into 3. They will be: - min/max and ValidityState.rangeOverflow rangeUnderflow support for type=number - ditto for date&time types - :in-range and :out-of-range CSS selectors Kent, did anything ever happen on this? (In reply to comment #5) > Kent, did anything ever happen on this? min/max attribute support was done. The remaining is :out-of-range and :in-range CSS selectors. It's easy to implement but my priority for it is low. OK, updating title. |