-
Bug
-
Resolution: Fixed
-
P3
-
8
-
None
There are several problems with bounds calculation in Parent class:
If several visible child nodes are added at once (getChildren().addAll(...)), some of them may be ignored during Parent bounds calculation:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotIgnoreMultipleAddedNodes
Parent.dirtyChildrenList may be initialized incorrectly which results in incorrectly calculated bounds:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotCreateEmptyDirtyChildrenList
Adding child inside previously calculated untransformed Parent bounds, will leave the transformed Parent bounds (for example boundsInParent) outdated:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotSkipGeomChangedForChildAdditionInsideUntransformedBounds
Removing child inside previously calculated untransformed Parent bounds, will leave the transformed Parent bounds (for example boundsInParent) outdated:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotSkipGeomChangedForChildRemovalInsideUntransformedBounds
Incorrectly calculated bounds have negative impact on other functionality - dirty area management, picking, etc.
If several visible child nodes are added at once (getChildren().addAll(...)), some of them may be ignored during Parent bounds calculation:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotIgnoreMultipleAddedNodes
Parent.dirtyChildrenList may be initialized incorrectly which results in incorrectly calculated bounds:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotCreateEmptyDirtyChildrenList
Adding child inside previously calculated untransformed Parent bounds, will leave the transformed Parent bounds (for example boundsInParent) outdated:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotSkipGeomChangedForChildAdditionInsideUntransformedBounds
Removing child inside previously calculated untransformed Parent bounds, will leave the transformed Parent bounds (for example boundsInParent) outdated:
reproducible by javafx.scene.Parent_recomputeBounds_Test.shouldNotSkipGeomChangedForChildRemovalInsideUntransformedBounds
Incorrectly calculated bounds have negative impact on other functionality - dirty area management, picking, etc.
- is blocked by
-
JDK-8126279 Node.boundsInParent is not updated when Node's geometry changes
-
- Resolved
-
- relates to
-
JDK-8102005 Investigate if clearing of top, left, bottom, right, near, far is needed in Parent.recomputeBounds()
-
- Resolved
-
-
JDK-8100854 Bounds computing on Parent contains a crippled optimization
-
- Closed
-