Skip to content

Quick edit: Show frequently edited fields inline - #85775

Open
jameskoster wants to merge 8 commits into
trunkfrom
update/quick-edit-regular-field-layout
Open

jameskoster wants to merge 8 commits into
trunkfrom
update/quick-edit-regular-field-layout

Conversation

@jameskoster

@jameskoster jameskoster commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

What?

See #84391

The quick edit drawer now shows the fields people edit most as inline controls. The rest keep their panels and are pinned to the bottom of the drawer, just above Cancel and Done.

This targets WordPress 7.3. The post editor's document sidebar is unchanged, apart from the Author, Link and Password improvements below and the removal of the divider above Password.

Why?

Opening the quick edit drawer is already a choice to edit. With every field in a panel, each change takes a second click to reveal the control, which makes quick edit slower than it should be. The issue covers this along with other bulk edit ideas; this PR only addresses that extra click.

How?

  • Drawer form in the view config: the view config endpoint returns a new quick_edit_form next to form (compat 7.3), so the drawer layout is shared by both site editors and extenders can change it with the same get_entity_view_config_* filters they use for form.
    • The default for post types puts Status, Sticky, Link, Author, Template and Excerpt in the regular layout (label on top), and keeps Date, Discussion, Password, Parent, Format and Revisions as panels.
    • Post types that provide their own form (templates, template parts, patterns, attachments) have no quick edit form by default, and the drawer uses their form instead.
    • Gutenberg_View_Config_Data::CONFIG_KEYS gains the new key, with an @since 7.3.0 note: the class checks keys against self::CONFIG_KEYS, so a 7.3 subclass couldn't extend it.
  • Inline vs. panel: both drawers split the quick edit form by layout type into two DataForms that share data and onChange: regular fields in the scrolling area, panels in a pinned area above the buttons. There is no field-specific logic left in the drawers.
  • DataForm config: a form field can pass settings to its field's Edit control through a new config property, merged over the field's own edit config, e.g. { id: 'status', config: { compact: true } }. It works in the regular and panel layouts.
  • Status: core-fields now ships the status Edit. It renders radios (RadioGroupControl from @wordpress/ui) by default, so the sidebar keeps its radios, and a SelectControl with a 16px icon and a description for each status when the form passes compact, as the drawer's form does. Trash is never offered as a choice.
  • Scheduled date: the drawer's form leaves out the date control that appears below Status for scheduled posts, since the pinned Date panel edits the same date. The sidebar still shows it.
  • Password: a field of its own in the drawer, pinned after Discussion because it is rarely set. A new render in core-fields summarises it as "Protected" or "None", so the panel row never shows the password. Data views that show the password column get the same summary. The divider above Password in the sidebar is removed.
  • Author: a SelectControl from @wordpress/ui with each author's avatar, shown with the same AuthorAvatar as the author view, so the default avatar of an author without a Gravatar is sized like the others. This is a new Edit in core-fields, so the sidebar's Author panel uses it too.
  • Link (slug): removes the description and the "Learn more" link. The full permalink shows as plain text in the input's details, below the slug. The copy button follows the Copy to Clipboard pattern: a minimal, neutral, compact IconButton labelled "Copy" that swaps to a check (or an error icon) for two seconds and announces the result with speak(), instead of showing a snackbar. These changes also apply to the sidebar's Link panel.
  • Parent: the "Child pages inherit…" explanation moves below the control as help text.
  • Template and Link: they now show their visible label when rendered inline.
  • Template on the front page and posts page: the drawers no longer mark Template read-only there, which showed it as plain text once it moved inline. The template control already disables its select on those pages, so it shows as a disabled select with the current template.
  • Drawer width: the drawer is narrower, capped at the small surface width token (--wpds-dimension-surface-width-sm, 320px) instead of 400px, so it is closer to the editor's sidebar. It keeps Modal's padding.
  • Divider: the pinned panels area has a top border made from @wordpress/theme tokens, with 16px of space above it so the inline fields don't sit against the border when they scroll.
  • Both editors: the changes are in the site editor (packages/edit-site) and the extensible site editor (routes/post-list). The latter now depends on @wordpress/ui.
  • Tests: PHPUnit tests for the 7.3 controller and the default quick edit form; DataForm unit tests for config; e2e specs updated for the new controls, and the view config extensibility spec now filters quick_edit_form.

For reviewers

  • IconButton from @wordpress/ui is marked "use with caution", and @wordpress/use-recommended-components flags it outside experimental code. The slug field has a one-line exception because the Copy to Clipboard pattern specifies it. If that isn't acceptable in core-fields yet, the fallback is the @wordpress/components button with the same icon swap and announcement.
  • core-fields no longer imports @wordpress/notices, but the dependency is still declared. Removing it would also touch package-lock.json, so it is left for a follow-up.
  • Bulk editing still uses the drawer's allowlist (Status, Date, Author, Discussion). Site Editor: template and parent fields are bulk editable #85947 adds Template and Parent; whichever PR lands second rebases. Letting fields declare bulk support is out of scope here.

Testing Instructions

  1. Go to Appearance > Editor > Pages.
  2. Open a page's actions menu and choose Quick Edit.
  3. Check the inline fields:
    • Status, Link, Author and Template are editable inline. Excerpt shows for posts, and for pages when a theme or plugin adds excerpt support (Jetpack does, for example).
    • Date, Discussion, Password and Parent are panels pinned above Cancel and Done.
    • The inline fields scroll above the pinned panels, with space between the last field and the border.
  4. Change Status and Author through the selects, and check the icons and avatars. An author without a Gravatar shows the default avatar at the same size as the others. Trash is not offered.
  5. Set Status to Scheduled and check that no extra date control appears below it.
  6. Check the Link field:
    • The full permalink shows below the input and updates as you edit the slug.
    • Copy switches to a check icon briefly, and the permalink is on the clipboard.
  7. Open the Password panel and set a password. The panel row reads "Protected". Set Status to Private and check that the Password panel disappears.
  8. Open Quick Edit on the front page (or the posts page) and check that Template is a disabled select showing its template, not plain text.
  9. Change the Link and Parent, then select Done and check that the changes are saved.
  10. Select several pages and choose Quick Edit:
  • Status and Author show inline.
  • Date and Discussion are pinned.
  1. Open a post in the post editor and check the document sidebar:
    • The fields are still panels.
    • Status still uses radio buttons, without Trash, and there is no divider above Password.
    • Author uses the avatar select.
    • Link is simplified, shows the full permalink, and uses the new copy button.
  2. Repeat steps 1 to 10 with the extensible site editor experiment enabled.
  3. To check extensibility, add a filter that changes the drawer form, and check that Quick Edit shows only those fields, while the post editor's sidebar is unchanged:
    add_filter( 'get_entity_view_config_posttype_page', function ( $data ) {
    	return $data->replace( array( 'quick_edit_form' => array( 'fields' => array( 'slug', 'date' ) ) ), 1 );
    } );

Testing Instructions for Keyboard

  1. Open Quick Edit and press Tab to move through the inline fields, then the pinned panels, then Cancel and Done.
  2. On the Status and Author selects:
    • Enter or Space opens the list.
    • The arrow keys move through the options.
    • Enter selects an option.
    • Escape closes the list without closing the drawer.
  3. On the Link field's Copy button, Enter copies the permalink, focus stays on the button, and a screen reader announces "Copied to clipboard".
  4. On a pinned panel, Enter opens its popover, and Escape returns focus to the panel's button.
  5. In the post editor's Status panel, the arrow keys move between the status radios.

Screenshots or screencast

Screenshot 2026-11-17 at 15 35 34

Use of AI Tools

This PR was written with Claude Code (Claude Opus 5.5), with direction and design review from me. I have reviewed the changes and tested them in the site editor.

@github-actions github-actions Bot added [Package] E2E Tests /packages/e2e-tests [Package] Edit Site /packages/edit-site [Package] Fields /packages/fields labels Oct 27, 2026
@jameskoster
jameskoster requested a review from a team October 27, 2026 19:09
@jameskoster jameskoster added [Type] Enhancement A suggestion for improvement. [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") Needs Design Feedback Needs general design feedback. labels Oct 27, 2026
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

🤖 PR meta 🤖

Preview in WordPress Playground

🎉 Props

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: oandregal <oandregal@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>
Co-authored-by: verofasulo <veronicafasulo@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

Updated as activity occurs, without notifying anyone named here. Add the props-bot label to refresh.

📦 Bundle size

Size Change: +19.9 kB (+0.23%)

Total Size: 8.7 MB

📦 View Changed
Filename Size Change
build/modules/core-fields/post_type_supports.min.js 101 kB +19.7 kB (+24.31%) 🚨
build/scripts/block-editor/index.min.js 556 kB +29 B (+0.01%)
build/scripts/core-data/index.min.js 77.7 kB +8 B (+0.01%)
build/scripts/edit-site/index.min.js 383 kB +43 B (+0.01%)
build/scripts/editor/index.min.js 572 kB +28 B (0%)
build/scripts/media-utils/index.min.js 238 kB +6 B (0%)
build/styles/edit-site/style-rtl.css 21.3 kB +34 B (+0.16%)
build/styles/edit-site/style-rtl.min.css 17.2 kB +29 B (+0.17%)
build/styles/edit-site/style.css 21.3 kB +35 B (+0.16%)
build/styles/edit-site/style.min.css 17.2 kB +30 B (+0.17%)
build/styles/editor/style-rtl.css 32.2 kB -13 B (-0.04%)
build/styles/editor/style-rtl.min.css 27.9 kB -10 B (-0.04%)
build/styles/editor/style.css 32.3 kB -13 B (-0.04%)
build/styles/editor/style.min.css 27.8 kB -10 B (-0.04%)

ba03d6f Run

⚡ Performance

Show the results

Client side metrics exclude the server response time.

front-end-block-theme

Metric 8687bba trunk % Change
timeToFirstByte 33.05 ms +11.2% -4.24% 36.2 ms +10.08% -12.29% -8.7%
largestContentfulPaint 56 ms +3.57% -7.14% 56 ms +14.29% -3.57% 0%
lcpMinusTtfb 22.1 ms +11.09% -8.37% 21.5 ms +12.79% -9.07% 2.79%
wpBeforeTemplate 17.08 ms +14.75% -1.58% 17.88 ms +23.88% -6.71% -4.47%
wpTemplate 12.97 ms +4.63% -7.56% 13.02 ms +6.99% -5.15% -0.38%
wpTotal 30.31 ms +11.45% -5.61% 33.25 ms +8.63% -12.96% -8.84%
wpMemoryUsage 7.76 MB +0% -0% 7.71 MB +0% -0% 0.59%
wpDbQueries 16 +0% -0% 16 +0% -0% 0%

front-end-classic-theme

Metric 8687bba trunk % Change
timeToFirstByte 27.4 ms +9.67% -1.82% 27.2 ms +7.9% -1.84% 0.74%
largestContentfulPaint 52 ms +0% -0% 50 ms +4% -4% 4%
lcpMinusTtfb 24 ms +3.96% -7.5% 21.8 ms +10.09% -2.29% 10.09%
wpBeforeTemplate 15.22 ms +10.91% -0.79% 15.02 ms +9.12% -1.26% 1.33%
wpTemplate 9.73 ms +2.36% -2.36% 9.59 ms +4.07% -3.55% 1.46%
wpTotal 24.95 ms +10.38% -1.8% 24.87 ms +7.8% -2.29% 0.32%
wpMemoryUsage 6.45 MB +0% -0% 6.40 MB +0% -0% 0.72%
wpDbQueries 13 +0% -0% 13 +0% -0% 0%

media-processing

Metric 8687bba trunk % Change
mediaProcessingJpeg 212.76 ms +1.26% -1.21% 215.09 ms +3.59% -0.6% -1.08%
mediaProcessingAvif 3495.78 ms +0.84% -0.4% 3467.58 ms +1.37% -0.29% 0.81%
mediaProcessingJpegToAvif 2447.85 ms +1.99% -0.02% 2426.39 ms +0.31% -0.53% 0.88%

media-upload

Metric 8687bba trunk % Change
jpegUploadProcessing 1412.08 ms +2.14% -28.08% 1415.31 ms +0.39% -0.98% -0.23%
pngUploadProcessing 176.54 ms +4% -1.46% 174.92 ms +6.75% -1.55% 0.93%
largeJpegUploadProcessing 1410.24 ms +0.52% -0.58% 1417.13 ms +0.47% -0.67% -0.49%
multipleImageUploadProcessing 1451.65 ms +0.5% -0.62% 1449.41 ms +1.2% -0.39% 0.15%

post-editor

Metric 8687bba trunk % Change
serverResponse 477.79 ms +0.51% -6.61% 486.19 ms +1.39% -2.28% -1.73%
firstPaint 450.96 ms +4.81% -9.97% 434.84 ms +7.75% -8.67% 3.71%
domContentLoaded 828.82 ms +2.88% -0.61% 822.94 ms +1.61% -0.37% 0.71%
loaded 829.86 ms +2.9% -0.61% 823.96 ms +1.64% -0.34% 0.72%
firstContentfulPaint 467.7 ms +1.83% -1.19% 459.13 ms +4.48% -2.77% 1.87%
firstBlock 2222.39 ms +7.92% -2.91% 2219.43 ms +1.33% -1.83% 0.13%
type 17.19 ms +12.51% -8.84% 21.05 ms +26.89% -5.13% -18.34%
typeWithoutInspector 16.92 ms +4.14% -13.24% 17.73 ms +10.83% -12.58% -4.57%
typeWithTopToolbar 21.27 ms +5.69% -1.79% 23.4 ms +6.32% -7.01% -9.1%
typeContainer 8.35 ms +2.87% -6.11% 7.5 ms +6.67% -8.4% 11.33%
focus 127.83 ms +1.89% -15.09% 116.89 ms +8.03% -4.3% 9.36%
firstFocus 271.51 ms +0% -0% 240.52 ms +0% -0% 12.88%
selectAll 404.19 ms +1.73% -0.49% 401.73 ms +3.11% -0.24% 0.61%
undo 26.94 ms +8.76% -1.19% 31.08 ms +1.42% -7.92% -13.32%
listViewOpen 81.55 ms +7.81% -7.85% 78.61 ms +5.24% -9.69% 3.74%
inserterOpen 41.41 ms +12.29% -8.14% 44.17 ms +8.47% -21.33% -6.25%
inserterHover 11.18 ms +13.42% -11.09% 11.12 ms +15.11% -5.76% 0.54%
inserterSearch 8.3 ms +3.13% -4.34% 8.18 ms +10.51% -8.8% 1.47%
loadPatterns 639.22 ms +6.35% -4.97% 638.67 ms +2.09% -3.29% 0.09%
wpTotal 468.19 ms +0.49% -6.79% 476.55 ms +1.09% -2.36% -1.75%
wpMemoryUsage 14.82 MB +0% -0% 14.77 MB +0% -0% 0.36%
wpDbQueries 55 +0% -0% 55 +0% -0% 0%

site-editor

Metric 8687bba trunk % Change
serverResponse 261.44 ms +3.01% -6.25% 275.37 ms +1.12% -2.6% -5.06%
firstPaint 323.37 ms +11.3% -7.12% 300.59 ms +8.92% -3.38% 7.58%
domContentLoaded 583.47 ms +4.84% -2.38% 593.85 ms +1.27% -1.35% -1.75%
loaded 584.39 ms +4.84% -2.38% 594.75 ms +1.27% -1.35% -1.74%
firstContentfulPaint 333.15 ms +9.76% -2.5% 335.88 ms +2.91% -3.89% -0.81%
firstBlock 1835.52 ms +1.78% -5.66% 1813.04 ms +0.91% -2.37% 1.24%
type 14.43 ms +5.82% -1.25% 14.49 ms +2.76% -13.39% -0.41%
navigate 80.81 ms +23.05% -5.12% 90.54 ms +4.15% -4.96% -10.75%
loadPatterns 1032.81 ms +9.02% -20.82% 971.81 ms +14.72% -5.16% 6.28%
loadPages 937.07 ms +2.16% -1.52% 908.72 ms +3.75% -0.64% 3.12%
wpTotal 254.58 ms +3.14% -6.38% 268.66 ms +1.19% -2.77% -5.24%
wpMemoryUsage 12.83 MB +0% -0% 12.79 MB +0% -0% 0.34%
wpDbQueries 45 +0% -0% 45 +0% -0% 0%

ba03d6f Run

🏁 Flaky tests

Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

As a user I want to be able to add multiple close buttons so that users can close the overlay from different positions in /test/e2e/specs/site-editor/navigation-overlay-template-part.spec.js, passed after 1 failed attempt.
Error: expect(locator).toHaveCount(expected) failed

Locator:  getByRole('button', { name: 'Close' })
Expected: 2
Received: 1
Timeout:  5000ms

Call log:
  - Expect "toHaveCount" getByRole('button', { name: 'Close' }) with timeout 5000ms
  - waiting for getByRole('button', { name: 'Close' })
    14 × locator resolved to 1 element
       - unexpected value "1"

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-overlay-template-part.spec.js:228:33
Undo restores the post selection when another synced entity is loaded (RTC WebSocket) in /test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 2
+ Received  + 2

  Object {
    "attributeKey": "content",
    "blockIndex": 0,
    "content": "abcdef",
-   "endOffset": 3,
-   "offset": 3,
+   "endOffset": 6,
+   "offset": 6,
  }

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts:363:5
Undo restores the post selection when another synced entity is loaded in /test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 2
+ Received  + 2

  Object {
    "attributeKey": "content",
    "blockIndex": 0,
    "content": "abcdef",
-   "endOffset": 3,
-   "offset": 3,
+   "endOffset": 1,
+   "offset": 1,
  }

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts:363:5
a navigation superseded by the traversal discharges to idle in /test/e2e/specs/interactivity/router-navigation-lifecycle.spec.ts, passed after 1 failed attempt.
SyntaxError: Unexpected token 'o', "not hydrated" is not valid JSON
    at readLog (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigation-lifecycle.spec.ts:28:14)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigation-lifecycle.spec.ts:47:24
    at waitForLogLength (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigation-lifecycle.spec.ts:46:2)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigation-lifecycle.spec.ts:693:5
does not select blocks in the canvas preview when editing from the sidebar (Site Editor v2) in /test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js, passed after 1 failed attempt.
Error: expect(locator).toBeFocused() failed

Locator: getByRole('combobox', { name: 'Search or type URL' })
Expected: focused
Timeout: 5000ms
Error: element(s) not found

Call log:
  - Expect "toBeFocused" getByRole('combobox', { name: 'Search or type URL' }) with timeout 5000ms
  - waiting for getByRole('combobox', { name: 'Search or type URL' })

    at LinkControl.useLinkControlSearch (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js:416:47)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js:179:21
should cut and paste individual blocks with collapsed selection in /test/e2e/specs/editor/various/copy-cut-paste.spec.js, passed after 1 failed attempt.
Error: expect(string).toMatchSnapshot(expected) failed

  @@ -1,3 +1,3 @@
   <!-- wp:paragraph -->
  -<p>2Cut - collapsed selection</p>
  +<p>2</p>
   <!-- /wp:paragraph -->


    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/copy-cut-paste.spec.js:45:49
should format text across blocks in /test/e2e/specs/editor/various/multi-block-selection.spec.js, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 1
+ Received  + 1

@@ -1,9 +1,9 @@
  Array [
    Object {
      "attributes": Object {
-       "content": "ab",
+       "content": "",
      },
      "name": "core/paragraph",
    },
    Object {
      "attributes": Object {

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/multi-block-selection.spec.js:2219:41
should gradually multi-select in /test/e2e/specs/editor/various/multi-block-selection.spec.js, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 1
+ Received  + 1

  Array [
    Object {
-     "name": "core/column",
+     "name": "core/paragraph",
    },
  ]

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/multi-block-selection.spec.js:1194:5
should indent and outdent a list item when its content is fully selected in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
Error: expect(received).toBe(expected) // Object.is equality

- Expected  - 5
+ Received  + 1

  <!-- wp:list -->
  <ul class="wp-block-list"><!-- wp:list-item -->
- <li>a<!-- wp:list -->
- <ul class="wp-block-list"><!-- wp:list-item -->
- <li>b</li>
- <!-- /wp:list-item --></ul>
- <!-- /wp:list --></li>
+ <li>b</li>
  <!-- /wp:list-item --></ul>
  <!-- /wp:list -->

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:819:52
should indent and outdent level 1 in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Indent"]')

    at Editor.clickBlockToolbarButton (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:17:15)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:775:3
should indent and outdent level 2 in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Indent"]')

    at Editor.clickBlockToolbarButton (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:17:15)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:933:3
should keep a full selection when outdenting nested items with Shift+Tab in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Indent"]')
    - locator resolved to <button id="_r_1l_" type="button" tabindex="-1" aria-label="Indent" aria-disabled="true" data-toolbar-item="true" data-truly-disabled="false" aria-describedby="components-button__description-26" class="components-button components-toolbar-button is-compact has-icon">…</button>
  - attempting click action
    2 × waiting for element to be visible, enabled and stable
      - element is not enabled
    - retrying click action
    - waiting 20ms
    2 × waiting for element to be visible, enabled and stable
      - element is not enabled
    - retrying click action
      - waiting 100ms
    18 × waiting for element to be visible, enabled and stable
       - element is not enabled
     - retrying click action
       - waiting 500ms

    at Editor.clickBlockToolbarButton (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:17:15)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:1166:3
should leave nested list intact when deleting the parent item in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  -  1
+ Received  + 19

@@ -1,19 +1,36 @@
  Array [
    Object {
+     "attributes": Object {
+       "content": "1",
+       "dropCap": false,
+     },
+     "innerBlocks": Array [],
+     "name": "core/paragraph",
+   },
+   Object {
+     "attributes": Object {
+       "ordered": false,
+       "values": "",
+     },
      "innerBlocks": Array [
        Object {
          "attributes": Object {
-           "content": "1",
+           "content": "",
          },
          "innerBlocks": Array [
            Object {
+             "attributes": Object {
+               "ordered": false,
+               "values": "",
+             },
              "innerBlocks": Array [
                Object {
                  "attributes": Object {
                    "content": "a",
                  },
+                 "innerBlocks": Array [],
                  "name": "core/list-item",
                },
              ],
              "name": "core/list",
            },
@@ -22,10 +39,11 @@
        },
        Object {
          "attributes": Object {
            "content": "3",
          },
+         "innerBlocks": Array [],
          "name": "core/list-item",
        },
      ],
      "name": "core/list",
    },
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:3017:38
should merge a following sibling list into the outermost list with Delete from a nested item (#77245) in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 2
+ Received  + 2

@@ -8,11 +8,11 @@
          "innerBlocks": Array [
            Object {
              "innerBlocks": Array [
                Object {
                  "attributes": Object {
-                   "content": "b‸",
+                   "content": "b",
                  },
                  "name": "core/list-item",
                },
              ],
              "name": "core/list",
@@ -25,11 +25,11 @@
    },
    Object {
      "innerBlocks": Array [
        Object {
          "attributes": Object {
-           "content": "1",
+           "content": "‸1",
          },
          "innerBlocks": Array [
            Object {
              "innerBlocks": Array [
                Object {

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:2854:41
should outdent list items when deleting an empty parent at the top in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 19
+ Received  +  1

- Array [
-   Object {
-     "innerBlocks": Array [
-       Object {
-         "attributes": Object {
-           "content": "a",
-         },
-         "name": "core/list-item",
-       },
-       Object {
-         "attributes": Object {
-           "content": "b",
-         },
-         "name": "core/list-item",
-       },
-     ],
-     "name": "core/list",
-   },
- ]
+ Array []

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:3074:41
should remove an anchored list when deleting its last item in /test/e2e/specs/editor/blocks/list.spec.js, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 1
+ Received  + 1

@@ -5,11 +5,11 @@
      },
      "innerBlocks": Array [
        Object {
          "attributes": Object {
            "anchor": "item",
-           "content": "x",
+           "content": "",
          },
          "name": "core/list-item",
        },
      ],
      "name": "core/list",

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/list.spec.js:2961:41
should select by dragging into separator in /test/e2e/specs/editor/various/multi-block-selection.spec.js, passed after 1 failed attempt.
Error: expect(received).toEqual(expected) // deep equality

- Expected  - 1
+ Received  + 0

  Array [
    1,
-   2,
  ]

Truncated. See the full report.

From 297e871, not the current head. Run

@jasmussen

Copy link
Copy Markdown
Contributor

Nice, at a quick glance this seems good to me. This PR touches only the bulk edit inspector, yes, not the in-editor document inspector?

One curiosity, probably not for this PR, the spacing between slash and slug here feels imbalanced:

image

@verofasulo

verofasulo commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Thanks so much for kicking this off, @jameskoster ! A few thoughts and questions:

  • Consistency across fields: I'm not sure I understand why some fields are directly editable while others use a read-only summary that requires an extra click. I don't think editing frequency is a good reason to use different patterns. Less commonly edited fields can be less prominent, but I'd keep the editing experience consistent and use inline fields throughout.

  • Discussion: I find this more complicated than it needs to be, especially for bulk editing. I'd stick with what WP Admin already does: an "Allow comments" checkbox. We could add some helper text to make it clearer, something like "Let visitors leave comments. Turn this off to hide the comment form." This would also work well for bulk editing, where we could show three clear states: checked, unchecked, and mixed.

  • Link: What does this refer to exactly? Is it the slug?

  • Status: I'd remove the icons. I'm struggling to see what value they add, and I think they make the UI feel a bit overwhelming.

image
  • Excerpt: Why was this field removed?

  • Title: Is there a reason the page title isn't directly editable in the panel? I'd expect to find it alongside the other fields, rather than having to click Rename and edit it in a separate modal. I find the current WP Admin experience much more straightforward in this regard.

image
  • Date field: The current calendar interaction feels quite confusing. The calendar is already visible, but I can only select the date, not the time. To change the time, I have to click the calendar icon, which opens another calendar with time controls. I'm not sure why we need two separate calendars here. I'd expect to be able to select both the date and time in the same place.
image
  • Bulk editing: I'm not quite following how this is supposed to work.
    • Why do some fields disappear, such as Featured image, Template, and Parent? I would expect these to remain available for bulk editing. The only field I'd exclude is the slug/link, since it's unique to each page.
    • There's no concept of a "Mixed" value. For example, if I select two pages with different statuses or authors, the selector simply appears empty. I'd expect to see "Mixed" so it's clear that the selected pages have different values.
image
  • Extensibility: How does this approach scale when we consider extensibility? How and where would extenders add their own fields? Since we're revisiting the panel, I think this is worth considering now. The Fields API was supposed to be targeted for 7.2, although I don't know if that's still the case. cc @oandregal

@jameskoster

Copy link
Copy Markdown
Contributor Author

I'm not sure I understand why some fields are directly editable while others use a read-only summary

One reason is to avoid overwhelming the panel with lots of text. For example the Parent field (which is not used for most pages, in most situations) includes the following help text:

Child pages inherit characteristics from their parent, such as URL structure. For instance, if "Pricing" is a child of "Services", its URL would be pizza.local/services/pricing.
They also show up as sub-items in the default navigation menu. Learn more.

This is useful, and I wouldn't want to remove it from the UI entirely, but it also doesn't need to permanently be on display imo. It adds a lot of noise an draws attention to a typically irrelevant field.

I'd stick with what WP Admin already does: an "Allow comments" checkbox.

I'll give this a try.

What does this refer to exactly? Is it the slug?

Yes. I would personally be in favor of using the term "Slug", but previous feedback deemed it too technical. We've flip-flopped on this a few times so probably a detail to unpack separately with all the associated context.

Status: I'd remove the icons.

Would you also remove them in the status field on the Pages DataView? My feeling is that we should be consistent; show the icons everywhere to reinforce the association, or show icons nowhere.

Excerpt: Why was this field removed?

I think excerpt only shows on posts currently. There is no bulk edit for posts in the site editor.

Title: Is there a reason the page title isn't directly editable in the panel?

I think mainly because bulk editing the title doesn't really make much sense. But perhaps we could show a field when the selection only contains a single item? This would be a different change though so best explored separate.

The calendar is already visible, but I can only select the date, not the time.
Why do some fields disappear, such as Featured image, Template, and Parent?

These are all consistent with trunk, and should be addressed separately. I tend to agree they should all be bulk editable but there's could be a good reason they aren't!

For example, if I select two pages with different statuses or authors, the selector simply appears empty. I'd expect to see "Mixed"

Agree, I'll look into this.

@verofasulo

Copy link
Copy Markdown
Contributor

I think excerpt only shows on posts currently. There is no bulk edit for posts in the site editor.

Hmm, unless it's a bug, I see it in the site editor:

image

I see it in the block editor as well, in the inspector panel:

image

Would you also remove them in the status field on the Pages DataView?

Not necessarily; I think they are different surfaces. I'd personally keep the dropdown cleaner, but I don't have a strong opinion.

I think mainly because bulk editing the title doesn't really make much sense. But perhaps we could show a field when the selection only contains a single item? This would be a different change though so best explored separate.

Yeah, editing the title for a single item only would be the most common action. But as a general rule, I'd keep all fields that aren't unique visible in bulk editing as well, and the title is not unique.

These are all consistent with trunk, and should be addressed separately. I tend to agree they should all be bulk editable but there's could be a good reason they aren't!

Maybe @jasmussen or @oandregal know why?

This is useful, and I wouldn't want to remove it from the UI entirely, but it also doesn't need to permanently be on display imo. It adds a lot of noise an draws attention to a typically irrelevant field.

Hmm, maybe we can find a way to make it a bit less overwhelming?

@oandregal oandregal left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did a first past focusing on implementation. Though I suppose, at this point, you're more interested on the design aspects of this. Feel free to ignore for now.

* radio group the editor's document sidebar uses, with the icon of each
* status next to its label, and its description in the list.
*/
export function StatusSelectEdit( {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I gather this is the Edit component for the status field: it should live in core-fields.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved to core-fields. The status field now ships its own Edit: radios by default (so the editor sidebar is unchanged) and a compact select when the form asks for it via a new form-field config option ({ id: 'status', config: { compact: true } }). Trash is never offered as a choice. Both route-level copies are gone.

Comment on lines +28 to +34
const fieldsWithRegularLayout = [
'status',
'slug',
'author',
'template',
'excerpt',
];

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that we've landed new APIs for extenders to add/update/remove fields and actions for entities in WordPress 7.2. It's through those APIs (core-fields, core-actions packages + view config endpoint) and the view config that we need to make changes going forward.

This info (whether fields are displayed using the regular panel) should live in the view config endpoint. That's what allow us to build a coherent experience (be shared across editor inspector, site editor v1 and site editor v2) as well as offer extensibility for 3rd parties.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, done. The view config endpoint now returns a quick_edit_form next to form (compat 7.3), and both drawers only split it by layout type: regular fields inline, panels pinned below. All the hardcoded field lists, the password reordering, the scheduled-date removal and the status override are gone from the client. Extenders filter it through get_entity_view_config_* just like form. Post types with their own form get no default and the drawer falls back to form. One thing I'd like your eyes on: Gutenberg_View_Config_Data checks keys against self::CONFIG_KEYS, so I added the new key to the 7.1 class (with @since 7.3.0) rather than subclassing. Happy to change that if you'd prefer another approach.

padding-top: $grid-unit-20;
// Password is a field of its own in the quick edit form, so drop the divider
// the editor's document sidebar draws above it inside the status group.
.dataviews-action-modal__quick-edit .fields-controls__password {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we're ready to move this style to core-fields.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than moving it, I removed the divider altogether: the editor sidebar rule (the #75916 TODO) and the drawer overrides are gone, and the core-fields password module only resets the fieldset defaults now.


const fieldsWithBulkEditSupport = [ 'status', 'date', 'author', 'discussion' ];

/*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ignoring the implementation for site editor v2 in this 1st round of review, as it's not important for WordPress 7.2 beta (not becoming stable), but the same comments I mentioned about core-fields, core-actions and view config APIs apply.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same changes applied to v2: it reads quick_edit_form, uses the core-fields status Edit, and has no route-level field logic left.

@oandregal

Copy link
Copy Markdown
Member

Extensibility: How does this approach scale when we consider extensibility? How and where would extenders add their own fields? Since we're revisiting the panel, I think this is worth considering now. The Fields API was supposed to be targeted for 7.2, although I don't know if that's still the case. cc @oandregal

APIs for extending (add/update/remove) fields and actions from PHP landed and will be released with WordPress 7.2. We also have the View Config API since 7.1 (also PHP), which is about providing the form and view configs (for DataForm and DataViews, respectively). I touched on this on my review.

@oandregal

Copy link
Copy Markdown
Member

After my first pass at this the key question I have is: is this something we aim to get ready for WordPress 7.2 (for context, we're past beta 2)? Does revisiting how fields look and are interacted with impact the plans to make the DataForm-driven inspector stable for 7.2 (what I'm looking at here)?

@oandregal

Copy link
Copy Markdown
Member

re: why some fields are not bulk editable.

Not all of them are because it may not make sense (e.g., title, feature image) and fields need to support working with multiple records. It seems template and parent should be bulk editable, and I've prepared #85947 to add them.

How a field declares it's bulk editable is something we need to improve. We have an allowlist of editable fields, but this doesn't scale to fields added by extender (they won't be bulk editable by default). A potential solution is that fields declare if they can be bulk editable, like actions do.

@verofasulo

verofasulo commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

@jay, I explored some of the things I mentioned above in a prototype: https://dataviews-panel-vs-drawer.space.fast/?screen=pages&editView=drawer&plugins=three.

Please ignore that it’s in wp-admin and focus on the drawer. 🙏

  • I added the title and excerpt.
  • I moved the featured image down. It’s one of the least-used fields, so I don’t think it should come first. It looks really good when there’s an image, but most of the time it’s empty. I’d also consider removing the thumbnail from the default table for the same reason. Does it make sense to you?
  • I noticed the date field gets confusing for drafts:
    • The site editor labels it “Modified”, but changing it appears to set the publication date rather than the modified date. After you pick a date, the label still says “Modified”, so it’s hard to tell what you’ve changed.
    • I’d only show an editable date when users can actually set it, with a label that reflects what it controls, e.g. “Published date” or “Scheduled date”.
    • Am I missing a reason to make “Modified on” editable? My understanding is that WordPress sets it automatically on every save, but I might be wrong. cc @oandregal in case you know and I'm missing something 🙏
  • I followed the editor’s approach to expandable/collapsible sections. I think these will come in handy especially if plugins add more fields.
    • Question: can the form config group fields into labeled sections, and can a field say which plugin it came from?
pages-drawer.mp4

@jameskoster

Copy link
Copy Markdown
Contributor Author

is this something we aim to get ready for WordPress 7.2

I don't think it's urgent.


@verofasulo yeah the date field is a bit weird. Iirc it's meaning changes based on status. For drafts it's 'last modified' but for published content it's the publish date. This makes bulk editing the date create some unpredictable results. Maybe it should be conditional; you can only bulk edit the date if the selection contains content with the same status? It's a bit opaque, but probably better than allowing folks to mistakenly publish a bunch of drafts..?

I've said for a while that modified date and published date could probably be separate datapoints, but that's a bigger change.

I followed the editor’s approach to expandable/collapsible sections. I think these will come in handy especially if plugins add more fields.

I don't love panels that contain only a single field. We might as well use the panel field layout in that case? I think this approach (in your prototype) would work better if the panels had semantic meaning so that plugins could add/sort fields in to appropriate panels rather than adding loads more. Maybe they just need different names?

As it stands I do feel the need to point out that this is basically what I was suggesting originally (use panel layout for certain fields), but I thought you disagreed? Or maybe it was just about which specific fields used the panel layout.

I'm still unconvinced about bulk editing the title. I can't think of a single case where you'd want posts/pages/media etc. to have the exact same title :p

@jameskoster
jameskoster force-pushed the update/quick-edit-regular-field-layout branch from 297e871 to 2b6a7f6 Compare November 4, 2026 12:10
@github-actions github-actions Bot added [Package] Core data /packages/core-data [Package] Editor /packages/editor [Package] DataViews /packages/dataviews [Package] Views /packages/views labels Nov 4, 2026
@jameskoster

Copy link
Copy Markdown
Contributor Author

@oandregal thanks for the review! To clarify the target: this is aimed at 7.3, not 7.2, so it shouldn't affect the plan to make the DataForm-driven inspector stable for 7.2. The editor sidebar is untouched apart from dropping the password divider.

On extensibility: the drawer layout now lives in the view config (quick_edit_form), so third parties can add, reorder or re-layout drawer fields with the same filters they use for form. Semantic groupings are follow-up territory (see my reply to Vero).

On bulk editing: thanks for #85947. Whichever PR lands second can rebase; the drawer still filters by the bulk allowlist. I agree fields should declare bulk support like actions do, but I'd keep that out of scope here.

@jameskoster

Copy link
Copy Markdown
Contributor Author

@verofasulo I think there's plenty still to do here, but would consider these follow-up territory:

  • Explore whether to include a title field in bulk edit—it's just not making sense to me so would appreciate wider feedback
  • Unpack the date field and all of its permutations—complex, warrants a dedicated issue
  • Revisit featured image position—I don't know it's reasonable to say it's a "least used" field, this seems highly subjective.
  • Explore semantic field groupings—complex and needs careful planning. (Extensibility is partly covered now: the drawer layout lives in the view config, so plugins can add, reorder and re-layout drawer fields with the same filters they use for the editor form.)

I figured out the excerpt was missing for you because it is not registered for pages by default (only posts). Plugins (commonly Jetpack) add excerpt support to pages, but it's not stock behavior.

@jameskoster

Copy link
Copy Markdown
Contributor Author

Any thoughts on this @WordPress/gutenberg-design ?

@jameskoster
jameskoster force-pushed the update/quick-edit-regular-field-layout branch from 1928cc4 to 114d90a Compare November 13, 2026 20:37
@github-actions
github-actions Bot requested review from aduth and ciampo November 13, 2026 20:37
@jasmussen

Copy link
Copy Markdown
Contributor

Important to me, the in-document inspector should read more like a colophon, and it still does:

2026-11-16 09 03 14 localhost a022df7b63ab

So the inline fields is for bulk editing, where it feels very much appropriate and the right direction:

2026-11-16 09 03 02 localhost e25ac2d26e9e

Two things though:

  • The density of the quick edit modal in general feels too low. It is much airier, and the panel is wider, than the in-editor version. Can they both have the same density? It might even be a good use-case for compact controls.
  • There's something wrong with the author picker, look at the avatar.

@jameskoster

Copy link
Copy Markdown
Contributor Author

Thanks for looking. I updated to use a narrower width token for the drawer, and fixed the author input. Screenshot in the PR description updated.

@jasmussen

Copy link
Copy Markdown
Contributor

Genuinely, that density helped more than I thought it would:

2026-11-18 08 54 44 localhost 87feffe0f87c

What do you think?

The fields are still 40px. I don't think we have to change that in this PR, since there's still whitespace, but it's still something we can consider.

@jasmussen jasmussen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cautious thumbs up.

@jameskoster

jameskoster commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor Author

Open to trying compact inputs separately 👍

One thing I noticed in your last screenshot that looks a little odd is the Template field. Presumably there's no field there because there's no template to swap to, but I wonder if we should still show the select, disabled. I'd appreciate input from @oandregal on this.

@jameskoster

Copy link
Copy Markdown
Contributor Author

One thing I noticed in your last screenshot that looks a little odd is the Template field. Presumably there's no field there because there's no template to swap to, but I wonder if we should still show the select, disabled.

Fixed this; the template select now shows as disabled when it cannot be changed:

Screenshot 2026-11-19 at 15 24 08

jameskoster and others added 8 commits November 19, 2026 15:27
Opening the quick edit drawer is already the choice to edit, so Status,
Password, Link, Author, Template and Excerpt now render their controls
inline. Fields that are edited less often keep their panels, pinned to
the bottom of the drawer above the buttons.

- Status and Author use the UI SelectControl, with an icon per status
  and an avatar per author.
- Password is a field of its own.
- The Link field drops its description, Learn more link and permalink
  preview.
- The parent explanation moves below the control as help text.

Applies to the site editor and the extensible site editor.

See #84391

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The Link field shows the full permalink below the slug input.
- The scheduled date is left out of the quick edit drawer, since the
  Date panel edits the same date.
- The password moves into the panel group, as it is rarely set. Its
  panel summarises whether the post is protected, without revealing
  the password.
- The inline fields get more space above the panel group's border.

Applies to the site editor and the extensible site editor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
The copy button is a minimal, neutral, compact `IconButton` labelled
"Copy". It swaps its icon for a check, or an error icon if copying
fails, for two seconds, and announces the result with `speak()`. It no
longer shows a snackbar, since the button stays visible.

See https://wordpress.github.io/gutenberg/?path=/docs/design-system-patterns-copy-to-clipboard--docs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Applies to the site editor and the extensible site editor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- Add a `quick_edit_form` to the view config (compat 7.3), with a default for post types using the default form, and read it in both drawers, which now only split fields by layout type.
- Let a DataForm form field pass settings to its control through `config`.
- Move the status Edit to core-fields: radios by default, a compact select when the form asks for it, and no Trash choice.
- Remove the password divider from the editor sidebar and the drawers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Narrow the quick edit drawer from 400px to the 320px small surface width token, closer to the editor inspector.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Show the avatar in the author control with the shared AuthorAvatar, like the author view, so the default avatar shown for an author without a Gravatar is no longer rendered at its full size. Space it from the name like the view.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stop marking the template field read-only in the quick edit drawers. Inline, a read-only field shows as plain text; the template control already disables its select on the front page and the posts page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jameskoster
jameskoster force-pushed the update/quick-edit-regular-field-layout branch from 1535e0f to ba03d6f Compare November 19, 2026 15:27

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") Needs Design Feedback Needs general design feedback. [Package] Core data /packages/core-data [Package] DataViews /packages/dataviews [Package] E2E Tests /packages/e2e-tests [Package] Edit Site /packages/edit-site [Package] Editor /packages/editor [Package] Fields /packages/fields [Package] Views /packages/views [Type] Enhancement A suggestion for improvement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants