Google Chrome 34 Is Out: Responsive Images, Supervised Users
An anonymous reader writes "Google today released Chrome version 34 for Windows, Mac, and Linux. The new version includes support for responsive images, an unprefixed version of the Web Audio API, and importing supervised users. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome."
n/t
In case anyone wanted to know what responsive images are, I googles this imformative article on the subject:
http://dev.opera.com/articles/...
Bye!
With the NSA API?
That is very nice. Do the fonts still look like total crap?
A "responsive image" will load either a small or large version (or multiple versions) depending on the browsers's screen resolution. To do this, it makes an extra request to the server before requesting the appropriate image size.
(The referenced Opera article prattles on and on - Google's faster.)
If it exists there is ...
Wait, sorry, misread the subject.
What about proper HiDPI support?
Why is this still a 32-bit browser? Java won't install in 32-bit browsers.
If it still eats up 1 GB memory for 3 open tabs (or 500 MB with no tabs), then sorry, it's still shit.
...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
The 32-bit version will install in a 32-bit browser.
Well good news! Once Firefox fully apes the Chrome UI they can both look equally ugly!
I have a dream... Where, instead of learning to support some new "responsive image" paradigm, the web designers of the world focus their efforts on learning to make use of the responsive vector images that browsers already support.
Chelloveck
I give up on debugging. From now on, SIGSEGV is a feature.
I tried chrome some time back. After installing it I switched user accounts and it was gone. Silly thing had installed in %appdata% or something like it thought it was Reveton. Even if I liked it (in my short experience it seemed a bit creepy) I would not find it reasonable to have to spend all day installing the same program over and over again just to have access to it across user accounts.
So, fixed? Or defective by design?
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
You don't need wavelets for that. Instead, all you really need is so-called "progressive JPEG": send the first 15 or 21 DCT coefficients for a half-resolution decode, then send more coefficients for the full-resolution decode. But in practice, that doesn't speed things up because in order to terminate the image download after the first few coefficients, the web browser has to close the HTTP connection instead of keeping it alive, which means yet another round of TCP slow start.
True, with IE for XP officially dead, it's finally safe to use SVG on the vast majority of browsers. But good luck efficiently vectorizing a photograph received through a camera lens.
Did they fix the problem with not showing urls when hovering over links?
Download the crx file from where ever you want and drag & drop the file into the extension tab in settings. Done.
All of the good mouse gesture add-ons broke when chrome update 32 removed some legacy features in the name of security. The only mouse gestures that work now have ad-ware built in. Why can't someone make an open source mouse gesture add on?
You can update to the latest release now using the browser's built-in silent updater
Whoa, whoa, slow down... could you walk me though that?
32-bit Windows -- chrome taking 256MB...at first. Has shrunk down to 165MB a few minutes later. Not my idea of acceptable memory usage.
Opera, with 17 tabs, and it has been running for a few days, is only using 323MB
I come here for the love
Not on OS X. See http://www.java.com/en/downloa...
Safari and Firefox are both 64-bit, fwiw. I don't understand why Google is dragging their feet on this.
huh?? NOTHING looks as ugly as Firefox, it's freakin hideous
What's your point? Jokes are supposed to be funny.
when they add a menu bar. Until then, I have ZERO interest in Chrome.
I'm not trolling. I'm completely serious. Removing a standard UI component "just because" is an absolute deal breaker for me.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
So draw us a better UI... and don't just say "Internet Explorer 9!"...
What would you do if you go home and the plastic's all melted and so is the Chrome?
Still no APNG support? Yawn...
http://i.cubeupload.com/T6cyLu.png
the decode is probably faster than the network transfer
That's not the bottleneck as much as the multi-decisecond latency of requesting each range over a wireless (satellite or cellular) connection.
so it can request it in batches of size X
How would the browser know what size X is, so that it doesn't get a tiny range, request another, wait two seconds, request another, wait two seconds, etc.?