W3C home > Mailing lists > Public > www-style@w3.org > June 2014

Re: Cross Referencing Between Elements

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 12 Jun 2014 12:24:26 -0400
Message-ID: <5399D43A.2020308@mit.edu>
To: Marat Tanalin <mtanalin@yandex.ru>, Brian Blakely <anewpage.media@gmail.com>
CC: "www-style@w3.org" <www-style@w3.org>
> Possible performance issues are quite clear, but should probably not be a blocker to develop specs for the future

They might be if no UA is willing to implement the spec as written.

> given that some specs are developed for years while hardware performance grows constantly according to Moore's law.

Except it doesn't anymore: transistor counts are still growing at the 
same rate for now, but actual serial computation performance is growing 
much slower.  Parallelism is picking up some of the growth, which is why 
we should be making sure specs can be efficiently implemented on 
parallel hardware...

But also, even Moore's law performance growth won't help you that much 
if you change some algorithm from constant-time to quadratic.

> For now, we could limit referencing selectors to id's as well as SVG and `element()` are

This would make such proposals a lot more likely to get implemented, yes.

> Referencing by id would cover at least most basic needs of web developers as for setting a property value of an element based on computed value of a property of another element

Computed value has a separate set of cycle issues.  Brian's proposal set 
a specified value based on specified values; it did not involve computed 
values at all.

>      #aside {margin-top: computed("#h1", height); }

Probably not what you want, since I bet the computed 'height' value of 
#h1 is "auto".

-Boris
Received on Thursday, 12 June 2014 16:24:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:22 UTC