[META] HTML5 for Backdrop

[jenlampton]

We need to triple check that we have all the HTML5 hotness that's in Drupal 8.

Someone will need to review each issue mentioned in the following d.o issues and check the date the patch was committed to D8. If it was before our fork date (Feb 29th, 2012) then we have the change, and nothing else needs to be done. If it was committed after that date, however, then we'll need to include it here to be sure we get the changes.

General HTML5 changes

(http://drupalcode.org/project/drupal.git/commit/ae5cc6f8f40604987274799978e065bd5820d07b) | d.o
(http://drupalcode.org/project/drupal.git/commit/8fd2b4779ec83c3e44a8caac65300b96e3a52ab8) | d.o

• Issue #1468582 by Schnitzel, lewisnyman, dcmouyard, alanburke, tstoeckler, edward_or, janusman: Add mobile friendly meta tags to the html.tpl.php. backdrop#386 | Issue #1468582 by Schnitzel, lewisnyman, dcmouyard, alanburke, tstoeckler, edward_or, janusman: Add mobile friendly meta tags to the html.tpl.php. | bf6a8a1a | d.o
• N/A | Issue #1717090 by BarisW, barraponto: Fixed Remove the http-equiv='cleartype' meta tag. | 94143f22 | d.o
• Issue #1974422 by ericduran: Update to latest html5shiv library. backdrop#222 | Issue #1974422 by ericduran: Update to latest html5shiv library. | 6f2f1b7 | d.o
• Issue #1943142 by jessebeach: Add the main element to the list of HTML5 elements that get set to display block. backdrop#221 | Issue #1943142 by jessebeach: Add the main element to the list of HTML5 elements that get set to display block. | 12df490 | d.o
• N/A | Issue #1436814 by gary4gar, webchick: switch to HTML5 for Fast 404 'Not found' pages. | a2ee8c1 | d.o
• N/A | Refactor block-admin-display-form.tpl.php | d.o
• N/A | add the 'browsers' option to drupal_add_js() | d.o
• N/A | Add a theme_datetime() function to consistently theme dates and datetimes | d.o
• N/A | Add mobile friendly meta tags to the html.tpl.php d.o

Re-factor templates / theme functions to use HTML5 elements

Review this list

• Convert page.tpl.php & maintenance-page.tpl.php to HTML5 backdrop#219 | Convert page.tpl.php & maintenance-page.tpl.php to HTML5 | cc7c70e | d.o
• Issue #1190206 by cosmicdreams: Convert taxonomy-term.html.twig to HTML5... backdrop#213 | Issue #1190206 by cosmicdreams: Convert taxonomy-term.tpl.php to HTML5. | d.o
• N/A | Convert book-all-books-block.tpl.php to HTML5 | d.o
• N/A | Convert book-export-html.tpl.php to HTML5 | d.o
• N/A | Convert book-navigation.tpl.php to HTML5 | d.o
• N/A | Convert book-node-export-html.tpl.php to HTML5 | d.o
• N/A | Convert comment.tpl.php to HTML5 | d.o
• N/A | Convert comment-wrapper.tpl.php to HTML5 | d.o
• N/A | Convert html.tpl.php to HTML5 | d.o
• N/A | Convert node.tpl.php to HTML5 | d.o
• N/A | Convert user-profile.tpl.php to HTML5 | d.o

Themes

• Convert Bartik to HTML5. backdrop#218 | Issue #1179764 by mjohnq3, mbrett5062, tim.plunkett: Convert Bartik to HTML5. | d.o
• Issue #1190206 by cosmicdreams: Convert taxonomy-term.html.twig to HTML5... backdrop#213 | Issue #1913692 by mgifford: Convert Seven to HTML5. | d.o

Form API support for new HTML5 elements

Review this list

• Add HTML 5 elements for number and range backdrop#247 | Issue #1174640 by Niklas Fiekas, aspilicious, ericduran, cosmicdreams, amateescu, tim.plunkett: Added new HTML5 FAPI element: number. | d.o
• Add HTML 5 elements for number and range backdrop#247 | Issue #1174646 by aspilicious, ericduran, Niklas Fiekas: Added new HTML5 FAPI element: range. | d.o
• Add HTML 5 elements for number and range backdrop#247 | Issue #1519720 by Niklas Fiekas: Remove element_validate_integer() and element_validate_integer_positive() in favor of the new number element type. | d.o
• Add HTML 5 elements for number and range backdrop#247 | Issue #1519852 by Niklas Fiekas: Use the new number FAPI element for the number field textfield widget. | 1fd8114 | d.o
• Add HTML 5 elements for number and range backdrop#247 | Issue #1527988 by Niklas Fiekas: Fixed Missing or legacy number validation.[d.o] | 055716f | (http://drupal.org/node/1527988)
• Add new HTML5 FAPI element: search backdrop#242 | Issue #1174628 by Dave Reid, Niklas Fiekas, ericduran, Jacine: Add new HTML5 FAPI element: search. | d.o
• Issue #1445224 by Niklas Fiekas, sun, Tor Arne Thune: Add new HTML5 FAPI element: color. backdrop#308 | Issue #1445224 by Niklas Fiekas, sun, Tor Arne Thune: Add new HTML5 FAPI element: color. | d.o
• Add new HTML5 FAPI element: url backdrop#211 | Issue #1174630 by Dave Reid, Niklas Fiekas, ericduran, xjm: Added new HTML5 FAPI element: url. | d.o
• N/A | Issue #1174620 by Niklas Fiekas, Dave Reid, ericduran: Added new HTML5 FAPI element: email. | d.o
• Fixed Some attributes not allowed for the new HTML5 input elements. backdrop#228 | Issue #1540174 by Niklas Fiekas, attiks: Fixed Some attributes not allowed for the new HTML5 input elements. | 3e88616 | d.o

RELATED ISSUES

• Detials vs Fieldsets: [A11Y] Add the HTML details element to core form API #324
• HTML5 #required [A11Y] Natively support the HTML5 #required property #325
• More HTML5 elements for dates Add more HTML5 elements for dates #326

[quicksketch]

@clickbox filed a PR for the first issue (color elements): backdrop/backdrop#187

The PR looks like a great start, but unfortunately I think the PR won't work because it first depends on adding HTML5 color element, before we add an HTML5 color field. Additionally, this color field wasn't even committed to Drupal 8.

I think we may have linked to the wrong issue in this meta. We linked to https://drupal.org/node/1740438, but it should have been https://drupal.org/node/1445224. Doh! I've fixed the meta list in this issue to point to the right d.o issue.

That issue also gets a bit gnarly since it introduces a new PSR-0 class for "Color", and then it had several followups fixing problems. We might need to make a separate stand-alone issue here to discuss how we want to implement this in Backdrop.

[quicksketch]

Let's go ahead and close this issue out. For the 1.0.0 release, we are already where we want to be. I made a new issue for multiple file uploads (#440), which we can try to wrap up in the 1.1.0 release.