X3Photo Gallery Forums

Evening !
I just encountered a bug(?) or maybe it comes from my firefox version...

I set up a possible full screen mode at start using the click parameter over the filemod image which is my start page.
Then when in fullscreen with firefox 3.6.13 everything seems to be frozen, menu is inactive, right-click too...
If I start the visit in normal mode through the menu and then later go fullscreen, firefox handles it fine.

I also tried it under google chrome and it works fine...
So I'm a bit puzzled about to find what is causing this issue.
Anyone has encountered the same prob ?

you could check it here :www.nz-photo.com

Thanks !

So... no Firefox users facing the same prob ?

Hi Karl !
Thanks for checking !
Though I'm on FF 3.6.13 here too and anytime I use the "click on the home page picture" to start in fullscreen mode, menu is frozen.
Whenever I go on Fullscreen from the home page using rightclick mouse or from any image pages (using control buttons) or via rightclick too it's working fine...
That's why I'm so puzzled about that.
Maybe I did mistake the home page parameter : I use click=togglefullscreen
Am I right ?

mjau-mjau wrote:I tried again, and it still works fine here if the first thing I do is click your "home page picture" ... It goes fullscreen, and everything works as it should. I am not quite sure why you are experiencing something else ...

Thanks again. Indeed I really dont understand why...

mjau-mjau wrote:Perhaps try to make a text link in your description on your start page instead? See if it works better ...

Code Select all

<a href='asfunction:_root.togglefullscreenfunc'>here</a>

I followed your advice and it does work fine. So right now I'm sticking to this option. Thank you for the code tip.

mjau-mjau wrote:You could probably use the link butto in the text editor, and simply input:

Code Select all

asfunction:_root.togglefullscreenfunc

Well ... have to say that I don't really understand what you mean with that link button... Anyway 1st option is ok.

I've asked to my bro' to check that pb and he did report the same issue I had... So may not be only from my FF configuration.
I'll be looking forward to find what it could be and let you know if I find sumthing.