-
Enhancement
-
Resolution: Unresolved
-
P3
-
8
-
Cause Known
-
generic
-
generic
The specification for Component.revalidate() (introduced with 7036669), as well as that of the invalidate() method is slightly unclear as to whether the invalidation stops on the component itself if the component is a validate root, or goes higher in the component hierarchy to locate a validate root for this component. The actual implementation of the method is that it goes upper in the hierarchy to find a validate root. This behavior is considered correct.
Also, we need to mention the new revalidate() method in the specifications of the rest of validity-related methods (invalidate(), validate(), isValidateRoot(), Component class spec, etc.)
Besides, it makes sense to generally revise the specification of the HW/LW Mixing feature to demonstrate the best practices of (re)validation of component hierarchies after making changes to the layout-related properties of components.
Also, we need to mention the new revalidate() method in the specifications of the rest of validity-related methods (invalidate(), validate(), isValidateRoot(), Component class spec, etc.)
Besides, it makes sense to generally revise the specification of the HW/LW Mixing feature to demonstrate the best practices of (re)validation of component hierarchies after making changes to the layout-related properties of components.
- relates to
-
JDK-7036669 Simplify revalidating component hierarchy with multiple validate roots
- Closed