This has been bugging me for a while now too! In particular, I am really annoyed to see some of the newer input types not as widely supported as I they should be. For example, the date type is still not supported by Firefox (which seems incredibly odd to me since Firefox has often been one of the fore-runners of new web standards—at least in my memory). Instead of being able to use that input type and have it function across all major browsers with sane defaults (even with different styling), you must use a giant pile of JavaScript (read: jQuery) to get something consistent and usable.
I often find myself lamenting the current state of affairs with the Web and how I would much rather modern web development focus on different things that they seem to be¹, but even that the current predominant paradigm differes from my preferences is far less a problem than when the infrastructure itself does not actually allow me to develop the way I would like (i.e., to create a fast, simple, ubiquitous experience for any of the people that might see fit to use/read something that I make/post).
An admirable sentiment, but the new input types are the work of the WHATWG, not the W3C. You can tell them apart because WHATWG are slightly less evil, and don’t, for instance, put DRM in HTML.
That kind of threw me off too, because when she says that, I actually imagine this: a future with <better-input>, <better-better-input>, and <better-better-input-final-342>.
In practice this wouldn’t be a thing. Web components would be more in line with a stylesheet “link” tag to import some components, and it would be called <react-input> or something similar. So you’d have whatever version you were importing, and someone looking at the source would have to figure out which version you were referring to. It’s an odd indirection, but it’s also how widgets in current windowing systems tend to work as well.
This has been bugging me for a while now too! In particular, I am really annoyed to see some of the newer input types not as widely supported as I they should be. For example, the date type is still not supported by Firefox (which seems incredibly odd to me since Firefox has often been one of the fore-runners of new web standards—at least in my memory). Instead of being able to use that input type and have it function across all major browsers with sane defaults (even with different styling), you must use a giant pile of JavaScript (read: jQuery) to get something consistent and usable.
I often find myself lamenting the current state of affairs with the Web and how I would much rather modern web development focus on different things that they seem to be¹, but even that the current predominant paradigm differes from my preferences is far less a problem than when the infrastructure itself does not actually allow me to develop the way I would like (i.e., to create a fast, simple, ubiquitous experience for any of the people that might see fit to use/read something that I make/post).
whew. Felt good to get that off my chest. </rant>
1 http://www.youtube.com/watch?v=r38al1w-h4k
Yes, it has been quite a long time… :( In any case, you can follow the bug for updates on this. There’s been some progress on it recently.
Yep, I’ve been following it for some time now; I have just had to avoid looking at the timestamps since they make me so sad…
In case others wish to share my agony:
Reported: 2012-12-28 11:45 PSTTechnically Firefox DOES support the date type, just in Mobile though…
And still some people are amazed that I abjure the W3C and reject all their Earthly works.
An admirable sentiment, but the new input types are the work of the WHATWG, not the W3C. You can tell them apart because WHATWG are slightly less evil, and don’t, for instance, put DRM in HTML.
I’m happy to throw that particular baby out with the bathwater.
“Now imagine the future where Web Components are supported natively, and someone else is allowed to write a <better-input>”
is this line with the real value of the web? seems like unwarranted complexity. i wonder whether the author liked gears.
That kind of threw me off too, because when she says that, I actually imagine this: a future with
<better-input>,<better-better-input>, and<better-better-input-final-342>.In practice this wouldn’t be a thing. Web components would be more in line with a stylesheet “link” tag to import some components, and it would be called
<react-input>or something similar. So you’d have whatever version you were importing, and someone looking at the source would have to figure out which version you were referring to. It’s an odd indirection, but it’s also how widgets in current windowing systems tend to work as well.