W3C home > Mailing lists > Public > public-respimg@w3.org > June 2015

Re: Requirement for Element Queries

From: <george@cantinaconsulting.com>
Date: Tue, 09 Jun 2015 09:50:06 -0700 (PDT)
Message-Id: <1433868606278.f1ded8fe@Nodemailer>
To: "Mikel Zorrilla" <mzorrilla@vicomtech.org>
Cc: public-respimg@w3.org
Mikel,




A couple of questions about your example:




* Are we assuming that the elements that appear on the tablet are newly inserted into the DOM, i.e. not hidden elements? 

* Are we assuming that the containing element for the new elements (the body or some component) is further constrained by an applicable container query, media query or another CSS property?




I've attached a diagram that illustrates what I think you're suggesting as a use case. Can you confirm that I've got it right?










Also: Hello RICG! I’ve been this list quite for a while, but it’s time to start participating!




Cheers,

George




George White

george@cantina.co

stonehippo@gmail.com

















—
Sent from Mailbox

On Tue, Jun 9, 2015 at 6:00 AM, Mikel Zorrilla <mzorrilla@vicomtech.org>
wrote:

> Dear RICG.
> Please, find on this emails some comments to the "Use Cases and
> Requirements for Element Queries" draft document in
> https://responsiveimagescg.github.io/cq-usecases/ :
> We find this work very interesting since we completely agree on the need to
> "define styles within an individual module on the basis of the size of the
> module itself rather than the viewport" and "the need for a standardized
> method of allowing content to respond to its container’s dimensions".
>>From the code in GitHub you provide, we find that you enable
> container-based element queries fired by a change on the viewport size. We
> think this could be extended to a change on the size of each element. We
> are working on the MediaScape (www.mediascapeproject.eu) project, where we
> are creating tools and libraries to create a multi-device media application
> based on Web technologies. For example, if we have an application with N
> elements, and a user is consuming that application from two devices at the
> same time (let's say a TV and a tablet), the TV will show only some of the
> N elements, and the tablet will show other elements. In this scenario, if
> the user turns off the TV, all the elements will be presented in the
> tablet. All the layout in the tablet will be resized, changing the size of
> each element. The container-based element queries should be applied, even
> if there is not a viewport change event.
> We are implementing this using Web Components as the elements. We find Web
> Components interesting, since they provide the containter/element concept..
> We would like to know if you have thought about extending your proposal in
> this direction, adding this as a new requirement for the element queries.
> Don't hesitate to contact us for more explanations.
> Best regards,
> Mikel Zorrilla Berasategi
> Senior Researcher & Project Manager
> Digital Television and Multimedia Services
> Vicomtech-IK4 - Visual Interaction Communication Technologies
> Mikeletegi Pasealekua, 57 - Parque Tecnológico
> 20009 Donostia - San Sebastián - Spain
> Tel: +[34] 943 30 92 30
> Fax: +[34] 943 30 93 93
> e-mail: mzorrilla@vicomtech.org
> www.vicomtech.org
> *** member of IK4 Research Alliance ****
> www.ik4.es
> *** member of GraphicsMedia.net ****
> www.graphicsmedia.net
> -----------------------------------------------------
> Vicomtech-IK4 is an ISO 9001:2000 certified institute
> -----------------------------------------------------
> Legal Notice - Privacy policy (http://www.vicomtech.org/en/proteccion-datos)
Received on Wednesday, 10 June 2015 06:41:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 June 2015 06:41:50 UTC