Fix early authenticated notices on fresh route loads (1.6.157) - #131
Merged
Merged
Conversation
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
1 participant
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.
Result\nFix the v1.6.156 QA 8080 fresh direct-URL permission notice overlap: mount the existing jGrowl instance when the authenticated template is actually inserted, and return it to the body on teardown. No API or authorization policy changes.\n\n## Evidence\n- QA v1.6.490 / Web 1.6.156 direct readonly Stack-create URL: notice remained under BODY/fixed and covered right-side actions; same-page transition worked.\n- Chrome 153 targeted growl tests 7/7 and require-create-permission tests 5/5 on this branch.\n- Packaged Server/browser QA remains pending and is not claimed by this PR.\n\n## Release\nBump to numeric Web Console 1.6.157; update README, release notes, package lock/baseline and version checks.