7 ms·
Firefox 18
- mcpherrinm 14y agoThis isn't officially released yet. 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.
- freditup 14y agoI've been using the beta channel since FF6 (maybe) and, as you said, it's been quite reliable. It's fun because you feel like you're somehow an insider and privileged because you get features (that no one but you would care about!) earlier than everyone else. Yes, these are quite silly feelings, but what the heck.
- corin_ 14y agoSounds like you might enjoy the Nightly channel, in my experience it's been pretty stable.
- zanny 14y agoAurora is a good compromise. I was on nightly for a few months, and I had one or two times where something would break. Usually it was just a GUI element getting misaligned from some change. The worst was when it broke web video for a day. I wish there was a reliable Aurora channel on Arch. The pkgbuild system isn't well suited to keeping up to date with a moving filename target like Firefox.
- zobzu 14y agoI agree, nightly does break badly from time to time. Beta or aurora are better bets.
- ck2 14y agoI've switched to Aurora for the past month and it's noticeably faster than FF18b on my older hardware.
- zalew 14y agoI've used Aurora for some time, extensions often get borked or don't work, so I went back to Beta. btw one tip for people who switch to beta/aurora - disable extensions compatibility check.
- km3k 14y agoThere's an Arch developer named heftig who maintains a custom repository with Aurora. I've been using it successfully the last few months. I think aurora is updated daily, but I haven't watched it closely. Info: https://bbs.archlinux.org/viewtopic.php?id=117157 https://bbs.archlinux.org/viewtopic.php?id=117157 Repo 32-bit: http://pkgbuild.com/~heftig/repo/i686 http://pkgbuild.com/~heftig/repo/i686 Repo 64-bit: http://pkgbuild.com/~heftig/repo/x86_64 http://pkgbuild.com/~heftig/repo/x86_64
- rammark 14y agoAnother option is to download the latest build [1] and use the built-in updater. [1] https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-aurora-linux64/ https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-bu...
- naner 14y agoThey do this every time: Make a news event around the appearance of a new Firefox release on the FTP site before it is officially announced/released. Although this stunt seems considerably stupider now that everyone running a recent version of Firefox will automatically get updates...
- instcode 14y agoIf anyone decides to change the release channel, you can do it now by modifying 'app.update.channel' in about:config to nightly, aurora, beta... Update: http://support.mozilla.org/en-US/questions/940799 http://support.mozilla.org/en-US/questions/940799
- evanw 14y agoI'm on the stable release, and I just got the v18 release by going to Help --> About and installed the automatic update. Their release notes also indicate that version 18 is now released as well: https://www.mozilla.org/en-US/firefox/18.0/releasenotes/ https://www.mozilla.org/en-US/firefox/18.0/releasenotes/
- Posibyte 14y agoInitial 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. 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. Other changes that interest me for fairly obvious reasons: 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. The last one for better, less specific Javascript.
- lillycat 14y agoFirefox implements it without prefix (it is finalized). It will be enabled by default in Fx 20. It supports both horizontal and vertical flexboxes but not yet multiline flexbox. Opera supports it fully and without prefix too. Webkit tends to be (very) late in unprefixing (they are the only ones with prefix for Animation, Gradients, Transitions nowadays.)
- michael_miller 14y agoCan anyone confirm whether final flexbox support was added? http://caniuse.com/flexbox http://caniuse.com/flexbox suggests that FF 18 only has support for the old version of the standard.
- Posibyte 14y agoAs referenced from Mozilla[1], Firefox and Opera support the new spec without prefix, Chrome supports it with the -webkit prefix, and Internet Explorer supports the old-flexbox. [1]: https://developer.mozilla.org/en-US/docs/CSS/Using_CSS_flexible_boxes https://developer.mozilla.org/en-US/docs/CSS/Using_CSS_flexi...
- michael_miller 14y agoThat page says it's behind a developer flag, and only limited single-line support is provided. Is the page up to date, or is the feature fully implemented, and accessible to anyone, regardless of flags?
- noibl 14y agoAccording to the channel on freenode, full, up-to-date, and prefix-free flexbox support is on track to be enabled in the stable version of Firefox that is released exactly 12 weeks from tomorrow.
- fyolnish 14y agoFirefox version numbers could hardly be any more meaningless.
- depr 14y agoLet's not have this discussion again.
- Already__Taken 14y agoA > B is the only thing that matters. Anything else is bullshit that you can't trust and still have to read the patch notes for anyway.
- sp332 14y agoCorrect, which is why Mozilla themselves removed most of the version numbers from their website, and you have to go digging in sub-menus to find out which version you're running.
- bsimpson 14y agoBrowsers that support TouchEvents: - Chrome (desktop and mobile) - Safari (mobile) - Firefox (mobile, and now desktop) Browsers that support Microsoft's proposed PointerEvents: - Internet Explorer (desktop and mobile) 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.)
- pilif 14y agoIsn't there a patent by apple related to the touch events that makes it unsafe and risky to implement them? http://blog.jquery.com/2012/04/10/getting-touchy-about-patents/ http://blog.jquery.com/2012/04/10/getting-touchy-about-paten...
- meaty 14y agoDoes this apply in the EU?
- pilif 14y agoIt might or it might not. In theory, we don't have software patents, but some tend to still slip through (maybe this one did? I don't know). It's totally beside the point anyways because the moment as a browser maker has an office in the US and is distributing the infringing software there, they can be sued there. MS, as far as I remember, has an office in the US :p
- josteink 14y agoFrom what I've heard Microsoft's PointerEvents offer a better complete model, without creating a web-standard which involves risks of getting sued by Apple should you ever dare to implement it. For once, it seems Microsoft has a better option. And no, just because it's in WebKit doesn't make it better, much less an official standard. WebKit is the new IE and it's destructive for the web. People design for "Webkit" as if it was the standard, and expect everyone else "to eventually come along". We did see how well that plays out not that many years ago, but then we did it for MSIE. As a 5 minute user of Firefox mobile, I can attest to this happening right now. The mobile web is at this point not even usuable on a non-webkit browser. This is bad for the web. You are doing it. Please stop doing it. The only thing good for the web is following web-standards. If you're not complying to them, you are doing something wrong, and I don't care what your reason is: You are doing something wrong.
- unicornporn 14y agoI'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: 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 https://addons.mozilla.org/en-US/firefox/addon/profileswitcher/ https://addons.mozilla.org/en-US/firefox/addon/profileswitch... addon. 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.
- huskyr 14y agoSeconding 2). Incognito is not just for porn, but very handy to check for cookie or session related troubles too. Chrome's implementation should be the default for all private browsing sessions in browsers.
- nossralf 14y agoPer-window private browsing is implemented and available in Nightly according to [1] (so, most likely in Aurora after the release shift this week). So hopefully it'll be in Firefox 20. Meta-bug for per-window private browsing in Bugzilla is [2]. [1] https://hacks.mozilla.org/2012/12/firefox-development-highlights-per-window-private-browsing-canvas-globalcompositeoperation-new-values/ https://hacks.mozilla.org/2012/12/firefox-development-highli... [2] https://bugzilla.mozilla.org/show_bug.cgi?id=463027 https://bugzilla.mozilla.org/show_bug.cgi?id=463027
- unicornporn 14y agoGreat news!
- rplnt 14y ago
- sequence7 14y agoDoes 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. The last release/mention I found was a preview [1] in October last year and then nothing but tumbleweed ... [1] https://blog.mozilla.org/futurereleases/2012/10/04/firefox-metro-preview/ https://blog.mozilla.org/futurereleases/2012/10/04/firefox-m...
- padenot 14y ago(Mozilla dev here) I can guarantee you that people are working on it. I don't know the specifics, but it's coming along. You can follow the commits here [1]. Of course because it is free software, if you are not afraid to test a early prototype, you can get a build for every push to the repo. It is a bit complicated (lots of clicks in our custom CI interface), tell me if you are interested. [1]: http://hg.mozilla.org/projects/elm/ http://hg.mozilla.org/projects/elm/, the elm branch being the repo where people work on Win8 support.
- sequence7 14y agoThanks padenot, it would be great if you could point me in the direction of where to find the builds.
- padenot 14y ago- Go to [1] (our CI) - Find a green "B" on a Win opt line (meaning that a build has succeeded for a Windows Optimized build), click on it, a panel appears at the bottom - On the bottom left of the page, you can see a link named "go to build directory". Click on it, that sends you to the location where the CI stores the build - In the list, there is an installer executable, that you can use to install this particular Firefox build (for examples: "firefox-20.0a1.en-US.win32.installer.exe"). Please keep in mind this is very much a work in progress, and it is likely to break horribly, maybe destroying your computer in the process (you never know :D). No warranties, blah blah blah. If you find bugs, it would be much appreciated to have them filed on bugzila.mozilla.org. [1]: https://tbpl.mozilla.org/?tree=Elm https://tbpl.mozilla.org/?tree=Elm
- btipling 14y agoPlease speed up SVG animations in Firefox 19. d3.js animations can be painfully slow in Firefox when they aren't in Webkit.
- lillycat 14y agoYou should fill a bug with a demo in http://bugzilla.mozilla.org http://bugzilla.mozilla.org (with timing in Fx and in a Webkit browser to show the problem) They won't read you here.
- kbrosnan 14y agoThat is not how Mozilla development works. Code changes go int the trunk/nightly builds currently FX 21. Only rarely does code get uplifted to Aurora or Beta. Usually this is because something regressed. Please file a bug with example code. https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=SVG&CC=:kbrosnan https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&...
- IgorPartola 14y ago> FIXED: Disable insecure content loading on HTTPS pages (62178). Very nice. Check out the test page here: https://people.mozilla.com/~bsterne/tests/62178/test.html https://people.mozilla.com/~bsterne/tests/62178/test.html 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.
- netghost 14y agoThe retina support is really welcome. Up until now, using firefox on a retina mac was kind of disappointing.
- JohnFromBuffalo 14y agoI'm still using 3.5.7. What more could you want?
- Trezoid 14y agoSecurity updates? The huge number of performance boosts and resource use reductions later versions have seen? The very large number of css properties and selectors added?
- tesmar2 14y agoI 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?
- mbrubeck 14y agoFirefox now has a built-in debugger (which appeared in Firefox 15, released in August 2012). This uses a new debugging back-end built by Mozilla's JS and devtools teams, totally separate from the older Firebug debugger code. It should be more robust, and has new features like remote debugging of code running in Firefox for Android. More info at https://hacks.mozilla.org/2012/07/debugger-responsive-design-view-and-more-in-firefox-aurora-15/ https://hacks.mozilla.org/2012/07/debugger-responsive-design...