...
I have always been comfortable with the 'x' part of srcset, but the w
and h part felt somewhat wrong to me. What you'd really want to consider
when deciding which image to pick isn't the size of the viewport itself,
but the size available for the image once the rest of the layout
On Tue, Sep 4, 2012 at 10:15 AM, Boris Zbarsky bzbar...@mit.edu wrote:
So now our list is:
1) Have a way for pages to opt in to software rendering.
2) Opt canvases in to software rendering via some sort of heuristic
(e.g. software by default until there has been drawing to it for
- Original Message -
On Tue, Sep 4, 2012 at 10:15 AM, Boris Zbarsky bzbar...@mit.edu
wrote:
So now our list is:
1) Have a way for pages to opt in to software rendering.
2) Opt canvases in to software rendering via some sort of
heuristic
(e.g. software by default until
Ian Hickson i...@hixie.ch schrieb am Tue, 4 Sep 2012 19:47:38 +
(UTC):
(regarding picture)
I don't understand why it's more intuitive and easier. It seems way
more unwieldly.
Personally, I consider picture with source to be very similar to
using ATOM enclosures in podcasting. The relation
On Thu, 5 Jul 2012, Glenn Maynard wrote:
On Fri, Jun 29, 2012 at 4:24 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 21 Feb 2012, Glenn Maynard wrote:
I don't think the existence of implicit submit should depend on
platform conventions, though, for interop on forms without visible
On Sep 4, 2012, at 3:47 PM, Ian Hickson wrote:
[...]
On Thu, 24 May 2012, Florian Rivoal wrote:
picture
source srcset=normal.jpg 1x, highres.jpg 2x
source media=(max-width:768px) srcset=ipad.jpg 1x, ipad3.jpg 2x
source media=(max-width:320px) srcset=iphone.jpg 1x, iphone4.jpg
2x
Whether it's easier for script is hard for me to say, because I don't
really understand what scripts are going to be doing here. Can you
elaborate? What will scripts need to do here?
Manipulating picture from script would be a huge pain -- you'd have to
be manipulating lots of elements
On Mon, Apr 30, 2012 at 08:55:04AM +0300, Aryeh Gregor wrote:
On Sun, Apr 29, 2012 at 11:39 PM, David Young dyo...@pobox.com wrote:
I'm curious what advantages document.execCommand() has over the
customary DOM API for adding/deleting/moving nodes?
execCommand() does vastly more complicated
On Fri, 13 Jul 2012, Ryosuke Niwa wrote:
On Fri, Jul 13, 2012 at 3:17 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 13 Jul 2012, Ryosuke Niwa wrote:
*HTMLCollection* returns the first element.
This is for compat in the default case, I believe.
*HTMLAllCollection* returns the first
On Wed, Aug 29, 2012 at 4:27 PM, Ian Hickson i...@hixie.ch wrote:
On Sun, 17 Jun 2012, Aryeh Gregor wrote:
On Thu, Jun 14, 2012 at 1:11 AM, Ian Hickson i...@hixie.ch wrote:
I strongly disagree. input and textarea are high-level constructs,
so it's fine for them to be defined by the UA's
On Tue, 04 Sep 2012 22:53:57 +0100, Leif Halvard Silli
xn--mlform-iua@målform.no wrote:
If we say that picture should have img role, then we imply that
alternative text should be provided via an attribute.
Why?
Because that is what ARIA 1.0 says about the img role: In order for
elements
On Mon, 27 Aug 2012 12:05:00 +0100, Chaals McCathieNevile w...@chaals.com
wrote:
While it's unlikely that screen resolution will go above 2x in the near
future, should we be taking into account the zooming of specific
elements that might result in the need for larger artwork? (take icons,
On Wed, Jul 25, 2012 at 7:20 PM, Ian Hickson i...@hixie.ch wrote:
Our remaining discomfort here is with isIntentHandlerRegistered(), and
for similar reasons to the fingerprinting qualities of
isProtocolHandlerRegistered(). That is, we'd prefer that web content
simply call
On Wed, Sep 5, 2012 at 1:45 PM, Mathew Marquis m...@matmarquis.com wrote:
I can say for my own part: manipulating strings is far more difficult than
manipulating the value of individual attributes. It’s hard to imagine a
situation where I’d prefer to muck through a space/comma separated string
Mathew Marquis m...@matmarquis.com schrieb am Wed, 5 Sep 2012 13:45:41
-0400:
[…]
I’m not sure how exactly to prove to you that developers find the
extended syntax unintuitive apart from continuing to point out the
things that developers themselves have said on the topic, and I’m
still not
Aaron Gustafson aa...@easy-designs.net schrieb am Wed, 5 Sep 2012
18:42:37 -0400:
[…]
Might I propose an option 3 (which is in no way a vote of support for
Hixies suggested srcset, I like the proposed video-like syntax far
more):
[{ image: 'img2.jpg', density: '2x', query: '300w' }, {
On Wed, Sep 5, 2012 at 7:01 PM, Nils Dagsson Moskopp
n...@dieweltistgarnichtso.net wrote:
Aaron Gustafson aa...@easy-designs.net schrieb am Wed, 5 Sep 2012
18:42:37 -0400:
[…]
Might I propose an option 3 (which is in no way a vote of support for
Hixies suggested srcset, I like the proposed
On Wed, Sep 5, 2012 at 12:45 PM, Mathew Marquis m...@matmarquis.com wrote:
I’m not sure how exactly to prove to you that developers find the extended
syntax unintuitive apart from continuing to point out the things that
developers themselves have said on the topic, and I’m still not certain
On Sep 4, 2012, at 12:47 , Ian Hickson i...@hixie.ch wrote:
On Thu, 7 Jun 2012, Mark Callow wrote:
IIRC Kodak's PhotoCD image format had this characteristic. The first
part is a low res. image, the second is the differences between the low
res. image zoomed to the high res. size and the
Glenn Maynard gl...@zewt.org schrieb am Wed, 5 Sep 2012 19:01:19
-0500:
[…]
On Wed, Sep 5, 2012 at 6:01 PM, Nils Dagsson Moskopp
n...@dieweltistgarnichtso.net wrote:
Still, this would mean that existing DOM-like node-based data
structures could not be used easily – even if filled
On Wed, Sep 5, 2012 at 7:49 PM, Nils Dagsson Moskopp
n...@dieweltistgarnichtso.net wrote:
Often, solutions that can be considered “simple” for emitters of data
externalize costs, burdening consumers – especially when “simple”
prevents using off-the-shelf components like XML parsers (if a site
21 matches
Mail list logo
