> On Aug 28, 2025, at 8:20 PM, Prasanta Sadhukhan <[email protected]> > wrote: > > I dont think its a workaround...
What I did was a workaround because I was not changing the JDK but getting my code to work on the existing JDK. What you are doing is a bug fix. > The `layoutManager` can be either horizontal or vertical and we are updating > the components based on the current layouting..It's only we are using the > currently existing property but the contents is exactly what we want it be > done even if it were to be a new property. The fact that it “does what you want” even though it is a false change is a hack, in my opinion. By the way, generating a change event that was not previously generated (and is not specified to be generated) is a potential incompatibility. That sounds like reason enough to request a CSR. Maybe they will say it is fine... > Other suggestion i.e using new property or public method will need a CSR to > our java spec which will prevent it from backporting this fix to previous JDK > versions > I’m not familiar with the details, but I would think that requesting a review by itself would not prevent a backport, but the result of the review might state that the change should not be backported. Perhaps a CSR expert could comment?
