W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2021

Re: [csswg-drafts] [css-box] increase pointer target size independently of element layout (#4708)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 05 May 2021 23:30:35 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-833113541-1620257432-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-box] increase pointer target size independently of element layout`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-box] increase pointer target size independently of element layout<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/4708#issuecomment-588369114<br>
&lt;dael> fantasai: Posted a link to the comment with follow-up<br>
&lt;dael> fantasai: Last time had a question for the commentor about it being a length or larger/normal/smaller<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/4708#issuecomment-588451067<br>
&lt;dael> fantasai: Commentor responded ^<br>
&lt;dael> fantasai: Example of 2 buttons side by side and explaining author would not be able to know distance. Not spec a length larger. If we made it up to UA maybe there would be overlap<br>
&lt;dael> fantasai: That was a concern by the poster. Related, plinss commented explaining what happens with 2 JS elements with extended hit area. Don't want to cover another element. Need more sophisticated logic then extending the hit area<br>
&lt;smfr> q+<br>
&lt;dael> fantasai: These points were brought up. Figured bring back to the group for discussion on how to move forward<br>
&lt;astearns> ack smfr<br>
&lt;dael> smfr: Question if we need this. Mobile browsers have something we call area hit testing. When you hit test you look in area around target that respond to events. One answer is UA should do it automatically somehow<br>
&lt;dael> florian: Tempted to agree b/c how big hit area needs to be is not something author can know. Depends on type of thing used to click, finger or stylus. Ratio between css pixels and layout. It's guesswork<br>
&lt;dael> florian: Probably UA is in better position<br>
&lt;dael> myles: Similar. If you pinch zoom finger to page changes. Anything that's fixed is not right tool<br>
&lt;dael> iank_: Trying to remember if we had this convo. We had people asking for this a while ago. might be on us to circle back with what they were after<br>
&lt;dael> astearns: Do you mean automatic for "this"<br>
&lt;dael> iank_: Not auto. A fixed length. I think chrishtr was more involved. I'm diging from my memory. But I don't think there's more we can do<br>
&lt;dael> florian: Do all browsers to area hit testing or is it apple specific?<br>
&lt;dael> smfr: Pretty sure it's mobile browsers. We do it on mobile WK. I think Android has<br>
&lt;astearns> ack fantasai<br>
&lt;fantasai> https://cloudfour.com/thinks/jagged-little-pill-issues-with-rounded-buttons/<br>
&lt;dael> iank_: I believe we have similar. Not area of expertise<br>
&lt;dael> fantasai: Illustration from issue ^ Someone writing about rounded corners on buttons reducing click area and they wanted it fixed. That's another consideration<br>
&lt;dael> fantasai: If we're seeing a lot of people doing this with hacks we should build in. If browsers can do it automatically and we don't need hacks that's idea<br>
&lt;dael> iank_: Potential for that. I have hear border radius reducing hit test. Argument for authors to opt out, particularly with large rounded corner. Unlikely there will be other elements<br>
&lt;dael> iank_: We likely should move on. Not sure how much more we can do on this today<br>
&lt;dael> plinss: I'm in favor of leaving to UA. Might be worth spec an algo to get interop<br>
&lt;dael> astearns: That would start with defining hit testing<br>
&lt;dael> florian: I believe there's an action on me for years ago to put something i spec. I don't think there's a good definition of it, so it's not in spec<br>
&lt;dael> astearns: iank_ if you can dig up the request that would be great to add to the issue<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4708#issuecomment-833113541 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 May 2021 23:31:06 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:44 UTC