There is no actual vulnerability in the existing implementation, as we can only fetch existing elements (no DOM injection is possible). Plus, the only call occurring on those elements is `HTMLElement#focus`. Consider this an extra, more future-proof precaution.
displayed by `single.php`. See http://codex.wordpress.org/Template_Hierarchy
* Separate scoping and assignment so that a decision does not need to be made as to whether we should intermix spaces and tabs on the left * Restore the previously removed nav-menu class addition to the first unordered list in `#site-navigation`. * Restore the `.navigation-main.toggled-on .nav-menu` selector. * Remove rules for the `.main-small-navigation ul` selector.
… issue #200 * Only set button and menu if container is not null. * Break up the "return early" conditional into multiple parts. * Shorten the name of the toggled class from `toggled-on` to `toggled`. * Restore the "Hide menu toggle button if menu is empty." documentation. * Remove the `nav-menu` class. The previous code would replace any custom custom classes applied via `wp_nav_menu()` or template file. * Replace the `nav-menu` selector is style.css with selectors that will target both a custom nav menu and a page menu. These changes could use critical feedback. Do you know of an edge case where they might not work as expected?
removes an !important declaration in Custom Header CSS rules.
For more information about the philosophy behind the new approach, see http://24ways.org/2012/a-harder-working-class/
…ed via the customizer. Neither setting supports html.
…ntially the same as 136, but without jquery
Doesn't use jQuery, slightly easier to understand, uses a media query for max-width, rather than JS events making it faster to respond.