Steps to reproduce:

1. Download the attached test.* files to a directory accessible via a web-server (via http:// ..)
2. Execute the following commands:
   $ cd <to-that-directory>
   $ javac test.java
   $ jar cf test.jar test.class
3. Open a web-browser and navigate to the test.html file via http:// protocol.
4. Accept all the security warnings and/or change the settings in the Java Control Panel to allow the applet to run.
5. Move the mouse around the applet stage and observe that the buttons provide visual feedback when they're hovered with the mouse cursor.
6. Click the Toggle button to enter the full screen mode.
7. Observe that in the full screen mode the buttons do not render the hover effect.
8. However, the buttons do process mouse events: you can click the Toggle button again to return to the windowed mode.

Notes:

1. This bug may be Mac-specific. I've only tested it on Mac (OS X 10.8.2) using the Firefox browser. I can reproduce it with 8u40b02.

2. If you hack Glass code and ensure that the window created in GlassViewDelegate.m -enterFullScreen method doesn't actually enter the full screen mode and remains a regular top-level window, you may notice that when you move the mouse over the buttons in this new top-level window, all the graphical updates get sent to the browser window - i.e. the buttons there render the hover effect, etc. (you may need to move the browser window in order to observe the two windows at once)