W3C home > Mailing lists > Public > www-style@w3.org > February 2015

Re: The :min-width/:max-width pseudo-classes

From: Lucas Wiener <lucas@wiener.se>
Date: Thu, 05 Feb 2015 17:03:16 +0000
Message-ID: <CAHGk_Uw0oQ15DYYHpFwmd1rJam_4p4Xa_vun1QpNoWUqVX03=w@mail.gmail.com> (sfid-20150205_170324_802332_39071E5E)
To: "www-style@w3.org" <www-style@w3.org>
> Hey Lucas,

> I suggest following the Responsive Issues Community Group (http://ricg.io/)
for up to date information and following the RICG mailing list (
http://lists.w3.org/Archives/Public/public-respimg/), you can review recent
discussions there. You can also jump onto http://irc.w3.org/ and go to
channel #respimg if you have any specific questions, but it seems like most
of the EQ progress is still at the use case and initial planning stage (
http://lists.w3.org/Archives/Public/public-respimg/2014Dec/0000.html) .

Hi Greg and thank you for your answer. The links you provided are great.
However, I am looking for a bit more technical resources that can help me
understand why exactly the proposed solution of element queries is
infeasible to implement. Sorry, I should have been more clear about this.

>From what I get of this mail conversation it is agreed that a special
viewport HTML element needs to exist, for rendering engines to be able to
know about the separate viewport before doing the layout pass. Also,
element queries should be limited to nearest viewport ancestors, in order
to be able to layout the subtrees that the viewports create in parallel. So
the only problem left is that selectors can depend on layout.

Boris Zbarsky kinda ends the conversation with:

> > The problems here are (1) selectors depending on layout

> Well, we already have this with media queries on iframes, right?

> > This still leaves us with the problem of (1), though, which is
unsurmountable given the basic concept.

> I think it's fine as long as the UA can tell where viewport boundaries
are without doing anything related to selectors.  Again, that's where we
are with iframes.

Does that mean that this is a feasible thing to implement? I know Tab is
working with coming up with use cases for element queries but is there
anyone else pushing this forward?

Thanks
Lucas Wiener

Wed Feb 04 2015 at 1:46:34 AM skrev Greg Whitworth <gwhit@microsoft.com>:

> I'm doing research regarding element queries as my master's thesis. First
> of all I wonder how this discussion is going? It seems to me like this mail
> conversation pretty much died in the middle of an interesting discussion.
> > Also, are there any other mail threads similar to this one about element
> queries? Or any other research papers or similar that you know of?
> > I'm probably bad a searching, but it seems to me that there are few
> resources that talks about the problem in detail.
> > Kind regards
> > Lucas Wiener
>
> Hey Lucas,
>
> I suggest following the Responsive Issues Community Group (http://ricg.io/)
> for up to date information and following the RICG mailing list (
> http://lists.w3.org/Archives/Public/public-respimg/), you can review
> recent discussions there. You can also jump onto http://irc.w3.org/ and
> go to channel #respimg if you have any specific questions, but it seems
> like most of the EQ progress is still at the use case and initial planning
> stage (http://lists.w3.org/Archives/Public/public-respimg/2014Dec/
> 0000.html) .
>
> ~ Greg
>
>
>
>
>
Received on Wednesday, 11 February 2015 19:53:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:01 UTC