Here we are in the tenth week of the MP6 experiment, and with it comes our tenth release, 1.0. And while the version number is simply the one that comes after 0.9, it’s also beginning to look nearly complete. We’ve worked our way through our primary to-do list, concentrating now on responsive issues and core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issues for which we’ll be submitting patches. Here’s what’s new this week.
- Restyled toolbar submenus with a dark background that matches menubar submenus.
- Made all the various delete/trash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. links the same color red, and removed inconsistent backgrounds/borders.
- Improved the alignment of notices within thickbox containers.
- Added right padding to top level adminmenu links to leave room for the current arrow indicator.
- Improved the appearance of the file upload input.
- Improved the appearance of the comment moderation confirmation screen.
- Removed the blue hover state from disabled page navigation links.
- Removed the wayward borders within the .widefat table.
- Fixed a z-index issue causing toggle arrows to overlap expanded widgets on the widget 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. management page.
- Submenu and current item arrows in the .folded and .auto-fold states are now the same size.
- Corrected the alignment of the New link in toolbar.
- The annoying bug where the W menu opens by default on every page load has been fixed.
- General coding standards improvements throughout.
- Updated the Dashicons icon font.
- Mobile: Improved theme updates table styling.
- Mobile: Fixed toolbar quicklinks line height.
- Mobile: Improved plugins list styling.
- Mobile: Menu management page improvements.
- Mobile: Allow the HTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. editor buttons to wrap to two lines on small screens.
- Mobile: Improved styling of the link manager on small screens.
- Mobile: Adjusted height of select elements to match button height.
- Mobile: Bigger touch targets in the file editor’s file list; larger textarea for the editor.
- Mobile: Improved styling for post format options on small screens.
- Mobile: Fixed TinyMCE split buttons and list boxes.
- RTL: Added RTL tests to /branches/.
- RTL: Fixed meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress./post box widget positioning.
- RTL: Fixed Plugin 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/theme editor submit button position.
- RTL: Fixed dashboard comment widget avatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. position.
Whew! This week’s iteration includes contributions from Joen Asmussen, Mel Choyce, Ben Dunkle, Michael Erlewine (mitcho), Till Krüss, and myself.
We’ll be in #wordpress-ui to discuss your feedback on Monday, May 6 at 18:00 UTC. Thanks again as always to everyone who’s contributed your feedback so far. As always, please keep it coming — we’re interested in any suggestions, bug reports, ideas, or patches you may have. If you’ve reported an issue that we haven’t addressed yet, it won’t hurt to mention it again (with a screenshot if possible) at this point.
#mp6