Just a precision about my last message. As I said, the button displayed the overSkin instead of the upSkin. The mouse was outside of the browser window.
I think that when I click for the second time on the toggle Fullscreen button, the app change the stageDisplay value but doesn't refresh the mouse coord because the cursor is outside of the flash movie. So flash keep the old value and that means "over the button". What do you think ? --- In [email protected], "liloosweet" <liloosw...@...> wrote: > > This is the application before I do anything: > http://img34.imageshack.us/i/capture1yb.png/ > <http://img34.imageshack.us/i/capture1yb.png/> > > Then I toggle the button two times by clicking on the button: > http://img151.imageshack.us/i/capture2pu.png/ > <http://img151.imageshack.us/i/capture2pu.png/> > > The button skin is its overSkin. > > --- In [email protected], "valdhor" <valdhorlists@> wrote: > > > > I tried your example on my system (Windows XP, Firefox 3.6.3, Flash > Player WIN 10,0,45,2) and I don't see any bugs. What do you see? > > > > > > > > --- In [email protected], "liloosweet" liloosweet@ wrote: > > > > > > Hello there. > > > > > > I'm experiencing a bug with non-IE browsers (firefox, opera, chrome, > > > ...) and wondering if it's a Flash or Flex bug or a browser issue. > What > > > do I need to do to solve that ? > > > > > > Quick version: here is the example showing the problem > > > http://devenirlibre.com/fullscreen/FS.html > > > <http://devenirlibre.com/fullscreen/FS.html> > > > > > > More detail: > > > I have a fullscreen button. It's state is linked to the DisplayState > > > value. > > > > > > I made a example to show you the problem. It's based on a flex > example > > > source : > > > > http://blog.flexexamples.com/2007/08/07/creating-full-screen-flex-applic\ > \ > > > ations/ > > > > > > I just changed moved the button to the top of the Application, give > it > > > an id (button) plus the following: > > > > > > private function fullScreenHandler(evt:FullScreenEvent):void { > > > dispState = Application.application.stage.displayState + " > (fullScreen=" > > > + evt.fullScreen.toString() + ")"; > > > if (evt.fullScreen) { > > > /* Do something specific here if we switched to full screen mode. */ > > > } else { > > > /* Do something specific here if we switched to normal mode. */ > > > } > > > } > > > > > > to > > > > > > private function fullScreenHandler(evt:FullScreenEvent):void { > > > dispState = Application.application.stage.displayState + " > (fullScreen=" > > > + evt.fullScreen.toString() + ")"; > > > if (evt.fullScreen) { > > > button.selected = true; > > > } else { > > > button.selected = false; > > > } > > > } > > > > > > To see the bug, make sure that the place where the button is when > > > fullscreen is outside the browser content window when normal. I hope > it > > > make sense. > > > > > > Here is the example: http://devenirlibre.com/fullscreen/FS.html > > > <http://devenirlibre.com/fullscreen/FS.html> > > > > > >
