- From: Yehuda Katz <wycats@gmail.com>
- Date: Thu, 1 Dec 2011 13:40:30 -0800
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: robert@ocallahan.org, www-style <www-style@w3.org>
- Message-ID: <CAMFeDTUzzMgf85cBx0KgGWRXfwnpmvEsR1r50MT4WiOhiXFu3A@mail.gmail.com>
Yehuda Katz (ph) 718.877.1325 On Thu, Dec 1, 2011 at 9:17 AM, Rik Cabanier <cabanier@gmail.com> wrote: > 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. > Or we can provide both, as I suggested earlier. "The math" is non-trivial for the average developer. > > 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 21:41:20 UTC