-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update: Simplify some permission checks. #63812
Update: Simplify some permission checks. #63812
Conversation
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -29 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
This PR had a weird/negative impact on the "navigate site editor" metric. Any ideas what that might be? |
Probably two additional We need to re-evaluate global style selectors and allow |
@youknowriad, create a follow-up to see if we can improve performance - #65177. |
Simplifies some permission checks by using canUser instead of checking capabilities directly which is not as reliable (e.g: may not take into account some backend filters).
Props to @Mamaduka for the research that led to this PR.
Testing Instructions
I checked the editor still works as expected.
With an author role, I checked in the developer tools that there are no 403 HTTP errors while opening the editor.