I wanted to float another idea which I’ve been toying with to hear what other people think and see if its a viable tool.<\/p>\n
When we created our noscript solution we discovered that the image inside wasn’t being added to the DOM and therefore the\u00a0src attribute wasn’t making a request to the server. So we were pleased we’d found a work around but it’s a pretty dirty hack and I’m not that keen on it even though it does the job.<\/p>\n
What I’d really like is another way of adding content to the\u00a0HTML which isn’t loaded into the DOM until either my CSS or JS has decided what it wants to do with it. I’m also wondering if this is a way I can get more info into the HTML page, without having to add weight to the HTTP header and if this idea could be extended beyond just responsive images, into other parts of responsive asset management and build (i.e. fonts, media, video etc. )<\/p>\n
I was thinking of submitting a proposed spec for something like a defaults tag, or possibly \u00a0a line in the meta data to tell modern browsers to omit certain DOM requests, like img src until the client has decided which src request it wants to make. That way old browsers can still load the image src as normal, we don’t have to do dirty things like hiding stuff in the noscript and modern browsers can hijack the img tag to prevent the page making the img src request until its ready.<\/p>\n
Would love to hear other peoples opinions on this technique and if anyone has any suggestions on ways to improve on it.<\/p>\n","protected":false},"excerpt":{"rendered":"
I wanted to float another idea which I’ve been toying with to hear what other people think and see if its a viable tool. When we created our noscript solution we discovered that the image inside wasn’t being added to … Continue reading