*Andy Goryachev
*Cc: *openjfx-dev
*Subject: *[External] : Re: Enhanced Text/TextFlow APIs
In most cases, I would advise against having similarly-named methods
that exhibit different semantics. If the behavior of the existing
methods is indeed a bug (and not just different, but legitimate
semantic
good compromise - things get fixed without immediately
breaking the existing apps, a win-win.
Cheers,
-andy
From: Michael Strauß
Date: Monday, July 7, 2025 at 19:41
To: Andy Goryachev
Cc: openjfx-dev
Subject: [External] : Re: Enhanced Text/TextFlow APIs
In most cases, I would advise ag
In most cases, I would advise against having similarly-named methods
that exhibit different semantics. If the behavior of the existing
methods is indeed a bug (and not just different, but legitimate
semantics), then fixing that would be best. We've done breaking
changes in the past where appropriat
ncement - P4)
· JDK-8358000<https://bugs.openjdk.org/browse/JDK-8358000>: Enhanced
Text/TextFlow APIs (CSR)
