-
Notifications
You must be signed in to change notification settings - Fork 1.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
Staleness indication inconsistency misapplied to layouts based on navigation. #7670
Closed
2 of 7 tasks
Labels
Milestone
Comments
VIPER 7670 |
Assigning to @jvigliotta |
14 tasks
jvigliotta
added a commit
that referenced
this issue
May 31, 2024
…7736) * clear any staleness subscriptions before viewing a new object * add checkbox to options for createDomainObjectWithDefaults, update swg staleness provider to use new time api, add test * revert * modified for simplification and to remove the need to update helper methods * consistent naming convention * Update e2e/tests/functional/staleness.e2e.spec.js Co-authored-by: Jesse Mazzella <[email protected]> * adding back vars that were removed --------- Co-authored-by: Jesse Mazzella <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The display gets confused when to show / not show staleness indicator after visiting stale providing object in navigation.
I theorize that pub/sub isn't un-subbing somewhere.
Expected vs Current Behavior
If you are on a Display layout where one object/component goes stale, only that component indicates staleness. What I'd expect.
But, if you visit that object directly on the browse navigation (outside a display layout), there after, the staleness affect not only appears on the object/component but the whole display layout whether the object/component is part of the display layout or not. If it is part of the layout, the layout is stale and the subcomponent is stale as well. This seems incorrect.
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: