back to front?
"He added that some Macbooks detect the orientation information backwards, which is something Mozilla is also working on"
Surely something Apple should be working on.....
Anon - cos I don't want to face the fanbois
The next iteration of Firefox will be able to detect the orientation of laptops and mobile devices that come loaded with accelerometers. Mozilla said yesterday that Firefox 3.6 would carry support for web pages to read machine orientation details, if available on the device. It created the device API to allow users to work …
''nifty for rotating the user interface based on the orientation of a mobile device''
Yes indeed bloat, certainly on a mobile, because correct me if i'm wrong, but won't most devices that detect orientation already change the display accordingly? So would tilting the device 90 degrees left result in firefox mobile being upside down?
Just a thought..
Excellent news. That's way more important than, for example, fixing the fact that the autoupdate mechanism is completely borked if you happen to be one of those people who think running a web browser with full administrator rights is a bit retarded. Way to prioritise feature development!
The point is not to have he browser rotate it's chrome (that's done by the O/S as suggested), but to provide an API that apps in the browser can use to (for instance) change from portrait-based icon GUI to landscape-biased buttons-with-text GUI (thus making better use of the horizontal space).
Most of our icons are square anyway, so it shouldn't make a difference.
The browser would be better just to handle "narrow" resolutions in the way it shows their toolbars etc. They do that now, by hiding the icons in the spill over in a new popup menu... I think that will suit most people when they turn their laptops for... a few minutes.
Anyways, how are you going to click anything whilst you are holding your laptop on its side?
What if I wanted to lie on my side, using the laptop... I would now need to site up to lie on my side ;)
Even though its a point, I think its pointless.
Bloat, bloat, bloat, bloat.
I'm still using FF 184.108.40.206 on both my G4 tower and G4 iBook, as FF 3.0 was absolutely dog-slow -- not to mention that there's no way to get rid of those goddamn' thumbnail site icons in the Bookmarks menu which, I'm quite sure, is what's slowing things down in FF 2.x and is what almost always sent FF down in flames in early versions of 2.x and 3.x.
I tried a later version of FF 3.x on my iBook and, while it was able to access the Bookmarks menu without crashing -- which is what almost invariably happened as it tried to load all those goddamn' icons next to the site names -- I still had to wait several seconds while FF grunted and groaned as the Bookmarks menu crawled down the screen.
I got rid of FF 3.x pronto, and have gone back to 220.127.116.11, which can at least load that needlessly icon-loaded Bookmarks menu without crapping its drawers.
FF is still my main browser, but I've found myself occasionally tinkering with Opera while waiting for something better as, sadly, Mozilla seems determined to send FF down the road to ruin.
Why the hell haven't they fixed the AutoUpdate/phone-home "feature" in 2.x yet?
Are any other FF 2.x users here noticing how -- even if you explicitly turn off auto-update in the Preferences -- FF 2.x still insists on trying to contact mozilla.org for an auto-update? It doesn't happen _very_ often, but on a regular basis; I'll be happily browsing along, and all of a sudden a message pops up from Little Snitch telling me that FF wants to contact addons.mozilla.org. Not catastrophic, mind you, but still annoying as hell, especially when I went to the Prefs and specifically turned the goddamn' auto-update _off_.
Jayzus, you guys, get with the goddamn' program, already.
Biting the hand that feeds IT © 1998–2019