Page: remove destroyed detail form and table from page #982
Conversation
This file contains 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
A page may reference a detailForm or a detailTable. If the corresponding
widget is destroyed, the member should also be set to null. Otherwise,
it may happen that the destroyed widget is still accessed, creating the
potential for unexpected errors ('Widget is destroyed').
For example, if a node page with both a detail form and a detail table
is destroyed while still being selected, the DesktopBench will be
triggered by a pageChanged event and tries to update the outline content
with an already destroyed widget.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A page may reference a detailForm or a detailTable. If the corresponding widget is destroyed, the member should also be set to null. Otherwise, it may happen that the destroyed widget is still accessed, creating the potential for unexpected errors ('Widget is destroyed').
For example, if a node page with both a detail form and a detail table is destroyed while still being selected, the DesktopBench will be triggered by a pageChanged event and tries to update the outline content with an already destroyed widget.