[wp-trac] [WordPress Trac] #35372: Post/paging navigation forces use of HTML5

[WordPress Trac]

#35372: Post/paging navigation forces use of HTML5
--------------------------+-----------------------
 Reporter:  bizurkur      |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Themes        |     Version:  4.2
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  template
--------------------------+-----------------------
Changes (by obenland):

 * status:  new => closed
 * version:  4.4.1 => 4.2
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Replying to [comment:2 bizurkur]:
 > Then what would be the point of having {{{add_theme_support( 'html5'
 )}}}? If pagination/navigation is forced to use HTML5, why is it an option
 to add it to comment lists, forms, and search? Seems like the WordPress
 core should be built around compatibility and to let the theme authors
 dictate whether or not they want to ditch support for older browsers.

 It's a tool to make older template tags HTML5 compatible. Comment list and
 search for example have been around forever. With the emergence of HTML5
 we needed a backwards compatible way to modernize these parts, and
 checking for HTML5 support for them does that.

 > In the rest of the WordPress core, the "de-facto" standard is HTML(4)
 and theme authors have to manually enable support for HTML5... except in
 the pagination/navigation template tags.

 WordPress is 12 years old and is committed to backwards compatibility.
 Themes that have been written 5 years ago should still work with the
 latest version of WordPress. This is why we don't outright overhaul
 existing template tags but use tools like declaring HTML5 support for
 them.

 > Relying on JavaScript to convert HTML5 to markup that can be styled on
 older browsers is not an acceptable solution to all people.
 >
 > I don't think I'm the only one who thinks that way. Luckily there is a
 workaround using {{{get_the_posts_pagination()}}} and manually replacing
 {{{<nav>}}} with {{{<div>}}}, but it just seems like a poor solution when
 there's a function built around the idea of adding HTML5 support when
 '''''desired'''''.

 WordPress tries to push the adoption of modern web technologies. One of
 the ways it does that is by not making new features use old technology,
 and encourage themes to adopt modern technologies by providing these newer
 template tags.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/35372#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform