alex Posted December 11, 2013 Share Posted December 11, 2013 Hi, I have a problem with the latest firefox (android) release. I seems that the innerheight is wrong and reports the size of the whole window without the adressbar - but the adressbar is still visible... e.g. s4 in landscape mode:starting game with innerheigt 287 (seems okay)than I am getting a resize event and now the innerheight is 335 (would be correct if the top/adress bar disappeard, but it is still there...)(using <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">) Maybe the error is somewhere else and my code is wrong but it works for chrome, stock browser and safari (ios)... Thanks, alex Quote Link to comment Share on other sites More sharing options...
James Cat Posted December 11, 2013 Share Posted December 11, 2013 Yeah, I got a similar issuehttp://stackoverflow.com/questions/19162794/browser-window-height-on-mobile-firefox-v23 no one gave me any clues, I suspect is is to do with the scaling/zooming being worked out in some 'virtual pixels' way, I had a few problems with absolute positioning of html elements in FF on android. sorry can't be more helpful, but you're not alone. Quote Link to comment Share on other sites More sharing options...
alex Posted December 11, 2013 Author Share Posted December 11, 2013 >>but you're not alone Good to know Maybe I can describe my problem a little more in detailed:I think the problem with the wrong innerHeight started some time ago - maybe with firefox 23...First I tried to ignore the resize event. But this wasn't a good solution and I changed the body height to 'auto' - before that it was >100% because of an safari/ios issue -So this wrong(?) resize event wasn't triggered anymore and I was happy.But now the resize event is triggered again and causing again some trouble... Quote Link to comment Share on other sites More sharing options...
chrismendis Posted May 27, 2014 Share Posted May 27, 2014 Checked in with the Firefox Mobile devs on IRC today. Turns out that this is known bug that they wontfix. See https://bugzilla.mozilla.org/show_bug.cgi?id=923663 and https://bugzilla.mozilla.org/show_bug.cgi?id=943921. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.