Posted by alanburke on August 24, 2010 at 7:52am
Jump to:
| Project: | HTML5 |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
Although this module has been around for longer,
the momentum is currently behind
http://drupal.org/project/html5_tools.
Perhaps this module should be deprecated and efforts continued there.
Alan
Comments
#1
#2
Hi,
After having a quick look at the html5_tools module I see it serving a different purpose to html5 module. This module is more of an effort to enable the base fixes to enable a consistent implementation of html5 across all browsers, whereas html5_tools sees to do this, but also convert as much code to html5 entities where applicable. I think that the two modules cater for different cases.
Also there hasn't actually been a code release for the module as of now, I'll be happy to re-review when this changes.
Thanks!
#3
Hi,
I'm not sure that they are different use cases.
Both modules aim to do the base work to allow a site to be built in HTML5.
This module makes sure older browsers understand the new elements, and
as you've pointed out, HTML 5 tools does this too [via Modernizr or IE Shiv].
HTML5 tools [along with HTML5 base] goes further in trying to do all the foundation work to allow a site be built in HTML5.
There will be a release of both the base theme and module shortly, I hope.
#4
Hi there, just wanted to provide input. For the perspective of a supporter, I'm not sure of the difference either.
Those who want to support HTML5 want to support HTML5 -- I think people who are interested in these module do so because they thing it's the future. I don't think HTML5 enthusiasts are going to make the distinction between "base support" and "support"...
Just my two cents. Thanks :)
#5
...there are now both D6 and D7 versions of HTML5 Tools and a growing base of 130 sites using it. Perhaps its time to rethink this and join forces(?).
#6
Sorry guys. This project is now being used by the official HTML5 Initiative, so this issue is no longer valid. See the project page for more information.