Hello iPad user! You should definitelydownload and try our free iPad app!

Published
  1. scottjehl
    Time to shift the responsive imgs discussion to how we'd actually prefer to do things, and then make it happen. Attrs? CSS? JS? New headers?
    0 likes
     · 
    0 comments
  2. scottjehl
    …maybe some predefined attribute values for sending a specific extra header with certain assets? <img src="…" headers="viewport"> /cc @beep
    0 likes
     · 
    0 comments
  3. beep
    @scottjehl Ooh! I like that. Or maybe a BASE-like element that accepts a media value? Could gate requests conditionally.
    0 likes
     · 
    0 comments
  4. scottjehl
    @beep nice! One of these combined with existing responsive imgs techniques that worked in most browsers before aggressive prefetch set in :)
    0 likes
     · 
    0 comments
  5. scottjehl
    @beep easier to lobby for a way to manipulate asset request urls with js on the client before they go out? y know ike it worked last month?
    0 likes
     · 
    0 comments
  6. scottjehl
    @beep and okay this would solve all the things: http://t.co/EDVBJqth (I hear @paul_irish is receptive for these sorts of things… ;) )
    0 likes
     · 
    0 comments
  7. The link that Scott points to is a tweet he sent my direction back in September.
  8. scottjehl
    @grigs silly: <script preparse> //document.src references raw HTML src document.src = document.src.replace( pattern, replacement ) </script>
    0 likes
     · 
    0 comments
  9. 0 likes
     · 
    0 comments
  10. grigs
    @scottjehl @beep declaring preparse in script would work. It does bug me a bit that it would require JS for something as fundamental as imgs
    0 likes
     · 
    0 comments
  11. grigs
    @scottjehl @beep it *seems* like a long term solution belongs in HTML or CSS. Also not a fan of headers because of server requirement.
    0 likes
     · 
    0 comments
  12. beep
    @grigs @scottjehl Don’t disagree entirely, but JS would allow us to negotiate other media. The BASE-like approach could be cool too.
    0 likes
     · 
    0 comments
  13. grigs
    @beep agreed. i think there is a general argument for preparse, like defer, that likely goes beyond media even. +@scottjehl
    0 likes
     · 
    0 comments
  14. scottjehl
    @grigs @beep HTML-only might be done with video-like source tags…? <img src="…"><source media="…" src="…"><source media="..." src="…"></img>
    0 likes
     · 
    0 comments
  15. grigs
    @scottjehl i like the media-xs="(min-device-width:320px and max-device-width:640px)" media-src-xs proposal http://t.co/QTEBd77x +@beep
    0 likes
     · 
    0 comments
  16. grigs
    @scottjehl @beep not sure what old browsers would do with <img><source><source></img>. Sure would be easier on the eyes. :-)
    0 likes
     · 
    0 comments
  17. 0 likes
     · 
    0 comments
  18. _crossdiver
    @grigs - <img src="large"><source src="mobile"></img>. Legacy browsers only see the first img tag. Moderns replace it. +@scottjehl @beep
    0 likes
     · 
    0 comments
  19. _crossdiver
    Suggestion for an #ffly HTML <img> tag spec reboot. http://t.co/ip0XMdPo /cc @grigs @beep @scottjehl
    0 likes
     · 
    0 comments
  20. _crossdiver
    @beep - Built an example page for one of the responsive img ideas from last night: http://t.co/ip0XMdPo
    0 likes
     · 
    0 comments

Did you find this story interesting? Be the first to or comment.

Liked!
Total views
126