Visible load-permission error in builder (human-mode finding) - #65
Merged
Merged
Conversation
…-mode permission specs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Human-mode test: an author opening someone else's page in the builder previously saw an empty canvas with a 403 swallowed in a catch — confusing and looking like an empty page. Now loadPost surfaces a visible role=alert error (permission or generic load failure). New e2e/permissions.spec.ts runs both human paths: author blocked (403 + alert) and author compiling+saving own page end to end. Suite 39/39.