-
-
Save darobin/5ce286e635f239c94180 to your computer and use it in GitHub Desktop.
Questions about After 5/WebSpecs
@briandipalma sorry may be unclear, we are just gathering questions to be answered for a future article on http://html5doctor.com
I'd like to see a future version able to handle more common interactions that are currently only achievable using Javascript. Elements like the new input types have already started this process by allowing things like a default date picker for dates.
Possible examples...
- Simple show/hide/toggle (possibly using an attribute in a tag to trigger an action on another tag with matching ID)
- Accordions (expand/collapse one element in a series of elements, maybe using attributes and ID's)
The end result would have a few advantages:
- less reliance on Javascript for basic UI functions
- less page weight
- faster development for both web and HTML5 apps
Just a few thoughts!
Why is the future seen as using a modularity model similar to CSS when the entirety of HTML5 will make it to rec before the vast majority of CSS level 3 specs do, despite the fact that CSS level 3 started first?
where do implementers fit in to this?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Gists are a poor way to communicate I'd put this stuff in a repo, you never get notified of comments on Gists...