Thank you for the report, Jason. I've just re-opened the issue and
targeted it for JDK 9 for now. The fix may eventually be backported to a
JDK 8 update release, but it needs to be fixed in 9 first.
This mailing list is the best place to discuss possible approaches for
fixing this bug. And you're welcome to suggest a solution and contribute
a fix for it. Please make sure you've read the document that I referred
to in my previous reply and sign your OCA. After that we'll be able to
accept the contribution. Note that you can start discussing the fix
right now. The OCA is only needed to accept a patch from you.
I'm also CC'ing Alexander Scherbatiy who is the nominal assignee for
this bug and will be sponsoring your contribution once you come up with
a solution for this issue.
--
best regards,
Anthony
On 4/18/2014 2:12 AM, Jason Mehrens wrote:
Anthony,
Using the testcase from the bug report I can reproduce the error on Java 8.
This bug in the ToolTipManager is really about how the mouse events are
not fired when something happens to the z-order. When the modal dialog
is shown the mouseExited is not fired even though that modal dialog is
now the only thing I can interact with. The patch for the symptom was
to hide the tooltip when initiateToolTip was called and this condition
was detected. I would think that would be pretty easy to get approved.
However, fixing the root cause requires a bunch of thought and debate on
what determines the mouse being contained in a component (X-axis and
Y-axis only or X,Y,Z-axis).
Thanks,
Jason
> Date: Fri, 18 Apr 2014 01:22:39 +0400
> From: anthony.pet...@oracle.com
> To: jason_mehr...@hotmail.com; swing-dev@openjdk.java.net
> Subject: Re: <Swing Dev> JDK-6219960 null reference in ToolTipManager
>
> Hi Jason,
>
> Is this bug still reproducible with Java 8?
>
> Also, if you want to contribute a patch, please read
> http://openjdk.java.net/contribute/
>
> --
> best regards,
> Anthony
>
> On 4/18/2014 1:14 AM, Jason Mehrens wrote:
> > Hello swing-dev,
> >
> > I'm the submitter of the testcase for bug id 6219960 and I had also
> > submitted a patch for this issue. However, I noticed that this is
> > closed as won't fix. Is this in error? If so I can resubmit the patch.
> >
> > Thanks,
> >
> > Jason
