[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:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  4.4.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  template
--------------------------+------------------------------

Comment (by 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.

 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.

 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'''''.

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