That ability to run compiled web apps could end up being a big positive for the web. Chrome only does JIT. Safari also does KIT but even that is barred from being used for web apps.
I'm not sure what IE does but my cynical mind tells me Microsoft wants out privacy to be an app store based one.
Whilst we effectively lost that Open Screen Project, no doubt due to strong pressure from Microsoft, it is good to actually see some stuff still developing for the web..
Has anyone run into this JavaScript error after updating to 22?
"Illegal operation on WrappedNative prototype object"
Get it on start-up and new pages. Have to keep clicking OK until it goes away. Haven’t pinned it down yet. It’s fine with all extensions disabled. I re-enabled all my most commonly used extensions but haven't reproduced the problem yet.
I will re-enable the others as and when needed. Then presumably at some point the error will be triggered.
Anyone who has an an old PC like myself may want to hold fire upgrading, 22 seems very cpu intensive at times even when its sitting idle, also pages seem slower to load than 21
I haven't upgraded yet and I don't think I will until all the known problems are out. I'm even finding 21 a bit of a RAM hog and I'm not using an old computer.
Anyone who has an an old PC like myself may want to hold fire upgrading, 22 seems very cpu intensive at times even when its sitting idle, also pages seem slower to load than 21
I'm using a P4 with 1GB of RAM that I've owned since 2003 as my main machine, and Firefox 22 is working fine on it with less than 1% CPU when idle. Still, this is on Linux, so maybe it's different on whatever you might have. I'm not saying your problems are imaginary, but they're not what I'm experiencing on this old machine.
For those using a slingbox, Sling have now fixed their sling watch addon and it works now in v22.
I had to use chrome for a while just to watch the slingplayer, glad to have firefox back for that.
For those using a slingbox, Sling have now fixed their sling watch addon and it works now in v22.
I had to use chrome for a while just to watch the slingplayer, glad to have firefox back for that.
Maybe only for a month when they release 23 and it breaks god knows what again.
These rapid release cycles are too much bother, always one add-on or another breaks each time. I should think the add-on developers are getting pissed off with it.
Comments
as someone who has been using 22 for 6 weeks i can confirm it is the same as 21.
well it supports WebRTC on by default. but since you don't know what that is it wont affect you.
Nooooo!!!!!
<falls down on knees>
You Maniacs! You blew it up! Ah, damn you! God damn you all to hell!
I liked the bookmarks button where it is.
That ability to run compiled web apps could end up being a big positive for the web. Chrome only does JIT. Safari also does KIT but even that is barred from being used for web apps.
I'm not sure what IE does but my cynical mind tells me Microsoft wants out privacy to be an app store based one.
Whilst we effectively lost that Open Screen Project, no doubt due to strong pressure from Microsoft, it is good to actually see some stuff still developing for the web..
That is what happened when I installed V21.
Just hangs the browser.
Never had a problem with this plugin before.
"Illegal operation on WrappedNative prototype object"
Get it on start-up and new pages. Have to keep clicking OK until it goes away. Haven’t pinned it down yet. It’s fine with all extensions disabled. I re-enabled all my most commonly used extensions but haven't reproduced the problem yet.
I will re-enable the others as and when needed. Then presumably at some point the error will be triggered.
Even with much of IE 10 being built into and loading when Windows starts, IE comes nowhere.
http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534-12.html
This is the worst update for a while, should still be in beta, gone back to 21
Just the 'first run shockwave flash' problem, where when you first run Firefox, after booting or rebooting, it Flash hangs for ages.
But once it has run, it works OK until the next reboot.
I'm using a P4 with 1GB of RAM that I've owned since 2003 as my main machine, and Firefox 22 is working fine on it with less than 1% CPU when idle. Still, this is on Linux, so maybe it's different on whatever you might have. I'm not saying your problems are imaginary, but they're not what I'm experiencing on this old machine.
Fast compiled web apps will certainly give encouragement to web development.
http://www.osnews.com/story/27161/Firefox_22_is_the_new_king_of_the_hill
Interesting that WebGL in Chrome is rated as bad.
Am I missing something, Is that more of a security risk and also why are they required?
Anyway it have to be supported by other browsers as well.
Obviously there will be plenty of big money marketing to tell us otherwise.
I had to use chrome for a while just to watch the slingplayer, glad to have firefox back for that.
Maybe only for a month when they release 23 and it breaks god knows what again.
These rapid release cycles are too much bother, always one add-on or another breaks each time. I should think the add-on developers are getting pissed off with it.