Everything else seems to be just the same that it used to be, the only improvement is the ability to run it side by side with another Firefox profile but if you used work with Aurora like I did, all this means that you must go back to the beta channel to keep an usable Firefox with a normal UI (after applying the Classic Theme Restorer)
Their "mobile emulator" is quite simple, I don't understand why anyone would like to use it to debug Chrome on Android instead of using Chrome on their computer as it has better tools and surely it will always be integrated better.
And for CSS tweaking I prefer to use Firebug or even the IE11 dev. tools thanks to its great CSS Changes pane.
I come to
/. for the comments, but with the new Beta, I can't even see anything! It just says:
''Shazbot! We ran into some trouble getting the comments. Try again... na-nu, na-nu!
It seems like the "developers" need to take some advice from people who actually know what they are doing. I'm happy to help explain what graceful degradation means if they like...
Link to Original Source
I will not trust in Chrome until they stop adding their plugin into Firefox.
If they care so much about what's run inside Chrome, why do they inject their Google Updater into Firefox and put their update code in a bazillion places?
Yes, they say that it's mean to always have the latest version available, but if I'm not using it daily, why should I waste CPU cicles and bandwith trying to upgrade it until I use it?
I have Chrome installed only because I need to use it for testing, but I strongly dislike its UI and its behavior, I just wish that it would be a normal program that only tries to update itself when I run it.
I use Firefox daily on my Nexus 7 and I think that I haven't ever seen it crash.
When the Jelly Bean 4.2 was released Firefox was one of the apps that required an upgrade, but even then I didn't had a problem because I use the beta so by the time that Google sent the OTA to my tablet Firefox was already updated.
even if Samsung doesn't make an Android tablet,
Besides their own branded tablets, have you checked which is the manufacturer of the Nexus 10 monster (2560x1600 screen, 16Gb at 400$) that comes out tomorrow?
However, on Android I've made far far less revenue on the same apps, only to see my app get 'returned' daily and probably pirated.
So your apps are returned in Android and you blame that on piracy.
But the fact is that the user only has 15 minutes to return the app and if he plans to pirate it, why would he bother on buying it at all?,
Pirates won't ever bother inserting their credit card on Google Play and go straight to the alternative markets and when people are returning your app after just 15 minutes then it's clear that there's something wrong with your app and you shouldn't blame anyone else but you about that
Are your apps those that are simple ports from iOS and that lacks total respect for the Android UI and environment?
It's funny to see how people claim how iOS is much more stylish and when they port an app to Android they try to force such iOS UI and of course people rejects those abominations
Instead of creating your own browser as other people have suggested, you can use an existing app: Kiosk Browser HC, and for a little price (after all you won't pay that so that shouldn't be a worry) there's an improved version: Kiosk Browser SE.
According to the version of the OS and if you can root the tablets or not, that might be all that you need, but if there's some other requirement then check SureLock Kiosk Lockdown
I don't know which browser you're using, but with Firefox it automatically shows a status bar with the destination of the link as soon as I hover it.
Sorry, clicked wrong while moderating the post.
"IE is still easily number one at 50%, while Chrome has 25%."
What's it matter? I'm much more interested in what percentage of web sites are W3C compliant. When that approaches 100%, then browsers will compete on true merit (speed, UI, etc.), not their support of proprietary extensions and how well they put up with badly coded HTML.
I'm sick and tired of "browser x isn't supported," and "this site best viewed with..." crap, which is just indicative of clueless website developers.
And what happens with new sites (specially mobile versions) that use webkit only css features instead of using a standard approach?
Why can't they add the vendor prefix for the other browsers as well?
Although not stated as "best viewed with..." they are hurting the forward development of the web by sticking to just one vendor and we are going to suffer the same IE6 problems that we hate so much, but now it's webkit the culprit
First, bring back the fucking menu bar and the status bar by default!.
Go to the Firefox button, Options and check Menu bar. For the status bar, install the status-4-ever extension
I also thought at the beginning that not having the status bar would mean a lack of UI that I will miss very much, but the fact is that I only really need it while I'm hovering a link and in those cases it automatically pops up, so I'm perfectly happy of not having those pixels wasted.
If you look at other comments, people still complain that there's still too much UI in Firefox, and all the browsers have been focused on cleaning up the UI. There's no reason to keep the same metaphors and UI elements than 20 years ago, browsing the internet should be easy and focused on that: browsing the web, not looking at the UI of the browser. I don't mean that the current trends are perfect, but rejecting any changes doesn't help us to move forward; of course sticking to a very old version and then jumping to the latest one will mean lots of changes but staying updated helps to take the changes little by little.
An example of something that I don't like/understand about the current Firefox is that Panorama thing. It could be useful if it could handle all the Firefox windows and tabs, but instead it just allows to group the tabs inside a window and hide the rest so I did test it a little and then forgot about it. The problem might be that someday they fix it and start behaving really well but I will miss it because they introduced it in a broken state and so I no longer have any interest about it
Google is already serving webkit-only css in the mobile versions, so when people try Firefox mobile those sites don't work as nicely as the default browser in Android, although Firefox is perfectly capable of handling them if they were coded properly.