On Tue, May 22, 2012 at 9:16 PM, Maciej Stachowiak m...@apple.com wrote:
It seems like making FileList mutable would serve the same use case and would
also be more flexible (as you could upload a set of files collected from
possibly multiple sources). And it seems like adding is a more likely
On Wed, May 23, 2012 at 3:38 AM, Jonas Sicking jo...@sicking.cc wrote:
But even a sequenceBlob should be allowed IMO.
How would you expose that in the UI?
One concern I have though is that this is pretty problematic UI-wise.
Simply displaying the .name (if it's a file) property in the UI
On May 22, 2012, at 11:57 PM, Adam Barth w...@adambarth.com wrote:
On Tue, May 22, 2012 at 9:16 PM, Maciej Stachowiak m...@apple.com wrote:
It seems like making FileList mutable would serve the same use case and
would also be more flexible (as you could upload a set of files collected
from
2012-05-22 13:53 Europe/Helsinki: Paul Court:
img src=face-600-...@1.jpeg alt= srcset=face-600-...@1.jpeg
600w 200h 1x, face-600-...@2.jpeg 600w 200h 2x, face-icon.png 200w
200h
Not to mention, what happens when a 3x device is released? Do I have
to change all my code again?
As I see it,
Sorry for not replying to the right message in the thread,
I was previously not subscribed to this list, so I can't.
As the editor of the CSS Media Queries spec, I've been asked
to share my opinion about this debate on responsive images, srcset,
media queries, etc.
Disclamer: I haven't followed
But, by the same token, XHR upload of FormData[1] already serves this use
case in a more flexible way. You can even make a FormData from the contents
of an html form and then add additional File objects. Making the change would
(afaict) not serve any new use cases. At most it would be a
On May 23, 2012, at 11:21 AM, Florian Rivoal wrote:
Having said all that, I think srcset=foo.jpg 1x, foo2.jpg 2x is quite
good, because it does indeed provide the browser with a set of images with
different quality, leaving it free to pick the appropriate one.
On the other hand, I think
On 23.5.2012 17:37, Nico Weber wrote:
But, by the same token, XHR upload of FormData[1] already serves this use case
in a more flexible way. You can even make a FormData from the contents of an
html form and then add additional File objects. Making the change would
(afaict) not serve any
I agree with Mat.
This idea appears to elegantly satisfy the goals we originally set out to
address in the responsive images group (and ended up subsequently coming to
like the picture/source syntax), while also bringing the advantages of the
pixel density notation.
From: Florian
I think this is a good step forward, however nless I am
mis-understanding something (entirely possible given how much has been
going on over this recently) there are problems still...
Resolution of an image and a device is not a guarantee of suitability
of an image at a given physical size. This
With this proposal, could src be used on a source element if you don't need
the features srcset provides?
Or maybe, would that just be equivalent to srcset with a single source listed?
On May 23, 2012, at 2:56 PM, Matthew Wilcox wrote:
I think this is a good step forward, however nless I am
Am 23.05.2012 17:21 schrieb Florian Rivoal:
Here's what I think we should do:
1) simplyfy srcset to only accept the *x qualifier
2) add support for srcset as an attribute of the source sub-element of
the picture element (in addition to src, or instead of it? I am not
sure).
Then you could do
On 22/02/12 00:35, Ian Hickson wrote:
I've changed the spec to be clearer that CSS cannot be taken into account
when determining the default. The default button is just always the first
submit button in the form.
What about the situation where there isn't a button? Implicit
submission still
On Tue, May 22, 2012 at 6:38 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, May 22, 2012 at 10:41 AM, Nico Weber tha...@chromium.org wrote:
Hi,
The files attribute of the input element is currently marked readonly
[1], to protect from `myInput.files = /etc/passwd; myForm.submit()`.
On Wed, May 23, 2012 at 7:01 PM, Ojan Vafai o...@chromium.org wrote:
On Tue, May 22, 2012 at 6:38 PM, Jonas Sicking jo...@sicking.cc wrote:
I don't think simply marking the attribute as writable is the correct
solution here. At the very least we should make it possible to assign
a sequenceFile
On Wed, May 23, 2012 at 7:11 PM, Nico Weber tha...@chromium.org wrote:
On Wed, May 23, 2012 at 7:01 PM, Ojan Vafai o...@chromium.org wrote:
On Tue, May 22, 2012 at 6:38 PM, Jonas Sicking jo...@sicking.cc wrote:
I don't think simply marking the attribute as writable is the correct
solution
Given a set of images of different qualities, browsers can have fairly
advanced heuristics to pick the right one. For example switching from low
res to high res halfway through the rendering of the page if the device is
high resolution and the bandwith just went from bad to good and the
latency
17 matches
Mail list logo
