Open draganescu opened 2 days ago
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot
label.
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: draganescu <andraganescu@git.wordpress.org>
Co-authored-by: fabiankaegy <fabiankaegy@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.
Size Change: +47 B (0%)
Total Size: 1.81 MB
Filename | Size | Change |
---|---|---|
build/editor/index.min.js |
106 kB | +47 B (+0.04%) |
Flaky tests detected in e8896b91766222b63e87d8bc9bb0f19974b435db. 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.
đ Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11594426519 đ Reported issues:
/test/e2e/specs/editor/various/taxonomies.spec.js
Follow up to #65732
Currently there is a hardcoded check for certain post types to see if we should offer users the zoomed out view or not. Ideally this decision should be based on an ability of the currently edited post type.
This PR adds a new post support to a few core post types, a post support named "content".
It then checks if the currently edited post has this new content support.
Context: