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

Re: [csswg-drafts] [css-ui-4] Make selection change behavior configurable

From: Kagami Sascha Rosylight via GitHub <sysbot+gh@w3.org>
Date: Wed, 03 May 2017 03:37:02 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-298816544-1493782620-sysbot+gh@w3.org>
>In typical native apps, clicking on UI areas does not deselect any previously selected text.

I would say "it depends". For example, imagine if you use Facebook app and you somehow want to copy someone's post. The current Facebook app allows user to cleanly select text only inside the post, without copying any UI components. Deselecting works by clicking outside of the post.

![selection2](https://cloud.githubusercontent.com/assets/3396686/25647380/6fcb00aa-2ffc-11e7-8529-a06c0d1de199.gif)

The original discussion was about editor apps and I agree the new behavior is helpful there, but not for all type of apps.

> In the example you sent, if an image fails to load and the alt text is shown instead, it would not be selectable.

Specifically I mentioned Twitter there, you will not expect any images fail to load on Twitter and instead show alternative text.

-- 
GitHub Notification of comment by SaschaNaz
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1317#issuecomment-298816544 using your GitHub account
Received on Wednesday, 3 May 2017 03:37:08 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:12 UTC