How do you find out if a bug has been fixed?
Sergey Bylokhov
Sergey.Bylokhov at oracle.com
Tue May 28 05:37:03 PDT 2013
Hello.
I trace down this bug and found that part of the issue is in the CAlayer
implementation. The reason is simple: setNeedsDisplay is not followed by
the drawInGLContext.
The problem is not reproduced if i set layer.asynchronous from FALSE to YES.
On 23.05.2013 22:22, David DeHaven wrote:
> I don't think it's fixed, I still see it with b90. In a lot of cases I don't even see the buttons to be able to click them.
>
> -DrD-
>
>> It should show up at bugs.sun.com as resolved.
>> Since 8014369 bug is marked unresolved, its not likely its fixed,
>> unless by amazing chance it was fixed under a different bug ID
>> at around the same time you submitted your report.
>>
>> -phil.
>>
>> On 5/23/2013 6:21 AM, Mickey Segal wrote:
>>> The bug “Intermittently only some components refresh” at http://bugs.sun.com/view_bug.do?bug_id=8014369 shown at http://www.segal.org/java/refresh4/ seems fixed in JRE 8 early release build 90.
>>>
>>>
>>> In general, how does one learn a bug is fixed? I was impressed with the level of interest shown in this bug by people at Oracle so I’ve been checking the JRE 8 early release builds and pleased to see that it seems to have gotten fixed so quickly. Is that the only way one finds out a bug is fixed? The Sun bug page still lists it as unresolved.
>>>
>>>
>>> I’ll ask one of our users who has the problem worse than others check to see if the bug is gone for him too. Presumably he has a slower computer and ran into the timing problem worse than others. When the fix comes out in JRE 7, does he switch back to JRE 7 by removing all Java versions and installing the latest version of 7?
>>>
>>>
>>>
>>>
--
Best regards, Sergey.
More information about the macosx-port-dev
mailing list