Chrome 42 Launches With Push Notifications

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.

Comments

Actually, it's worse than that.

[Rob from RPI]

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...

Re:Actually, it's worse than that.

[The MAZZTer]

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.

Re:Actually, it's worse than that.

[Billly Gates]

Agreed, I wish Java would die a very horrible and torturous death. (very slowly)

But I'm forced basically by state law in our organization to have it ready to use on most of our machines to run state tests.

So until Pearson's idiot developers pull their head out of their asses and stop using it in all their education products I'm stuck with this crap.

Alright

First thing first grab a thick Windows Server 2008 or 2012 book from Microsoft Inside OUT and walk over to your system administrator and wack him on the back side of the head with it!

Then proceed to open the chapter on creating Group Policy Objects? disable java in internet zone under internet options in the control panel. Then create another one to enable java scripting in the intranet zone and add Pearson's to this. DONE.

It is negligence to run this on the web and any system administrator worth his salt under has it enabled for trusted zone sites or intranet sites. Safe, secure, and works with old crud.

IE has it's advantages at work over Chrome. One of them is managing ancient insecure crud and this is where is it useful over Chrome.

How about a working middle button?

[drinkypoo]

Lately the middle button in Chrome has been deprecated, and it doesn't do what it says on the tin. Sometimes I middle-click on something and the page just begins scrolling, for example Youtube videos (even when not yet loaded!) especially in G+, which is a place you especially don't want to scroll accidentally. Also, image galleries which are probably hosted by google are just coming up as a slideshow in the current tab instead of opening a new tab. Google reserves the right to change the behavior of Chrome only for their sites, and up yours.

I wouldn't use Chrome at all, but some Google sites sometimes only work properly in it. Youtube is the primary example. Sometimes a given resolution will choke in Firefox, sometimes in Chrome, and there's no apparent rhyme or reason to it.

Re:Circa 1995

[Lennie]

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.