I did -- https://bugzilla.mozilla.org/show_bug.cgi?id=780999. Please see it.
2012/8/7 Kartikaya Gupta <kgu...@mozilla.com> > Do you have test cases that demonstrate this behaviour? If so, it would be > better to file a bug and attach the test cases, so we can reproduce the > behaviour and investigate it. > > Cheers, > kats > > > On 12-08-02 18:09 , Arthur Stolyar wrote: > >> Hi, all. >> >> I just tested view port meta tag on various devices and browsers. In >> chrome, opera and default browser for Android (4 at Galaxy Nexus) and on >> Blackberry 10 webkit all is good, when we pass in content attribute >> "width=device-width, initial-scale=1.0, user-scalable=no" both browsers >> scales page into screen and pass actual CSS/js width closer to 320 pixels. >> In same time gecko scale page to the view port closer to 320px, but does >> not changes innerWidth/document.body.**offsetWidth to actual size of view >> port (~320 with scale factor ~2). Additionally, Nightly build for android >> have more strange behavior, it just scale page to view port, but do not >> perceives real device dpi or scale factor. So, in media queries Nightly >> always matches like a desktop with 96dpi. >> >> That do you think about this? >> >> > -- @nekrtemplar <https://twitter.com/#%21/nekrtemplar> _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
