Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I saw this come across twitter today. http://html5reset.org/
The idea is that it's a set of defaults for creating html5 projects. Not unlike what we're trying. I've looked at the code briefly and there seems to be a little more "stuff" in the css than it needs. I'll want to look at it more deeply, but don't have time to tonight so I'm sharing it with you fine folks.
Any thoughts on this? Any bits worth including?
Comments
Comment #1
tim.plunkettI saw this too on twitter, but it was in the context of: "I fear this will do more harm than good in its current state: http://html5reset.org - For instance: reset.css is for XHTML not HTML5 tags." :)
There isn't a single HTML5 element in the CSS. It just includes modernizr.js.
I think a reset could be useful, and this might provide good inspiration, but we'd need to write our own.
Comment #2
jensimmons CreditAttribution: jensimmons commentedOh, you beat me to opening to this issue. :P
I do think we should pick through the code of "HTML5 Reset" and snag any great ideas. It will help us understand how other people are thinking about the semantic markup of the new elements.
I do not think we should include a reset stylesheet in our project. We already decided over here to not include much CSS at all: #864564: How much CSS? or if people want to re-debate including more CSS, including resets, let's do so on the other issue.
To me the reset part of HMTL5Reset.org is useless. And not the interesting part. (Sad choice of name, therefore.)
What we should look at is the *HTML5* part in index.html, and the javascript for making the HMTL5 elements work in IE.
Comment #3
jensimmons CreditAttribution: jensimmons commentedI think this one might be better:
http://html5boilerplate.com/
Comment #4
jensimmons CreditAttribution: jensimmons commentedHere's more on HTML5 Boilerplate:
The Official Guide to HTML5 Boilerplate
http://net.tutsplus.com/tutorials/html-css-techniques/the-official-guide...
Video walkthrough tour by co-creator Paul Irish.
Comment #5
mason@thecodingdesigner.com CreditAttribution: mason@thecodingdesigner.com commentedhtml5 boilerplate most lays out a scaffold and some base css. Some of the items, like jquery and favicons already come from drupal core.
Other items:
meta tags:
- chrome frame: Do we want this? It seems controversial
- set viewport scale properties: I love this, but I think it needs configuration options. Could be a theme setting or part of html5_tools
- apple touch icon: also either a theme setting or part of html5_tools
- modernizr: I do love this, and I know I've said before that it should be a contrib module. However since it needs to add a class to the HTML tag it might fit best in this theme.
Beyond that it has a nice css reset and some good default styles. I don't think we should keep the default styles.
Oh, and there are also some @media query stubs in the css. I don't see any harm in including those.
Comment #6
paul.irish CreditAttribution: paul.irish commentedhi all. :)
regarding chrome frame, the only trick used here is to use chromeframe if it is installed. I think we can safely say the user experience will be better in chrome than IE6-8. Plus the auto-updating will keep those users up to date with great features and fast pages. I highly recommend enabling this.
The more controversial side of chromeframe is prompting users who don't have it installed to install it. (The CFinstall.js) In most cases this is only feasible for sites that are also considering dropping IE6 support. This part I definitely don't recommend for this project.
Comment #7
mason@thecodingdesigner.com CreditAttribution: mason@thecodingdesigner.com commentedThanks for jumping in, Paul. And thanks for clarifying how you're using Chrome frame. It makes sense to use it that way.
I think we should work these features into the theme. I'll take the first pass as it, and try to make many of them options in theme_settings rather than hard code them.
Comment #8
mason@thecodingdesigner.com CreditAttribution: mason@thecodingdesigner.com commentedI just added most of this to the theme. See: http://drupal.org/cvs?commit=419252
Support for modernizr is definitely a "first-draft". Right now it requires a manual download (probably always will) and I've hard-coded the current version in template.php. That will obviously need to change.
There are some other cool bits (conditional stylesheet switching for browser-classed body tags, chrome frame, mobile viewport meta tags) so please check it out help me get this right.
Comment #9
tim.plunkettThat article has been updated, and it makes a little more sense to me. We should probably update as well.
Also,
if (!theme_get_setting('html5_base_modernizr')):should be made a variable in template.php, and the call toprint $modernizr_head;in throws errors because... it doesn't exist.Finally, I don't understand this:
<!--[if IE]><![endif]-->.Comment #10
tim.plunkettOh, I just re-read this article, and I understand the purpose of the empty comment (I still don't understand how it helps).
Ignore that, but the first two issues still stand.
Comment #11
jensimmons CreditAttribution: jensimmons commented