Slashdot Mirror

← Back to Stories (view on slashdot.org)

Chrome 42 Launches With Push Notifications

Posted by Soulskill on from the douglas-adams-edition dept.

An anonymous reader writes: Google today launched Chrome 42 for Windows, Mac, and Linux with new developer tools. Chrome 42 offers two new APIs (Push API and Notifications API) that together allow sites to send notifications to their users even after the given page is closed. While this can be quite an intrusive feature for a browser, Google promises the users have to first grant explicit permission before they receive such a message.

7 of 199 comments (clear)

  1. Fuck No by sexconker · · Score: 5, Insightful

    Can we go back to the web being "Hey can I get your page at site.tld/page.ext ?" and "Sure, here is what you asked for, and not an entire cart of horseshit jammed in with it, alongside it, or after it! Thank you for visiting our website, valuable reader / customer!"?

  2. I Closed the Frikkin' Page for a Reason! by Irate+Engineer · · Score: 4, Insightful

    Oh great, so if I stumble on a page so full of crap that I decide to backtrack the hell away, the site can still shove notifications in my face, even though I clearly don't want that content? Yeah, I have to explicitly allow it, that's awfully nice of them. But how long will opting out last when the advertisers realize they can force a few more eyeballs? Is there another browser out there that hasn't been bloated to death with "features"? I jumped from Firefox to Chrome when they started churning versions, but Chrome just jumped the shark by doing the same thing.

    --

    Left MS Windows for Linux Mint and never looked back!

    Vote for Bernie in 2016!

  3. Actually, it's worse than that. by Rob+from+RPI · · Score: 4, Informative

    Java is Broken in Chrome 42. Totally. There is no way to run Java in the browser, at all. In any way.

    Trying to run any Java app results in this: http://i.imgur.com/Imuxmay.png

    There's a ticket open here:
    https://code.google.com/p/chro...

    --
    Schlock Mercenary.
    1. Re:Actually, it's worse than that. by The+MAZZTer · · Score: 5, Informative

      It was a design decision to improve browser security (NPAPI model is horribly outdated). Almost no one uses Java on the web any more so it was decided it was acceptable. Oracle is free to port Java to NaCl or PPAPI if they want to continue supporting Chrome.

      Yeah it sucks for the small % of users who still want to use it, but it's necessary to move security forward.

  4. Circa 1995 by dmaul99 · · Score: 4, Insightful

    Way back in the day when Microsoft was unleashing IE onto the world, everybody howled that they were introducing new IE specific things for websites to be able to provide, eg ActiveX. Now it seems that google is doing the same thing with Chrome. In both cases the idea is to take ownership of the web...

    1. Re:Circa 1995 by Lennie · · Score: 5, Informative

      Chrome ?

      These APIs have been created by organisations working together at the W3C.

      It was actually the person from AT&T which did the most work on getting Push API adopted by the W3C.

      --
      New things are always on the horizon
  5. Re:Another? by jonwil · · Score: 4, Interesting

    I use SeaMonkey which is the descendent of the old Mozilla suite.
    Its got all the same web engine stuff as Firefox does but it doesn't have the crappy UI or some of the other "unwanted" crap from Firefox.