--- title: Miscellaneous Editor Changes in WordPress 7.1 | daily.dev description: WordPress 7.1 brings several miscellaneous block editor changes for developers. The Navigation block no longer propagates font-size to child items to fix CSS... canonical: https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Miscellaneous Editor Changes in WordPress 7.1 | daily.dev og:description: WordPress 7.1 brings several miscellaneous block editor changes for developers. The Navigation block no longer propagates font-size to child items to fix CSS... og:url: https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5 og:image: https://api.daily.dev/og/posts/gyQtpvyU5.png og:image:alt: Miscellaneous Editor Changes in WordPress 7.1 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Miscellaneous Editor Changes in WordPress 7.1 **[Make WordPress Core](https://daily.dev/sources/wordpresscore)** · 6 min read · 5 upvotes · 1 comments ## Summary WordPress 7.1 brings several miscellaneous block editor changes for developers. The Navigation block no longer propagates font-size to child items to fix CSS compounding issues, with a PHP filter available to restore legacy behavior. The experimental cloneSanitizedBlock and sanitizeBlockAttributes functions are now deprecated in favor of stable versions. The Markdown parser in @wordpress/blocks switches from showdown to marked, following CommonMark/GFM specs. Mobile multi-selection support is added to the paragraph block, shifting editing event handlers to the canvas element. A new disableContentOnlyForTemplateParts editor setting lets themes opt out of content-only editing for Template Parts. Block-level preset CSS classes now use :where() to match root-level specificity, fixing responsive state conflicts. A bug in getEntityRecords() client-side pagination is fixed so non-paginated entities return full collections. The @wordpress/nux package becomes a no-op compatibility shim, and @wordpress/reusable-blocks APIs now log deprecation warnings. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did my custom entity's REST API results get limited to 10 items in WordPress before 7.1? getEntityRecords() applied client-side pagination to every entity, slicing responses to the default per_page of 10 and ignoring remaining records regardless of the page and per_page parameters sent. WordPress 7.1 fixes this bug: slicing now only happens for entities that declare supportsPagination: true, so other entities return the full collection. Custom entities backed by a non-paginated REST route should declare supportsPagination: false to opt out. _Developers auditing REST pagination bugs across WordPress upgrades can track breaking editor changes like this on daily.dev._ ### How do I restore the old font-size propagation behavior for WordPress Navigation block child items after upgrading to 7.1? Add a render_block filter for core/navigation-link, core/navigation-submenu, core/home-link, and core/page-list that checks the block context for a named or custom fontSize and reapplies it as a has-{slug}-font-size class or inline style using WP_HTML_Tag_Processor. This is needed because WordPress 7.1 stops forcefully propagating font-size to child navigation items to prevent compounding relative units in nested dropdown menus. _Theme developers migrating Navigation block styles can check breaking WordPress 7.1 changes like this on daily.dev before shipping._ ### Are __experimentalCloneSanitizedBlock and __experimentalSanitizeBlockAttributes still usable in WordPress 7.1? Yes, but they now log deprecation messages to the console. WordPress 7.1 introduces stable replacements without the __experimental prefix: cloneSanitizedBlock and sanitizeBlockAttributes in the @wordpress/blocks package, and developers should migrate their code to the stable names to avoid the console warnings. _Plugin authors cleaning up deprecated @wordpress/blocks APIs can follow upgrade notes like this via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@legacy8** · 0 upvotes > Wordpress is not going anywhere anytime soon. ## Similar posts on daily.dev - [Miscellaneous Editor Changes in WordPress 6.9](https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-6-9-kbhwlzums) · Make WordPress Core · 1 upvotes · 0 comments - [What’s new for developers? \(September 2026\)](https://daily.dev/posts/what-s-new-for-developers-september-2026--hj9hpdpts) · WordPress Developer · 4 upvotes · 0 comments - [WordPress PHP-Only Block Registration](https://daily.dev/posts/wordpress-php-only-block-registration-ocqm8qoge) · CSS-Tricks · 3 upvotes · 0 comments --- Tags: [#wordpress](https://daily.dev/tags/wordpress), [#rest-api](https://daily.dev/tags/rest-api) [View this post on daily.dev](https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Miscellaneous Editor Changes in WordPress 7.1","url":"https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5"},"datePublished":"2026-08-04T11:10:12.844Z","dateModified":"2026-09-13T21:57:18.739Z","description":"WordPress 7.1 brings several miscellaneous block editor changes for developers. The Navigation block no longer propagates font-size to child items to fix CSS...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6ad4f5b66be737a1618019916626b1bd?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6ad4f5b66be737a1618019916626b1bd?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Make WordPress Core","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Make WordPress Core","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/892d1a79e30e4e8a911b5726c6fb1a06","url":"https://daily.dev/sources/wordpresscore"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"wordpress,rest-api","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Make WordPress Core","item":"https://daily.dev/sources/wordpresscore"},{"@type":"ListItem","position":3,"name":"Miscellaneous Editor Changes in WordPress 7.1"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5","comment":[{"@type":"Comment","text":"Wordpress is not going anywhere anytime soon.","datePublished":"2026-08-09T01:40:26.723Z","url":"https://daily.dev/posts/gyQtpvyU5#c-IjeBG0BWj","author":{"@type":"Person","name":"Legacy","url":"https://daily.dev/legacy8","image":"https://avatars.githubusercontent.com/u/52163001?v=4"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/miscellaneous-editor-changes-in-wordpress-7-1-gyqtpvyu5#faq","mainEntity":[{"@type":"Question","name":"Why did my custom entity's REST API results get limited to 10 items in WordPress before 7.1?","acceptedAnswer":{"@type":"Answer","text":"getEntityRecords() applied client-side pagination to every entity, slicing responses to the default per_page of 10 and ignoring remaining records regardless of the page and per_page parameters sent. WordPress 7.1 fixes this bug: slicing now only happens for entities that declare supportsPagination: true, so other entities return the full collection. Custom entities backed by a non-paginated REST route should declare supportsPagination: false to opt out. Developers auditing REST pagination bugs across WordPress upgrades can track breaking editor changes like this on daily.dev."}},{"@type":"Question","name":"How do I restore the old font-size propagation behavior for WordPress Navigation block child items after upgrading to 7.1?","acceptedAnswer":{"@type":"Answer","text":"Add a render_block filter for core/navigation-link, core/navigation-submenu, core/home-link, and core/page-list that checks the block context for a named or custom fontSize and reapplies it as a has-{slug}-font-size class or inline style using WP_HTML_Tag_Processor. This is needed because WordPress 7.1 stops forcefully propagating font-size to child navigation items to prevent compounding relative units in nested dropdown menus. Theme developers migrating Navigation block styles can check breaking WordPress 7.1 changes like this on daily.dev before shipping."}},{"@type":"Question","name":"Are __experimentalCloneSanitizedBlock and __experimentalSanitizeBlockAttributes still usable in WordPress 7.1?","acceptedAnswer":{"@type":"Answer","text":"Yes, but they now log deprecation messages to the console. WordPress 7.1 introduces stable replacements without the __experimental prefix: cloneSanitizedBlock and sanitizeBlockAttributes in the @wordpress/blocks package, and developers should migrate their code to the stable names to avoid the console warnings. Plugin authors cleaning up deprecated @wordpress/blocks APIs can follow upgrade notes like this via daily.dev."}}]} ```