- From: Jihye Hong via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2019 08:59:43 +0000
- To: public-css-archive@w3.org
> Sounds OK if you remove the visibleOnly argument (it will have no effect?) and stop saying "DOM anchor" (use "boundary box" instead). The DOM anchor of an <area> is its <img>. An <area>'s <img> can be [partly] visible while the <area> itself isn't.. `visibleOnly` argument affects the result of focusables depending on its value, and its **default value is `true`**. This detailed description about `visibleOnly` is related to [focusableAreas() API](https://drafts.csswg.org/css-nav-1/#dom-element-focusableareas). So, please just take account when `true` is given to `visibleOnly` for the default behavior of spatial navigation. (If it is specified with `true` , focusables are the set of all the focusable areas which are visually inside the border boundary of the container. Else, focusables are the set of all the focusable areas (including invisible ones) which are children of the container.) > Let insiders be the set of focusable areas whose boundary boxes are completely inside searchOrigin. Thanks, your description is simpler. -- GitHub Notification of comment by jihyerish Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3965#issuecomment-501184071 using your GitHub account
Received on Wednesday, 12 June 2019 08:59:45 UTC