We're getting some good feedback over on the Community Group about
this, people seem to like it.
I'm still asking a few people to try and find holes in the proposal
though, reasons why it wouldn't work.
-Matt
On 14 May 2012 17:59, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, May 14, 2012
Hi all,
have any of you seen this proposal for an alternative solution to the problem?
http://www.w3.org/community/respimg/2012/05/13/an-alternative-proposition-to-and-srcset-with-wider-scope/
I like the general idea and from an author perspective this seems
great; but I know nothing of the
On Mon, May 14, 2012 at 10:55 AM, Matthew Wilcox m...@matthewwilcox.com wrote:
have any of you seen this proposal for an alternative solution to the problem?
http://www.w3.org/community/respimg/2012/05/13/an-alternative-proposition-to-and-srcset-with-wider-scope/
I like the general idea and
I'd contest that it is no harder to understand than it is to
understand why your CSS behaves differently when a JS element acts on
the mark-up. We are used to one stack defining how another acts. We do
it all the time. Adding classes to mark-up to control display, or just
the cascade on its own
On Mon, May 14, 2012 at 10:55 AM, Matthew Wilcox m...@matthewwilcox.com wrote:
Hi all,
have any of you seen this proposal for an alternative solution to the problem?
http://www.w3.org/community/respimg/2012/05/13/an-alternative-proposition-to-and-srcset-with-wider-scope/
I like the general
Thanks for the feedback. Please also forgive me not being too
technically aware of things at a browser level; so I'm not really sure
how valid my feedback can be:
The URI thing is actually using URI Templates, which are already
pretty far along? http://code.google.com/p/uri-templates/ I thought
On Mon, May 14, 2012 at 5:34 PM, Matthew Wilcox m...@matthewwilcox.com wrote:
Thanks for the feedback. Please also forgive me not being too
technically aware of things at a browser level; so I'm not really sure
how valid my feedback can be:
The URI thing is actually using URI Templates, which
All good points, thanks. Sorry I'd missed you saying style rather
than link/, my bad!
I had assumed that we would be able to take the logic for resolving
media query applicability directly from that in CSS, which is why I
have not given it any further thought. It seemed like a solved issue.
I
On 5/14/12 11:55 AM, Tab Atkins Jr. wrote:
That's why I mentioned an inlinestyle at the top of thebody -
I'm not sure if browsers skip past that when building the tree or not,
They certainly skip past such things when prefetching.
Putting information that needs to affect prefetching in
On Mon, May 14, 2012 at 9:31 AM, Matthew Wilcox m...@matthewwilcox.com wrote:
All good points, thanks. Sorry I'd missed you saying style rather
than link/, my bad!
I had assumed that we would be able to take the logic for resolving
media query applicability directly from that in CSS, which is
10 matches
Mail list logo
