7 ms·
Chrome 34: Responsive Images and Unprefixed Web Audio
- PStamatiou 13y agoDoes this only work for device resolution needs - ie, load an @2x version in the same image width/height for 2x hi dpi displays? Versus progressively download larger images the more the user widens the display. I actually care a bit less about loading huge images for 4k or other 'retina' displays than I do just showing a 1000px image instead of a 500px (note, not a 1000px image in a 500px container for high dpi needs) image when the user expands the window, etc. currently very hackily checking browser width (and keeping in mind of image is used in a grid or just a full-width image on its own) to rewrite all data-src when the page loads and before lazy loading has kicked in (to prevent double image downloading) on my photoblog: http://paulstamatiou.com/photos/carmel-monterey/ http://paulstamatiou.com/photos/carmel-monterey/
- scotth 13y agoI believe the element that you're looking for is <picture>, which will be shipping with a future version of Chrome. http://picture.responsiveimages.org/#examples http://picture.responsiveimages.org/#examples
- PStamatiou 13y agoAh right, thanks. I had been thinking that picture and srcset were competing.
- igrigorik 13y agoThey're complementary. <picture> uses subset of original srcset spec to meet the "resolution switching" use case - e.g. see Example 1 [1]. If you want to select an asset based on viewport width, then you'd either use "sizes" attribute on picture, or a combination of srcset + sources + sizes. [1] http://picture.responsiveimages.org/#examples http://picture.responsiveimages.org/#examples
- kclay 13y agoMaybe this http://foundation.zurb.com/docs/components/interchange.html http://foundation.zurb.com/docs/components/interchange.html when <picture> isn't supported?
- TazeTSchnitzel 13y agoI'd also be interested to know if it would use the 2x version if I zoom in the page 200% on a non-HiDPI machine.
- igrigorik 13y agoThis behavior is not defined by the spec / left to the UA. At the moment, I don't believe either WebKit or Blink implementation will swap the image on (desktop) zoom.
- TabAtkins 13y agoThe srcset attribute by itself can't do what you ask; it only lets you specify multiple resolutions of an image, all (intended to be) the same size. But wait for implementation to finish, and you'll be able to use the sizes='' attribute on the <img>, or the full <picture> deal, and that'll give you more control, letting you load a smaller image if the image would take up less space.
- higherpurpose 13y agoSince I upgraded to Chrome 33, some Flash videos don't work anymore. The screen is just black there, and there's no sound either. Are they aware of this bug? It could be Adobe's fault, but Flash is updated in Chrome only through Chrome, so then it's their fault, too. For example, the live video here isn't working right now in Chrome, and when I right click, it says "movie not loaded". It works in Firefox. http://www.theverge.com/2014/2/27/5453572/the-vergecast-113 http://www.theverge.com/2014/2/27/5453572/the-vergecast-113
- scotth 13y agoHave you tested the same video Incognito?
- deleted 13y ago[deleted]
- pknight 13y agoRecently I can't get any browser to reliably render flash content without the browser crashing or blacking out. It's a coin flip whether a video is going to show or not. The irony is that IE 11 has been the most consistent of all things.
- epmatsw 13y agoInteresting choice to ignore autocomplete=off. I am not sure how I feel about that. https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/zhhj7hCip5c/PxbtDtGbkV0J https://groups.google.com/a/chromium.org/forum/#!msg/chromiu...
- thirsteh 13y agoI love it! So many companies have made it a massive pain to use password managers, and thus unique, random and strong passwords for individual sites, all in the name of "security," using that property. I wish all browsers/password managers would ignore it.
- untog 13y agoI do get their logic. And it is just for password fields, which is good - I've used autocomplete=off before when making a custom autocomplete solution on the page.
- duskwuff 13y agoThis seems like it could be inconvenient for web applications that use <input type=password> in a non-login context. Imagine that you've got a web interface that can be used to configure usernames and passwords for something completely separate (say, for email accounts). Trying to autofill that form with credentials from the management interface, or saving usernames/passwords entered into that form, would be unexpected and undesirable.
- leeoniya 13y agoi have a web app that has multiple password fields on the same page / domain. especially on config/admin pages. this is gonna break many things for me.
- cpleppert 13y agoI use Safari solely because of this reason. It would cost me too much time to remember/retype all of my passwords, especially if it is a intranet type application that demands a password seemingly time I get a link and won't stay logged in for a reasonable time.
- therealmarv 13y agoDoes anybody know if this responsive image thing also works in Firefox and are there any polyfills for IE? Would look strange if images only look crisp and detailed in Chrome.
- nephyrin 13y agoMozilla intends to implement srcset/picture, but it hasn't landed yet. Relevant bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=870021 https://bugzilla.mozilla.org/show_bug.cgi?id=870021 https://bugzilla.mozilla.org/show_bug.cgi?id=870022 https://bugzilla.mozilla.org/show_bug.cgi?id=870022
- mdemare 13y agoI hope the development tools get some love, since they're completely borked in the last couple of releases.
- farnsworth 13y agoYes - what the heck happened there?
- pjmlp 13y agoStill waiting for proper WebGL support without having to force it.
- slacka 13y agoThis is great news, but what I'd really love to see is the Chrome team focus on their memory footprint. Chrome < 20 used to run great on my 2GB ultrabook, now Firefox is my only option. Chromium on my Raspberry Pi can barely handle 1 open tab, while Firefox can handle several before the system starts to thrash. If Google was smart, they create a group like Firefox's memshrink to get this situation under control.