On Mon, 9 Nov 2020 13:56:33 GMT, Andy Herrick wrote:
> JDK-8189198: Add "forRemoval = true" to Applet APIs
@andyherrick can you enter the `/csr needed` command? I would, but it needs to
be done by either the author of the PR or a Reviewer.
-
PR:
On Thu, 12 Nov 2020 20:48:13 GMT, Andy Herrick wrote:
>> JDK-8189198: Add "forRemoval = true" to Applet APIs
>
> Andy Herrick has updated the pull request with a new target base due to a
> merge or a rebase. The incremental webrev excludes the unrelated changes
> brought in by the
> JDK-8189198: Add "forRemoval = true" to Applet APIs
Andy Herrick has updated the pull request with a new target base due to a merge
or a rebase. The incremental webrev excludes the unrelated changes brought in
by the merge/rebase. The pull request contains six additional commits since the
On Mon, 9 Nov 2020 13:56:33 GMT, Andy Herrick wrote:
> JDK-8189198: Add "forRemoval = true" to Applet APIs
Since all APIs in the java.applet package are deprecated "forRemoval = true",
consider adding a brief deprecation note to java/applet/package-info.java too.
As an example, when all of
On Mon, 9 Nov 2020 13:57:32 GMT, Andy Herrick wrote:
>> JDK-8189198: Add "forRemoval = true" to Applet APIs
>
> preliminary changes for JDK-8189198 for evaluation
The following field, which is currently deprecated (not for removal) should
probably also be marked as deprecated for removal::
JDK-8189198: Add "forRemoval = true" to Applet APIs
-
Commit messages:
- Merge branch 'master' into JDK-8189198
- JDK-8189198: Add "forRemoval = true" to Applet APIs
- JDK-8189198: Add "forRemoval = true" to Applet APIs
- JDK-8189198: Add "forRemoval = true" to Applet APIs
On Mon, 9 Nov 2020 13:56:33 GMT, Andy Herrick wrote:
> JDK-8189198: Add "forRemoval = true" to Applet APIs
preliminary changes for JDK-8189198 for evaluation
-
PR: https://git.openjdk.java.net/jdk/pull/1127
On Thu, 12 Nov 2020 08:46:36 GMT, Sergey Bylokhov wrote:
> The new test added in JDK-8211999 hits a bug on Linux (in mach5 it is passed
> on ubuntu 18.04 and failed on 20.04). The problem is that the bounds of the
> fullscreen frame include insets of the frame additionally to the screen size.
On Thu, 12 Nov 2020 08:46:36 GMT, Sergey Bylokhov wrote:
> The new test added in JDK-8211999 hits a bug on Linux (in mach5 it is passed
> on ubuntu 18.04 and failed on 20.04). The problem is that the bounds of the
> fullscreen frame include insets of the frame additionally to the screen size.
Printing text using GlyphVector outline has bad quality on printers with low
DPI on Windows.
The GDI system used for text printing on Windows accepts only integer path
coordinates.
Rounding GlyphVector outline coordinates leads to distorted printed text.
To reproduce the issue run the
The new test added in JDK-8211999 hits a bug on Linux (in mach5 it is passed on
ubuntu 18.04 and failed on 20.04). The problem is that the bounds of the
fullscreen frame include insets of the frame additionally to the screen size.
The behavior of the decorated full-screen window is not
11 matches
Mail list logo