You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In off-canvas sidebars the widgets are output wrapped in <li> HTML elements, but not as children of a <ul>, <ol>, or <menu> element –or the obsolete <dir> element–, which is invalid HTML markup (reference in MDN).
Steps to reproduce the behavior:
Add a off-canvas sidebar.
Add a couple of widgets inside the sidebar.
Inspect the code in dev tools to see the <li> elements wrapping the widgets.
Expected behavior
In my opinion, the widgets should not be output wrapped in <li> elements, <div> seems to me semantically more neutral and appropriate.
Screenshots
Specifications
Plugin Version: 0.5.4
WordPress Version:5.4.1
Other plugins installed: none
Theme: Twenty NineteenVersión: 1.5
Browser: Chrome version 81.0.4044.138 (Official Build) (64-bit)
URL of where the bug occurs: staging site not public
Location of hook placement:
header.php: directly after <body <?php body_class(); ?>
footer.php: directly after the site content, before <?php wp_footer(); ?>)
The text was updated successfully, but these errors were encountered:
You can change this through the ocs_register_sidebar_args filter to change it according to your theme.
WordPress by default uses <li> elements for widgets (no idea why...) so I'm trying not to change to much in WordPress defaults.
However, in this case I do agree that it might be better for me to overwrite this default since the sidebars will never be list items in my case I suppose.
Describe the bug
In off-canvas sidebars the widgets are output wrapped in
<li>HTML elements, but not as children of a<ul>,<ol>, or<menu>element –or the obsolete<dir>element–, which is invalid HTML markup (reference in MDN).Steps to reproduce the behavior:
<li>elements wrapping the widgets.Expected behavior
In my opinion, the widgets should not be output wrapped in
<li>elements,<div>seems to me semantically more neutral and appropriate.Screenshots
Specifications
<body <?php body_class(); ?><?php wp_footer(); ?>)The text was updated successfully, but these errors were encountered: