W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2014

Re: [whatwg] 'hidden' as resources control (Was: Simplified <picture> element draft)

From: Qebui Nehebkau <qebui.nehebkau+whatwg@gmail.com>
Date: Sun, 26 Jan 2014 23:39:49 +0000
Message-ID: <CAF_oMa1dOTLrwdnn+xP2mrBCXkHJjUsLNLqxfBYvvAJzXiKr-A@mail.gmail.com>
To: Bruno Racineux <bruno@hexanet.net>
Cc: WHATWG <whatwg@lists.whatwg.org>
On Sat, Jan 25, 2014 at 4:13 AM, Bruno Racineux <bruno@hexanet.net> wrote:
> What exactly do you find misguided, can you be more specific?

Basically, - and I'm trying not to over-elaborate here, since my
opinion isn't really very important - I just mean that I don't think
there should be any guarantees about how (or whether) browsers will
preload, nor any specific means of controlling this, because the way
resources get loaded is not really any of the author's business. I
also think that the purely presentational choice of a specific image
file to represent the same content (and, even in the art direction
case, they're clearly the same content if they can be represented with
the same alt text; otherwise, there should be multiple img tags)
should be specified in CSS, not HTML; the argument that preloaders
can't consider CSS isn't compelling to me, because a browser's choice
to preload an image or not isn't important enough (or, I think it
shouldn't be) to justify entrenching in a specification.

On Sat, Jan 25, 2014 at 4:13 AM, Bruno Racineux <bruno@hexanet.net> wrote:
>
>
> On 1/24/14 7:37 PM, "Qebui Nehebkau" <qebui.nehebkau+whatwg@gmail.com>
> wrote:
>
>>On Fri, Jan 24, 2014 at 9:09 PM, Bruno Racineux <bruno@hexanet.net> wrote:
>>> The requirement for ATs with 'hidden' is to access the structure of
>>>hidden
>>> elements. Not the presentation aspect... I am having a hard time
>>> translating that a resources that is "not yet needed or is no longer
>>> needed" means that it should load immediately *regardless*.
>>That seems like it should be up to the user, and, thus, the user
>>agent, yes?
> This is not about user-agents. Not sure what you are getting at...
>
>
>>The question of whether and what to preload strikes me as
>>very much contingent on the priorities and circumstances of individual
>>users, and obviously not at all the authors' business. I find the
>>entire subject of specifying how user agents should preload completely
>>misguided. Shouldn't this, if *anything*, be open for innovation?
>
> What exactly do you find misguided, can you be more specific?
>
>
Received on Sunday, 26 January 2014 23:40:34 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:15 UTC