<AWT Dev> <Swing Dev> Review request: 6852592 (revalidate() must be smarter)

Anthony Petrov Anthony.Petrov at Sun.COM
Wed Jul 15 23:35:04 PDT 2009

On 7/15/2009 11:14 PM Christopher Deckers wrote:
> This may be a stupid idea, so disregard it if it is :)
> If the problem is having isValidateRoot() used by AWT code, why not promote:
> public/protected boolean isValidateRoot()
> to the Container class? It would obviously return false by default,
> but if custom code wants to play with it (which is anyway unlikely to
> happen) why not! After all, is there anything specially swingish with
> this method?
Generally I like the idea. That would make the fix way smaller, and much 
clearer, and would in fact affect only AWT's specification of the 
Component/Container.invalidate() methods.

AWT, do we want to adopt the isValidateRoot() method?

I suspect this happened once before with, say, the isOpaque() method: it 
had had nothing to do with AWT until we recently overrode it in the 
Window class. But still the method is present in the Component class 
since JDK 1.2.

best regards,

More information about the awt-dev mailing list