Practically speaking, what you're saying isn't true. I'm able to set type="range", and jQueyr's able to detect that attribute on document.ready (in all browsers). It doesn't automatically fall back, before I have a chance to do something about it.
-- Yehuda
On 10/6/06, Klaus Hartl <[EMAIL PROTECTED]> wrote:
Jörn Zaefferer schrieb:
> Yehuda Katz schrieb:
>> I've developed (or partially developed) a new plugin that implements
>> webform2's slider. Specifically, you can do stuff like <input
>> type="range" step="1" min="1" max="10" value="1" id="a" /> and jQuery
>> will automatically convert it into a stylable range widget.
> Does the slider put its current value back into the input? I couldn't
> quite figure it out by looking at the code. It's an interesting aspect
> when thinking about integration with both form and validation plugins.
>
> Building widgets and validation according to the Webforms2 spec seems
> like the best excuse around for invalid html... :-)
Bah. Even adapting the DTD has no use (and I haven't seen anyone since
doing web developing who actually did this). If browsers do not support
it, what's the use? With an unknown type a browser falls back to the
default type="text", so better use it in the first place and think about
Webforms2 when its time to, in another 2 years or so...
Although I think it's always good to be aware of new standards, when
meeting governmental guidelines for accessibility sites simply have to
be compliant (valid).
-- Klaus
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
--
Yehuda Katz
Web Developer | Wycats Designs
(ph) 718.877.1325
_______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
