On Tue, 1 Feb 2022 18:38:39 GMT, Dmitry Batrak <dbat...@openjdk.org> wrote:
> The proposed fix makes fonts with and without fallback components > distinguishable (in terms of `equals` method), so that > font metrics cache (and other similar code) can handle them separately. This > is achieved by adding a new boolean field > to `Font` class, specifically denoting fonts with fallback components. The > latter ones don't need to pretend to be > 'created' fonts anymore, to preserve their `Font2D` handle. > It's not possible to use the existing `createdFont` field in `equals` > implementation, as JCK requires a 'real' created > font (the one obtained using `Font.createFont` method) to be equal to the > same font after serialization and > deserialization. This pull request has been closed without being integrated. ------------- PR: https://git.openjdk.org/jdk/pull/7313
