W3C home > Mailing lists > Public > public-bpwg@w3.org > June 2009

Re: MWABP: Revised text for Device Capability Detection.

From: Adam Connors <adamconnors@google.com>
Date: Fri, 19 Jun 2009 12:52:30 +0100
Message-ID: <393b77970906190452r7567727t115153c6c962592b@mail.gmail.com>
To: Bruce Lawson <brucel@opera.com>
Cc: Rotan Hanrahan <rotan.hanrahan@mobileaware.com>, Mobile Web Best Practices Working Group WG <public-bpwg@w3.org>
On Fri, Jun 19, 2009 at 12:16 PM, Bruce Lawson <brucel@opera.com> wrote:

> On Fri, 19 Jun 2009 11:53:57 +0100, Adam Connors <adamconnors@google.com>
> wrote:
>
>  Great. Bullet-point added... Would somebody more familiar with the
>> technology be able to supply a short summary please.
>>
>
> How about: CSS  provides a mechanism called media queries
> http://www.w3.org/TR/css3-mediaqueries/ whereby developers can provide
> stylerules depending on certain attributes of the device such as
> device-width, aspect ratio, number of colours supported. This can reflow
> content, provide different fonts or differently-sized backgroud images, or
> hide images etc.
>

Thanks. Added.


>
> - sidenote; if CSS has "display:none" for an image/ element with a
> background image, should we recommend that it not be downloaded until it's
> needed, or would that introduce too much delay if CSS or JAvaScript
> subsequently changed that display value?
>

This is controlled by the browser implementation and not in the control of
an application developer. You can hack around it in JavaScript to get a
deferred image load, but it's a bit low-level / technical for this doc IMO.
Received on Friday, 19 June 2009 11:53:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 19 June 2009 11:53:06 GMT