WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 3 years ago

#14771 closed enhancement (duplicate)

WP Administration as HTML5

Reported by: sc0ttkclark Owned by: mitchoyoshitaka
Milestone: Priority: normal
Severity: minor Version: 3.1
Component: Administration Keywords: has-patch
Focuses: Cc:

Description

The default theme is HTML5, shouldn't we be moving that direction with the WP Admin area?

Attachments (1)

14771.diff (13.4 KB) - added by mitchoyoshitaka 3 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 filosofo4 years ago

HTML 5 is a working draft, not yet a standard. It's one thing to take risks and be trendy with a theme, which can easily be changed; it's another to do so with the admin, which cannot.

comment:2 demetris4 years ago

  • Cc dkikizas@… added
  • Keywords html5 removed
  • Type changed from feature request to enhancement

@filosofo:

The parts we would use if we made the switch now are already stable.

Doctype:

<!DOCTYPE html>

Charset declaration:

<meta charset="CHARSET_GOES_HERE" />

(This sort declaration worked long before HTML5 came along, which is what made possible the recommendation.)

Less verbose SCRIPT and STYLE elements. E.g.:

<script src="/js/script.js"></script>

and

<style>h1,h2,h3 {color: red;}</style>

We could also get rid of the CDATA notation, unless we need it for more than just XHTML validation. (Do we? I have no idea.)

A switch along these lines is not fancy, in my opinion, or risky. And it has some benefits, even if we do not start using advanced HTML5 stuff right now: a) a bit cleaner code; b) slightly smaller files; and c) readiness for when we want to start using the really fancy stuff in HTML5.

comment:3 follow-up: sc0ttkclark4 years ago

Also, the entire plugin / theme dev community can begin using HTML5 in their backend management if they choose to do so with this change, even if WP itself doesn't utilize HTML5 specifically.

comment:4 in reply to: ↑ 3 filosofo4 years ago

Replying to sc0ttkclark:

Also, the entire plugin / theme dev community can begin using HTML5 in their backend management if they choose to do so with this change, even if WP itself doesn't utilize HTML5 specifically.

Well, that's why need to go all the way or not do it at all. If for example, we don't include that JS hack to get IE to recognize the new elements, every single plugin author will be adding her own version.

comment:5 sc0ttkclark4 years ago

Currently, no plugins / themes can use HTML5 elements if they choose to, and with the major players of the industry backing HTML5 and already using it, it makes sense to at the very least allow plugin / theme devs to use it too. This doesn't mean we have to use HTML5 in the UI at all, just allow for it to be used.

comment:6 sc0ttkclark3 years ago

  • Version changed from 3.0.1 to 3.1

Anyone opposed to adding some sort of filter here to be able to enable HTML5 via a plugin then if not modified directly in core for all page loads?

comment:7 sc0ttkclark3 years ago

Unless I'm mistaken, after further research it appears HTML5 can be used under the XHTML 1.0 doc type as long as the browser supports it - it won't validate but that wouldn't be too much of a problem in WP-Admin.

In the future, as HTML5 becomes used more mainstream an additional HTML5 JS could be included. I'll leave this ticket open, if someone can put it as 'Future Release' milestone that'd be appreciated.

comment:8 nacin3 years ago

  • Milestone changed from Awaiting Review to Future Release

mitchoyoshitaka3 years ago

comment:9 follow-up: mitchoyoshitaka3 years ago

  • Cc mitcho@… added
  • Component changed from UI to Administration
  • Keywords has-patch added
  • Owner set to mitchoyoshitaka
  • Severity changed from major to minor
  • Status changed from new to accepted

7 months have passed and I think the time to do this is here. <!DOCTYPE html> triggers standards mode on all modern browsers we support and it validates.

I advocate pushing this 3.3-early.

comment:10 in reply to: ↑ 9 ramoonus3 years ago

Replying to mitchoyoshitaka:

7 months have passed and I think the time to do this is here. <!DOCTYPE html> triggers standards mode on all modern browsers we support and it validates.

I advocate pushing this 3.3-early.

not every WP user uses the latest browser

comment:11 SergeyBiryukov3 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.