Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Derek Herman 8:00 pm on March 11, 2015
Tags: 4.2 ( 67 ), HTML5 ( 4 ), themes ( 43 ), widgets ( 26 )

HTML5 Widgets in WordPress 4.2

HTML5 widgets theme support in 4.2 has been reverted pending a decision about the correct container to use

With the upcoming WordPress 4.2 release, widgets have been added to the growing list of HTML5 supported markup. Once you’ve added HTML5 support for widgets, WordPress will use the <aside> element, instead of the generic list markup.

To declare that your theme supports HTML5 widgets, add the following call to your theme’s functions.php file, preferably in a callback to the after_setup_theme action:

add_theme_support( 'html5', array( 'widgets' ) );

For forward compatibility reasons, the second argument cannot be omitted when registering support. Otherwise, a theme would automatically declare its support for HTML5 features that might be added in the future, possibly breaking it visually.

If there are any questions about the current implementation, feel free to leave a comment below.

#4-2, #html5, #themes, #widgets

Emil Uzelac 8:54 pm on March 11, 2015

Awesome!
danieliser 9:22 pm on March 11, 2015

Wrote a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party a few years back that did this quite well. https://wordpress.org/plugins/html5-widgets/. The only thing I’m seeing here that is missing that is quite easy to add is assignment of the what html5 wrapper is used. For instance a nav menu should likely be wrapped in the

tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) rather than an

.

Nice to see it making it into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. finally.

+1
- Rami Yushuvaev 12:55 pm on March 12, 2015
  
  Daniel, you can do that with the GenerateWP SidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. Generator (http://generatewp.com/sidebar/) check the examples to generate sidebast with list items, div’s and aside’s.
Rami Yushuvaev 12:24 pm on March 12, 2015

I’ve updated the code:

https://codex.wordpress.org/Semantic_Markup

https://codex.wordpress.org/Function_Reference/add_theme_support#HTML5
- Rami Yushuvaev 9:58 pm on May 26, 2015
  
  Codex reverted.
Derek Herman 2:16 am on March 13, 2015

Just a quick heads up. We’re going to be changing the markup to sections instead of asides. The reason is because there are accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) concerns that come into play by proliferating ARIA landmarks. This change should happen soon, and I’ll update the post once a changeset exists.
- JakePT 2:24 am on March 13, 2015
  
  In my themes I’ve used section for widgets, and the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. is an aside element. So I like this idea. However wouldn’t there be semantic issues using sections without an appropriate wrapper? Should this feature come with such a recommendation?
  - Derek Herman 1:05 pm on March 16, 2015
    
    Yes, some mention of using an aside or another sectioning element to wrap your widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. sections should be added to the docs. I believe the semantically correct markup would also include adding a title to the aside for the document outline, but is not strictly required.
Devin Price 10:34 pm on March 13, 2015

Not directly related, but I’d love to see one other update go in with this. When styling widgets, I often need some markup to wrap the widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. content.

We have:

before_title
after_title

It would be nice to have:

before_content
after_content
- Derek Herman 1:15 pm on March 16, 2015
  
  I agree, it would be nice, though is out of the scope of the current patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. As well, there already exists a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. issue for this at https://core.trac.wordpress.org/ticket/10976 Granted it’s more that a little old. I’ll look into refreshing that patch for 4.3, as the 4.2 enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. deadline has passed.
Tomas Mackevicius 10:32 pm on March 16, 2015

Interesting, I’m using WP 4.1.1 at the moment and all standard widgets are generated as asides already :-/
- Tomas Mackevicius 10:44 pm on March 16, 2015
  
  Silly me… I was using aside in before_widget in my theme 😀
  
  Sorry!