W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: Adding a paint event to HTMLElement to support Web Components / Shadow DOM

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 8 May 2012 18:16:00 -0700
Message-Id: <C145F24C-1CF9-405E-B004-ECED7D4BA46B@jumis.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
On May 8, 2012, at 5:56 PM, Boris Zbarsky <bzbarsky@MIT.EDU> wrote:

> On 5/8/12 8:30 PM, Gregg Tavares (勤) wrote:
>> AFAICT the resize event only fires on window.
> 
> There have been proposals over the years to change that.


CSS Transform and zoom semantics are the steps I still don't catch in my Canvas apps. I will, once I port to web components.


> 
>> Imagine a relatively heavy to repaint WebComponent like one that draws
>> an representation of an audio wave. If that component is hidden behind
>> some other component it would be nice if it didn't re-draw itself.
> 
> This seems like a use case for requestAnimationFrame's second argument, and browser quality-of-implementation issues.
> 
>> Does a 'paint' event make sense?
> 
> Possibly, depending on how it's defined; actually running arbitrary script during painting is pretty undesirable (e.g. ideally painting happens on a totally separate thread from script, and having to synchronize them is not particularly ideal).

We've got transition end and rAF. I think we're good on this one.
> 

In fact, might just hook into the transition events with web components.
Received on Wednesday, 9 May 2012 01:16:29 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT