RE: FW: Pointer target size

> For target within target, this essentially makes it a minimum size requirement (since the edge of the target is also the "opposite" edge of sorts for the parent target).

> If that's intentional / lucky side effect, it should be documented/clarified as well.



Hmm, I'm not sure. The simple case (non-overlapping) is straightforward:

[Two boxes, A and B. B is to the right of A, and there's an arrow from the right edge of A, to the right edge of B.]



But for the overlapping case that logic creates a minimum within the larger target, but not the nested one. I think?



[Box A is within Box B. An arrow indicating 24px goes from the right edge of A to the right edge of B. A double-headed arrow is within box A with a question mark.]



We could accept that and keep it simple, or update to something like:



“The distance from each target’s edge to the to the furthest edge of any adjacent target is at least 24 CSS pixels, and any nested target is at least 24 CSS pixels high and wide, except when:”



Or possibly add that extra requirement after the exceptions.



Cheers,



-Alastair

Received on Monday, 2 November 2020 16:37:23 UTC