Re: [whatwg] responsive imgs proposition (Re: The src-N proposal)

2013-11-16 Thread Bruno Racineux
On 11/16/13 3:24 PM, "matmarquis.com" wrote: > >I started and have been running the Responsive Images Community Group for >nearly three years now.I helped build BostonGlobe.com and the original >³prototype² script for responsive images, I¹m a maintainer on the >Picturefill project, and I wrote la

Re: [whatwg] responsive imgs proposition (Re: The src-N proposal)

2013-11-16 Thread matmarquis.com
On Nov 16, at 4:25 PM, Bruno Racineux wrote: > > > On 11/15/13 9:48 PM, "matmarquis.com" wrote: > >> I©öd say the likelihood of a project not using a content image directory a >> step or two from root is roughly the same as the likelihood that I©öm >> hot-linking to images on someone else©ös

Re: [whatwg] responsive imgs proposition (Re: The src-N proposal)

2013-11-16 Thread Bruno Racineux
On 11/15/13 9:48 PM, "matmarquis.com" wrote: >I¹d say the likelihood of a project not using a content image directory a >step or two from root is roughly the same as the likelihood that I¹m >hot-linking to images on someone else¹s website땧hich is to say ³very >slim.² The ³real world with clouds

Re: [whatwg] The src-N proposal

2013-11-16 Thread Timothy Hatcher
On Nov 16, 2013, at 11:30 AM, Tab Atkins Jr. wrote: > This entire discussion, for months, has been entirely about syntax. I > don't think I've seen a single person talk about semantics, nor do I > think it would make much sense to do so. Maybe semantics is the wrong word. I feel (and others agr

Re: [whatwg] The src-N proposal

2013-11-16 Thread Tab Atkins Jr.
On Sat, Nov 16, 2013 at 10:54 AM, Timothy Hatcher wrote: > My objections were mostly about semantics and not purely aesthetic. I also > wasn't the only one to raise concerns on webkit-dev. To represent the WebKit > community concerns as “personal” is disingenuous. I don't pretend to > represent

Re: [whatwg] The src-N proposal

2013-11-16 Thread Timothy Hatcher
> On Nov 16, 2013, at 8:09 AM, "Tab Atkins Jr." wrote: > >> On Sat, Nov 16, 2013 at 3:55 AM, Kornel Lesiński wrote: >> Basically authors will hate us. We've been going in circles for a couple of >> years now and all we have to offer is an incomplete solution? And browser >> vendors can't even a

Re: [whatwg] The src-N proposal

2013-11-16 Thread Tab Atkins Jr.
On Sat, Nov 16, 2013 at 3:55 AM, Kornel Lesiński wrote: > Basically authors will hate us. We've been going in circles for a couple of > years now and all we have to offer is an incomplete solution? And browser > vendors can't even agree which one of the half-baked solutions is it going > to be :(

Re: [whatwg] [mimesniff] The Apache workaround should not sniff random types

2013-11-16 Thread Gordon P. Hemsley
On 8/27/13 12:26 PM, Boris Zbarsky wrote: The current mimesniff spec says that when the Apache workaround is applied sniffing should still be able to detect the content as PostScript, images, videos, archives, audio formats, etc. I feel that this poses an unacceptable security risk due to allowi

Re: [whatwg] The src-N proposal

2013-11-16 Thread Kornel Lesiński
On Sun, 10 Nov 2013 08:20:33 -, Adam Barth wrote: This is similar to AppCache vs Alex's ServiceWorkers. AppCache addresses a small set of use cases, probably not enough. ServiceWorkers provides the tools to address a lot of use cases, but isn't directly itself a solution; you use it t

Re: [whatwg] responsive imgs proposition (Re: The src-N proposal)

2013-11-16 Thread Markus Lanthaler
On Saturday, November 16, 2013 12:11 AM, Bruno Racineux > On 11/15/13 2:50 PM, "Tab Atkins Jr." wrote: > > There is no compaction > > scheme that helps here. (Unless you're trying for one of the > > url-template ones, and we don't want to go there.) > > Why not? I'd like to hear the argument aga