Re: Some filter effects specification review comments

Robert O'Callahan:
>Those aren't really use-cases yet. What are situations where authors would
>be using filters like that and expecting hit-test correction to happen?

A usual use case can be a game or an artwork, where the player has to
catch a moving/morphing/vanishing/blurring object. Or one uses a filtered
element to cover other objects (partly) to prevent events for them in such
a game to make it more difficult. If the events are not related to the 
filtered output, practically one can forget filters for such applications
completely and has to solve the problem with a simpler graphical
output or some blown up source code to simulate the effect of such
filters without filters. 

For the given example with a shadow, already the name implicates, that
no event for the shadow is ok, because the shadow is not the object itself
(the naive construction of such 'shadows' by designers or here CSS is always
a source of fun for me - it does not contain important properties like 
scattering, diffraction, light source dimensions etc, but anyway...).
In case of a filter the output replaces the object effectively, therefore 
there is no presentation of the original object anymore.


Olaf

Received on Wednesday, 22 June 2011 08:37:33 UTC