HTML5 support for specific features doesn't work.
|Reported by:||nathanrice||Owned by:||nacin|
|Severity:||normal||Keywords:||has-patch commit fixed-major needs-codex|
Description (last modified by SergeyBiryukov)
The check for the second parameter in current_theme_supports() in  is irrelevant.
Unit test here:
There is no exception in the switch statement for html5 support, so the function just returns true (early) if html5 is supported at all. The second parameter is essentially ignored.
So, if you intend to turn on html5 output for just 1 of the 3 options, it doesn't matter. All 3 will output in html5.
Which is, perhaps, intentional. I'm really not sure.
If not, I'm prepping a patch to correct it.
Change History (22)
- Keywords commit added
- Owner set to nacin
- Status changed from new to accepted