W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2014

RE: [whatwg] Object.observe()able properties on the web platform

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Thu, 28 Aug 2014 22:43:42 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <5c380980d92342f2bafd3904c7d75a83@BLUPR03MB344.namprd03.prod.outlook.com>
Sounds like something worth discussing with IE devs about the feasibility in our implementation...

-----Original Message-----
From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] 
Sent: Thursday, August 28, 2014 3:38 PM
To: Boris Zbarsky
Cc: Travis Leithead; public-script-coord@w3.org
Subject: Re: [whatwg] Object.observe()able properties on the web platform

On Fri, Aug 29, 2014 at 6:45 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 8/28/14, 4:39 PM, Travis Leithead wrote:
>> and Object.observe wouldn't help either.
>
> It _could_ help if you Object.observe the getComputedStyle's 
> .backgroundColor.
>
> Actually implementing that could be pretty painful, though.  :(

I'm been visiting the Sydney office all week to discuss CSS extensibility, we discussed this a few days ago. Listening for property changes doesn't seem to be hard.  Doing it directly through O.o might be, but the system already listens for computed value changes in order to start transitions; checking for listeners and queueing a task to call them wouldn't be expensive.

~TJ
Received on Thursday, 28 August 2014 22:44:12 UTC

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