I've used Firefox since the time it was called Phoenix. I still use it as my default browser, but there are two quite simple features in Chrome that I'm really missing in Firefox:<p>1. Exemplary implementation of user accounts. I have a separate user account for my private Google account (Gmail, Calendar etc), a second for Facebook, a third for work (separate Twitter and Google accounts) and a third for web development. I know Firefox has a Profile manager and that it is possible to use -no-remote to run several profiles at once. But: it does not work very well at all. Not even with the <a href="https://addons.mozilla.org/en-US/firefox/addon/profileswitcher/" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/profileswitch...</a> addon.<p>2. Incognito window can run in parallel with the "normal" browsing session. This is lovely when I want to see how a website looks in a clean browser. In Firefox the private session replaces the normal session until i chose to go back to "unprivate" again.
This isn't officially released yet.<p>If you're the type who would be willing to install this, you should consider using the Beta channel instead. Beta releases are generally very close to release quality, and you'd help gather telemetry data earlier.
<i>Initial support for the CSS Flexbox Module has been landed. It is disabled by default but can be enabled by setting layout.css.flexbox.enabled to true.</i><p>This is actually a feature I'm waiting to see on at least both Chrome and Firefox (without vendor prefixes). I haven't been tracking the spec closely enough to see how close it is to being finalized since the "new" flexbox model was adopted.<p>Other changes that interest me for fairly obvious reasons:<p><pre><code> Preliminary support for WebRTC.
New HTML scaling algorithm.
Performance improvements around tab switching.
Improvement in startup time through smart handling of signed extension certificates.
Support for W3C touch events impemented, taking the place of MozTouch events.
</code></pre>
The last one for better, less specific Javascript.
Browsers that support TouchEvents:
- Chrome (desktop and mobile)
- Safari (mobile)
- Firefox (mobile, and now desktop)<p>Browsers that support Microsoft's proposed PointerEvents:
- Internet Explorer (desktop and mobile)<p>I get in theory why having a combined touch/pen/mouse API is a good idea, but MS's proposal makes handling multiple touches concurrently much harder than it should be. It'd be nice if they'd get over themselves and implement the same standard as everyone else (especially if they want to be relevant in a world where touch interactions are designed primarily for WebKit, while they have vanishingly low market share in touch-first devices.)
Does anyone know the state of a Modern UI (what used to be called Metro) version of Firefox. I've recently switched to Windows 8 and love it apart from the lack of a native Firefox, obviously I can run the desktop version but I'd rather use the new UI where possible.<p>The last release/mention I found was a preview [1] in October last year and then nothing but tumbleweed ...<p>[1] <a href="https://blog.mozilla.org/futurereleases/2012/10/04/firefox-metro-preview/" rel="nofollow">https://blog.mozilla.org/futurereleases/2012/10/04/firefox-m...</a>
Can anyone confirm whether final flexbox support was added? <a href="http://caniuse.com/flexbox" rel="nofollow">http://caniuse.com/flexbox</a> suggests that FF 18 only has support for the old version of the standard.
> FIXED: Disable insecure content loading on HTTPS pages (62178).<p>Very nice. Check out the test page here: <a href="https://people.mozilla.com/~bsterne/tests/62178/test.html" rel="nofollow">https://people.mozilla.com/~bsterne/tests/62178/test.html</a><p>Also, if you can, switch your site to default to HTTPS (redirect from HTTP to HTTPS right away), especially if you run some kind of an API. I am looking at you Google, with your Charts API. Last I checked the only way to get those via HTTPS was through one employee's epic quest to make their API's HTTPS-capable.
I used firefox up until I ran into a nasty Javascript bug which caused Firebug to conk out, never hitting the breakpoint. I switched to Chrome and the breakpoint was hit every time. I got the overall impression that Firefox's debugging tools weren't as good as Chrome's. Has this changed at all?