from Hacker News

Firefox 39.0 released

by tlo on 7/3/15, 12:28 PM with 101 comments

  • by mrspeaker on 7/3/15, 1:26 PM

    I love that the Fetch API is happening (has happened!): https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API

        fetch(url).then(data => ...)
    Not earth-shattering, but much more fun than XHR!

  • by cesarb on 7/3/15, 1:54 PM

    > Disable use of RC4 except for temporarily whitelisted hosts

    This is the one which has the greatest chance of giving people a headache. For instance, one of the biggest banks here still uses only RC4 for its online banking site. Its top-level hostname and a few of its auxiliary hostnames are on the whitelist, but there's no guarantee that all the RC4-only auxiliary hostnames it might use for some of its functionality are on the whitelist.

  • by bbx on 7/3/15, 1:44 PM

    Surprised by the inclusion of "CSS Scroll Snap Points": https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-snap...

    It basically allows to do scroll hijacking [1] without any JavaScript, just like this: http://blog.gospodarets.com/demos/scroll-snap-full-screen/

    [1]: http://trentwalton.com/2013/10/23/scroll-hijacking/

  • by edwintorok on 7/3/15, 2:01 PM

    If all your passwords are gone/not working in the password manager after the upgrade see this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1146731

  • by ponyous on 7/3/15, 1:32 PM

    How much does Project Silk improves scrolling performance? Can you "feel" it?

    Scrolling/motion performance is the only thing that is keeping me away from FF at the moment - Even dev tools are getting amazingly good.

  • by lobster_johnson on 7/3/15, 7:07 PM

    To those using FF, is there a way to get an "omnibar" similar to Safari?

    For example, Safari usually suggests Wikipedia articles or other useful autocompletions. FF only autocompletes from domain names, bookmarks and history, it seems. It does have a separate search input in the toolbar, but even that one doesn't do what Safari does; all the suggested autocompletes are from Google, and additional search engines like Wikipedia or Amazon require that you click on their icon to search.

    There's an extension called Omnibar, but it doesn't seem to provide suggestions from other than Google, bookmarks and history.

  • by XaspR8d on 7/3/15, 3:29 PM

    The preconnect relationship is intriguing; I hadn't been following the adoption of resource hints.

    Sidenote: I find it really interesting that the current spec suggests preconnect and its siblings accept a probability attribute estimating how likely connecting to different resources is.[1] Something funny to me about making the directed-graph/state-machine nature of the internet finally show through the markup.

    [1] http://www.w3.org/TR/resource-hints/#hint-probability

  • by chippy on 7/3/15, 5:03 PM

    "Drag and drop enabled for nodes in Inspector markup view "

    This is going to make me never use Chrome dev tools again. Nice

  • by azinman2 on 7/3/15, 6:21 PM

    Yey for progress, but one of the most annoying things for me with FF is that if I cmd-t for a new tab, I can't start typing right away for a new search and have that get preserved. There's always some lag and only then do my keys get transcribed. Safari and chrome don't have this problem, and it drives me insane.

  • by JonnieCache on 7/3/15, 1:53 PM

    If you're wondering what "unicode 8 skin-tone emoji" is about, here you go: http://unicode.org/reports/tr51/#Diversity

    Hmmmm, I'm on ff 40.0a2 and they don't render for me: http://emojipedia.org/man-with-dark-brown-skin-tone/

  • by kozukumi on 7/3/15, 2:53 PM

    And yet there are still issues on my Sandy Bridge system with display corruption even with the latest Intel drivers.

    Also has anyone else noticed that Firefox is no longer keeping the page state when navigating back? For example on Reddit go to the comments section, minimize a few comments then navigate to a link then go back and none of the minimized comments remain minimized, in Firefox prior to 38 things worked correctly.

  • by forscha on 7/3/15, 4:11 PM

    Probably unfair of me, but when browsers have a new .0 release, my brain automatically thinks "Oh good, new security bugs."

  • by ikeboy on 7/3/15, 2:15 PM

    So, they finally fixed Logjam, 1 month and a half after publication.

    Chrome still hasn't fixed it. Color me unimpressed.