On 10/26/2017 12:45 PM, Sergey Bylokhov wrote:
On 26/10/2017 08:26, Semyon Sadetsky wrote:
The existing applications will use the new functionality which
behaves like the old ones. The appearance of the message itself will
differ but after the fix it will look like the native message, even
before the fix the appearance was different on different platforms.
I'm not sure that it will behave as before since that was a swing
component which uses Swing L&F, so at least the appearance is changed
by the fix >
Yet another thing is localization. Before the fix the message was
shown in java locale which may differ from the native locale, now it
is always follows the native locale and there is no way to change it
from java.
The things above are purpose of the fix - to look identical to a
native applications(appearance, location and behavior).
The old implementation of this class via Swing was just a stub which
was implemented to fill the gap in API between jdk6 and 7. Since this
is awt component it should be implemented via the native API.
This may cause unexpected changes in the existing applications, so I
suppose it is reasonable to introduce a compatibility property that
allows switching to the previous behavior. At a minimum, this should
be mentioned in compatibility section of the release notes.
I'll create a release notes subtask, do you have some other comments?
Thanks. Looks fine to me.
--Semyon
