-
Notifications
You must be signed in to change notification settings - Fork 468
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
Inconsistent Image Loading When Switching Between Preview,Live,Edit Modes #31362
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
#30991 (comment)
Problem Statement
content returned by the API reflects the selected mode. However, there is an issue where images are sometimes displayed from a previously selected mode instead of the current one.
This suggests a race condition or incorrect execution order when setting the session variable that defines the active page mode. As a result, when switching modes:
• Images may load from the previously viewed mode instead of the current one.
• A user switching to Live Mode may still see an image from Working Mode if they had previously viewed that mode.
• Conversely, when switching to Working Mode, an image from Live Mode might still be displayed.
This behavior indicates that the API calls responsible for setting the session variable for the page mode might not be executed in the correct sequence or may be experiencing delays that lead to inconsistent caching or session states.
See:
TM-cache.mov
Steps to Reproduce
Acceptance Criteria
Images should always load according to the currently selected preview mode.
• There should be no persistence of images from previously viewed modes.
• Switching modes should trigger a clear update of the images.
dotCMS Version
current trunk
Proposed Objective
User Experience
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: