- From: Rik Cabanier <cabanier@gmail.com>
- Date: Thu, 1 Dec 2011 09:17:34 -0800
- To: robert@ocallahan.org
- Cc: www-style <www-style@w3.org>
- Message-ID: <CAGN7qDBsKVfvah+bvRkDEmF6U059a6E0=NpTBDdLaS1A0bw55Q@mail.gmail.com>
That was just an example. My point was that information is lost if you append all the transforms. Better to give back the untransformed bounds and tell the user to do the math himself. Rik On Thu, Dec 1, 2011 at 2:55 AM, Robert O'Callahan <robert@ocallahan.org>wrote: > On Thu, Dec 1, 2011 at 5:37 PM, Rik Cabanier <cabanier@gmail.com> wrote: > >> It seems like you shouldn't take the transform into account since the >> axis-aligned box will be too big. >> ie if you were to use the getClientRects API for hit detection and you >> have 2 neighboring and skewed or rotated elements, their boxes will overlap. >> > > You shouldn't use getClientRects for hit detection. But if getClientRects > doesn't take transforms into account, it's even more useless for hit > detection. > > Rob > -- > "If we claim to be without sin, we deceive ourselves and the truth is not > in us. If we confess our sins, he is faithful and just and will forgive us > our sins and purify us from all unrighteousness. If we claim we have not > sinned, we make him out to be a liar and his word is not in us." [1 John > 1:8-10] >
Received on Thursday, 1 December 2011 17:18:27 UTC