{"id":12287,"date":"2026-07-03T04:19:43","date_gmt":"2026-07-03T04:19:43","guid":{"rendered":"https:\/\/make.wordpress.org\/test\/?p=12287"},"modified":"2026-07-03T08:33:54","modified_gmt":"2026-07-03T08:33:54","slug":"call-for-testing-responsive-styling","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/test\/2026\/07\/03\/call-for-testing-responsive-styling\/","title":{"rendered":"Call for Testing: Responsive Styling"},"content":{"rendered":"<p class=\"wp-block-paragraph\">As part of the upcoming <strong>WordPress 7.1 release<\/strong>, we\u2019re working on <strong>responsive styling<\/strong> \u2013 the ability to style blocks differently for tablet and mobile, directly from the editor. <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/75121\">PR #75121<\/a> unifies the resizable editor with the device-preview switcher, which is the groundwork this feature builds on, and we\u2019d love your help testing it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">More testing is needed to make sure it\u2019s reliable and intuitive before it ships.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is responsive styling?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Until now, a style you set on a <span tabindex='0' class='glossary-item-container'>block<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Block<\/span> <span class='glossary-item-description'>Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.<\/span><\/span><\/span> \u2013 a font size, some spacing \u2013 applied the same way on every screen. Responsive styling lets you change a value <strong>just for tablet or just for mobile<\/strong>, without writing any custom <span tabindex='0' class='glossary-item-container'>CSS<span class='glossary-item-hidden-content'><span class='glossary-item-header'>CSS<\/span> <span class='glossary-item-description'>CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site.<\/span><\/span><\/span>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A few real examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A large heading on desktop that becomes smaller on mobile.<\/li>\n\n\n\n<li>Generous padding on desktop that tightens up on a phone.<\/li>\n\n\n\n<li>A different text color on the tablet than on the desktop.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">To make these changes, first turn on Responsive editing from the device-preview dropdown \u2013 then switch the device view to Tablet or Mobile and edit the value while that view is active. The change is saved only for that breakpoint.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Let\u2019s you match a design across screen sizes without leaving the editor or hand-writing media queries.<\/li>\n\n\n\n<li>Keeps responsive tweaks, visual, and previewable \u2013 what you see is what visitors get.<\/li>\n\n\n\n<li>Moves WordPress toward fuller per-breakpoint design control in the editor.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to test<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The easiest way to test is <strong>WordPress Playground<\/strong> \u2013 no setup, nothing to install. This loads a fresh site with the latest <span tabindex='0' class='glossary-item-container'>Gutenberg<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Gutenberg<\/span> <span class='glossary-item-description'>The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses \u2018blocks\u2019 to add richness rather than shortcodes, custom HTML etc.\r<a href=\"https:\/\/wordpress.org\/gutenberg\/\">https:\/\/wordpress.org\/gutenberg\/<\/a><\/span><\/span><\/span>, which includes the responsive styling work plus any fixes that have landed since.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-55374303 wp-block-buttons-is-layout-flex\" style=\"margin-top:var(--wp--preset--spacing--20);margin-bottom:var(--wp--preset--spacing--20)\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/playground.wordpress.net\/?gutenberg-branch=trunk\" target=\"_blank\" rel=\"noopener\">Test responsive styling in Playground<\/a><\/div>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">The link logs you in as admin and opens a fresh post, ready to test. Building the PR can take a minute on first load, so give it a moment.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Tip: The device view switcher is the <strong>Desktop \/ Tablet \/ Mobile<\/strong> dropdown in the editor\u2019s top toolbar. Switching it is how you tell WordPress which breakpoint you\u2019re looking at. With this PR, you can also drag the <strong>resize handles<\/strong> at the edge of the canvas to change the width.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Key changes to observe<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The device-preview dropdown and the resizable editor now work together: picking <strong>Tablet<\/strong> or <strong>Mobile<\/strong> sets the canvas width, and dragging the resize handles updates the device view to match.<\/li>\n\n\n\n<li>The dropdown has a new <strong>Responsive editing<\/strong> option. When it\u2019s on, style changes you make apply to the current viewport (Tablet or Mobile) instead of Desktop.<\/li>\n\n\n\n<li>When Responsive editing is on, and you select a block on Tablet or Mobile, a <strong>viewport badge<\/strong> appears in the block inspector showing which device you\u2019re editing. No badge is shown on the desktop, since edits there apply everywhere.<\/li>\n\n\n\n<li>Per-viewport edits are preserved and shown per device; turning Responsive editing off resets the editing state to default, and the badge disappears.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Test steps<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You don\u2019t need to follow all of these \u2013 pick what you have time for, and note anything that feels broken or confusing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario 1 \u2013 Resize handles and device view together (Post editor)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the post editor, open the device dropdown and switch to Tablet (resize handles appear on the canvas edges).<\/li>\n\n\n\n<li>Drag a handle inward and outward and watch the canvas width change.<\/li>\n\n\n\n<li>Drag a handle all the way out to its widest \u2013 the handles should disappear, and you should land back in <strong>Desktop<\/strong> view.<\/li>\n\n\n\n<li>Confirm the dropdown and the handles always agree on which view you\u2019re in.<\/li>\n<\/ol>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Note: In Desktop view, the handles may not show at first if there\u2019s no spare space beside the canvas \u2013 use the dropdown to switch to Tablet\/Mobile first. This is expected.<\/p>\n<\/blockquote>\n\n\n\n\t\t<figure class=\"wp-block-jetpack-videopress jetpack-videopress-player\" style=\"\">\n\t\t\t<div class=\"jetpack-videopress-player__wrapper\"> <iframe loading=\"lazy\" title=\"VideoPress Video Player\" aria-label=\"VideoPress Video Player\" width=\"776\" height=\"325\" src=\"https:\/\/videopress.com\/embed\/I9JFtE4N?cover=1&amp;autoPlay=0&amp;controls=1&amp;loop=0&amp;muted=0&amp;persistVolume=1&amp;playsinline=0&amp;preloadContent=metadata&amp;useAverageColor=1&amp;hd=0\" frameborder=\"0\" allowfullscreen data-resize-to-parent=\"true\" allow=\"clipboard-write\"><\/iframe><script src=\"https:\/\/v0.wordpress.com\/js\/next\/videopress-iframe.js?m=1770107250\"><\/script><\/div>\n\t\t\t\n\t\t\t\n\t\t<\/figure>\n\t\t\n\n\n<h3 class=\"wp-block-heading\">Scenario 2 \u2013 Pattern editor and Navigation editor<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Edit or create a <strong>pattern<\/strong> (Appearance \u2192 Patterns, or via the site editor).<\/li>\n\n\n\n<li>Here, the resize handles are always visible. Drag them and also use the device dropdown.<\/li>\n\n\n\n<li>Confirm the two stay in sync and the canvas resizes smoothly.<\/li>\n\n\n\n<li>Repeat the same check in the <strong>Navigation editor<\/strong> (Appearance \u2192 Editor \u2192 Navigation), where the handles are also always visible.<\/li>\n<\/ol>\n\n\n\n\t\t<figure class=\"wp-block-jetpack-videopress jetpack-videopress-player\" style=\"\">\n\t\t\t<div class=\"jetpack-videopress-player__wrapper\"> <iframe loading=\"lazy\" title=\"VideoPress Video Player\" aria-label=\"VideoPress Video Player\" width=\"776\" height=\"431\" src=\"https:\/\/videopress.com\/embed\/Ajh2AZfF?cover=1&amp;autoPlay=0&amp;controls=1&amp;loop=0&amp;muted=0&amp;persistVolume=1&amp;playsinline=0&amp;preloadContent=metadata&amp;useAverageColor=1&amp;hd=0\" frameborder=\"0\" allowfullscreen data-resize-to-parent=\"true\" allow=\"clipboard-write\"><\/iframe><script src=\"https:\/\/v0.wordpress.com\/js\/next\/videopress-iframe.js?m=1770107250\"><\/script><\/div>\n\t\t\t\n\t\t\t\n\t\t<\/figure>\n\t\t\n\n\n<p class=\"wp-block-paragraph\">This change touches all four editors \u2013 Post, Template \/ Site (Appearance \u2192 Editor \u2192 Templates), Pattern, and Navigation \u2013 so testing across more than one is especially valuable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario 3 \u2013 Responsive editing (the main one)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the device-preview dropdown and turn on <strong>Responsive editing<\/strong>.<\/li>\n\n\n\n<li>Select a block that has style options (e.g., a <strong>Heading<\/strong>). (On Desktop, no viewport badge is shown \u2013 this is intended.)<\/li>\n\n\n\n<li>Switch the device preview to <strong>Tablet<\/strong> or <strong>Mobile<\/strong> \u2013 or drag the canvas to that width. A viewport badge now appears in the block inspector (right <span tabindex='0' class='glossary-item-container'>sidebar<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Sidebar<\/span> <span class='glossary-item-description'>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.<\/span><\/span><\/span>) showing which device you\u2019re editing.<\/li>\n\n\n\n<li>Change a style (for example, a smaller <strong>font size<\/strong>). Confirm the change applies <strong>only<\/strong> to that viewport, not to Desktop.<\/li>\n\n\n\n<li>Switch back to <strong>Desktop<\/strong> and confirm your per-viewport edit is preserved and the Desktop value is unchanged.<\/li>\n\n\n\n<li>Turn <strong>Responsive editing<\/strong> off and confirm the editing state resets to default, and the badge disappears.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Also worth trying (quick real-world checks):<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Save and reload<\/strong> the editor \u2013 your per-viewport edits should still be there.<\/li>\n\n\n\n<li>Try it on a <strong>couple of different blocks<\/strong> (Group, Button, Image) and <strong>different properties<\/strong> (spacing, colors), not just font size.<\/li>\n\n\n\n<li>Set <strong>both<\/strong> Tablet and Mobile differently on the same block and confirm each is remembered.<\/li>\n\n\n\n<li><strong>Undo\/redo<\/strong> a per-viewport edit and confirm it behaves sensibly.<\/li>\n<\/ul>\n\n\n\n\t\t<figure class=\"wp-block-jetpack-videopress jetpack-videopress-player\" style=\"\">\n\t\t\t<div class=\"jetpack-videopress-player__wrapper\"> <iframe loading=\"lazy\" title=\"VideoPress Video Player\" aria-label=\"VideoPress Video Player\" width=\"776\" height=\"354\" src=\"https:\/\/videopress.com\/embed\/AM1MbMjh?cover=1&amp;autoPlay=0&amp;controls=1&amp;loop=0&amp;muted=0&amp;persistVolume=1&amp;playsinline=0&amp;preloadContent=metadata&amp;useAverageColor=1&amp;hd=0\" frameborder=\"0\" allowfullscreen data-resize-to-parent=\"true\" allow=\"clipboard-write\"><\/iframe><script src=\"https:\/\/v0.wordpress.com\/js\/next\/videopress-iframe.js?m=1770107250\"><\/script><\/div>\n\t\t\t\n\t\t\t\n\t\t<\/figure>\n\t\t\n\n\n<h3 class=\"wp-block-heading\">Scenario 4 \u2013 Hidden-on-device blocks respond to canvas resize<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Block visibility itself has already shipped in Gutenberg. What\u2019s new in this PR is that <strong>resizing the canvas<\/strong> (not just the device dropdown) now triggers it.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Add a paragraph and set it to be <strong>hidden on Tablet<\/strong> using the block\u2019s visibility option.<\/li>\n\n\n\n<li>Drag the resize handles into <strong>tablet width<\/strong>. The block should hide.<\/li>\n\n\n\n<li>Drag back out to the desktop width. The block should reappear.<\/li>\n\n\n\n<li>Confirm the <strong>device dropdown<\/strong> set to Tablet hides it too, exactly as before.<\/li>\n<\/ol>\n\n\n\n\t\t<figure class=\"wp-block-jetpack-videopress jetpack-videopress-player\" style=\"\">\n\t\t\t<div class=\"jetpack-videopress-player__wrapper\"> <iframe loading=\"lazy\" title=\"VideoPress Video Player\" aria-label=\"VideoPress Video Player\" width=\"776\" height=\"353\" src=\"https:\/\/videopress.com\/embed\/Xanu1HyD?cover=1&amp;autoPlay=0&amp;controls=1&amp;loop=0&amp;muted=0&amp;persistVolume=1&amp;playsinline=0&amp;preloadContent=metadata&amp;useAverageColor=1&amp;hd=0\" frameborder=\"0\" allowfullscreen data-resize-to-parent=\"true\" allow=\"clipboard-write\"><\/iframe><script src=\"https:\/\/v0.wordpress.com\/js\/next\/videopress-iframe.js?m=1770107250\"><\/script><\/div>\n\t\t\t\n\t\t\t\n\t\t<\/figure>\n\t\t\n\n\n<h3 class=\"wp-block-heading\">Always check the front end<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">After any responsive edit, verify it in <strong>both<\/strong> modes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Preview<\/strong> \u2013 use the editor\u2019s <em>Preview<\/em> (the \u201cView\u201d \/ preview option) to open the page before publishing.<\/li>\n\n\n\n<li><strong>Saved\/published<\/strong> \u2013 <strong>Save<\/strong>, then open the live <span tabindex='0' class='glossary-item-container'>URL<span class='glossary-item-hidden-content'><span class='glossary-item-header'>URL<\/span> <span class='glossary-item-description'>A specific web address of a website or web page on the Internet, such as a website\u2019s URL www.wordpress.org<\/span><\/span><\/span>.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In each mode, resize your browser from wide to narrow \u2013 or use your browser\u2019s device\/responsive view \u2013 through desktop, tablet, and mobile widths. Each width should show the style you set for it (e.g. the smaller font on mobile, the different color on tablet), and both Preview and the saved front end should match what you saw in the editor at the same width.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What to expect<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is active development, so expect a few rough edges, and the <span tabindex='0' class='glossary-item-container'>UI<span class='glossary-item-hidden-content'><span class='glossary-item-header'>UI<\/span> <span class='glossary-item-description'>UI is an acronym for User Interface - the layout of the page the user interacts with. Think \u2018how are they doing that\u2019 and less about what they are doing.<\/span><\/span><\/span> may still change. A couple of things that are known or by design:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Resize handles in Desktop view (post\/template editor):<\/strong> they may not appear at first because there isn\u2019t enough space beside the canvas. Switch to Tablet or Mobile via the dropdown first. A follow-up is planned \u2013 see <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\/71210#issuecomment-3195959898\">#71210<\/a>.<\/li>\n\n\n\n<li><strong>Responsive editing is desktop-first:<\/strong> a value you set on Desktop carries down to Tablet and Mobile unless you override it at that smaller viewport. So seeing the Desktop style on mobile (until you change it) is expected.<\/li>\n\n\n\n<li>Only styles set in the block inspector (right sidebar) \u2013 font size, colors, spacing, etc. \u2013 apply per viewport. Block toolbar controls like alignment apply to all devices.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">For <span tabindex='0' class='glossary-item-container'>plugin<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Plugin<\/span> <span class='glossary-item-description'>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 <a href=\"https:\/\/wordpress.org\/plugins\/\">https:\/\/wordpress.org\/plugins\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span> and theme developers<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your plugin or theme interacts with the editor canvas, please test it against this build \u2013 the underlying device\/canvas model has changed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Code using <code>getDeviceType()<\/code> \/ <code>setDeviceType()<\/code> should keep working. <code>getDeviceType()<\/code> now derives the device from the canvas width, and <code>setDeviceType()<\/code> converts a device to a width.<\/li>\n\n\n\n<li><code>useResizeCanvas()<\/code> is now <strong>deprecated and a no-op<\/strong>. If you rely on it, please tell us your use case.<\/li>\n\n\n\n<li>Responsive styles work out of the box for custom blocks that use block supports (color, typography, border, layout, dimensions), so custom block authors can test on their own blocks too (Note: if a block implements custom controls instead of block supports, responsive styles won\u2019t apply to those).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sharing your Feedback<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There are a few ways to share what you find:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>General feedback \/ <span tabindex='0' class='glossary-item-container'>UX<span class='glossary-item-hidden-content'><span class='glossary-item-header'>UX<\/span> <span class='glossary-item-description'>UX is an acronym for User Experience - the way the user uses the UI. Think \u2018what they are doing\u2019 and less about how they do it.<\/span><\/span><\/span> impressions:<\/strong> comment on this post \u2013 it\u2019s the best place for overall impressions and questions.<\/li>\n\n\n\n<li><strong>Bugs and regressions:<\/strong> open a <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\/new\/choose\">Gutenberg issue<\/a> and reference PR <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/75121\">#75121<\/a>.<\/li>\n\n\n\n<li><strong>Not sure whether it\u2019s a bug?<\/strong> Ask in the <a href=\"https:\/\/wordpress.slack.com\/archives\/C03B0H5J0\">#core-test<\/a> channel on the WordPress <span tabindex='0' class='glossary-item-container'>Slack<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Slack<\/span> <span class='glossary-item-description'>Slack is a Collaborative Group Chat Platform <a href=\"https:\/\/slack.com\/\">https:\/\/slack.com\/<\/a>. The WordPress community has its own Slack Channel at <a href=\"https:\/\/make.wordpress.org\/chat\/\">https:\/\/make.wordpress.org\/chat\/<\/a><\/span><\/span><\/span>.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">We\u2019d love to know, for example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Specifics:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Was it clear how to turn on <strong>Responsive editing<\/strong> and which viewport you were editing?<\/li>\n\n\n\n<li>Did the viewport badge correctly follow the device as you switched?<\/li>\n\n\n\n<li>Did a per-viewport style edit stay on that viewport only, and survive a save and reload?<\/li>\n\n\n\n<li>Did the device dropdown and the resize handles always agree on the current view?<\/li>\n\n\n\n<li>Did resizing feel smooth, or did handles get stuck or disappear unexpectedly?<\/li>\n\n\n\n<li>Did the editor preview match the front end at each width?<\/li>\n\n\n\n<li>Did anything feel slower, confusing, or broken?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The bigger picture:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How intuitive did responsive styling feel overall \u2013 were you able to do what you wanted without guidance?<\/li>\n\n\n\n<li>Does this solve a real problem for you? Would you use it in an actual project?<\/li>\n\n\n\n<li>Anything about the overall approach that felt right, or that you\u2019d design differently?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When reporting something, a short step-by-step with a screenshot or screen recording helps a lot. To make a report actionable, please include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The editor you used (Post, Template \/ Site, Pattern, or Navigation).<\/li>\n\n\n\n<li>Your browser and OS, and whether it was a touch device.<\/li>\n\n\n\n<li>The Gutenberg \/ WordPress version or PR build.<\/li>\n\n\n\n<li>The active theme \u2013 especially block themes with custom breakpoints.<\/li>\n<\/ul>\n\n\n\n<p class=\"has-text-align-right wp-block-paragraph\">Props to <a href=\"https:\/\/profiles.wordpress.org\/huzaifaalmesbah\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>huzaifaalmesbah<\/a>, <a href=\"https:\/\/profiles.wordpress.org\/jeffpaul\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>jeffpaul<\/a>, <a href=\"https:\/\/profiles.wordpress.org\/talldanwp\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>talldanwp<\/a>, <a href=\"https:\/\/profiles.wordpress.org\/isabel_brison\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>isabel_brison<\/a>, and <a href=\"https:\/\/profiles.wordpress.org\/annezazu\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>annezazu<\/a> for review and feedback on this post.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n<p class=\"o2-appended-tags\"><a href=\"https:\/\/make.wordpress.org\/test\/tag\/7-1\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>7-1<\/a>, <a href=\"https:\/\/make.wordpress.org\/test\/tag\/call-for-testing\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>call-for-testing<\/a>, <a href=\"https:\/\/make.wordpress.org\/test\/tag\/core-test\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>core-test<\/a>, <a href=\"https:\/\/make.wordpress.org\/test\/tag\/full-site-editing\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>full-site-editing<\/a>, <a href=\"https:\/\/make.wordpress.org\/test\/tag\/gutenberg\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>gutenberg<\/a><\/p><nav class='o2-post-footer-actions'><ul class='o2-post-footer-action-row'><li class='o2-post-footer-action'><a href=\"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2026%2F07%2F03%2Fcall-for-testing-responsive-styling%2F%23respond&#038;locale=en_US\" title=\"Login to Reply\"  class=\"genericon  genericon-reply\"  data-action=\"login-to-reply\"  data-actionstate=\"default\" >Login to Reply<\/a><\/li><\/ul><div class='o2-post-footer-action-likes'><\/div><ul class='o2-post-footer-action-row'><\/ul><\/nav>","protected":false},"excerpt":{"rendered":"<p>As part of the upcoming WordPress 7.1 release, we\u2019re working on responsive styling \u2013 the ability to style blocks differently for tablet and mobile, directly from the editor. PR #75121 unifies the resizable editor with the device-preview switcher, which is the groundwork this feature builds on, and we\u2019d love your help testing it. More testing [&hellip;]<\/p>\n","protected":false},"author":14674280,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[283],"tags":[836,281,280,315,267],"class_list":["post-12287","post","type-post","status-publish","format-standard","hentry","category-call-for-testing","tag-7-1","tag-call-for-testing","tag-core-test","tag-full-site-editing","tag-gutenberg","mentions-annezazu","mentions-huzaifaalmesbah","mentions-isabel_brison","mentions-jeffpaul","mentions-talldanwp","author-nikunj8866"],"revision_note":"","jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/phhDg8-3cb","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/posts\/12287","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/users\/14674280"}],"replies":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/comments?post=12287"}],"version-history":[{"count":9,"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/posts\/12287\/revisions"}],"predecessor-version":[{"id":12344,"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/posts\/12287\/revisions\/12344"}],"wp:attachment":[{"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/media?parent=12287"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/categories?post=12287"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/make.wordpress.org\/test\/wp-json\/wp\/v2\/tags?post=12287"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}