fix(std): prevent unexpected touch behavior

[EYHN]

Currently, unexpected drags will be triggered on touch screens.

I recommended to ignore touch events until we implement better touch logic.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
blocksuite	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 22, 2024 2:18pm

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
blocksuite-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 22, 2024 2:18pm

[graphite-app[bot]]

Your org has enabled the Graphite merge queue for merging into master

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

[EYHN]

• #6818 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @EYHN and the rest of your teammates on Graphite

[Saul-Mirone]

My suggestion is that we should not introduce changes before adding support for touch screens.

[Flrande]

I think we need to support a "read-only" mode like other products, as the reading experience on mobile devices is very poor now.

[EYHN]

I think we will eventually need to rewrite a completely different set of operation logic for touch, and before that it is appropriate to completely separate pointer events from touch events.

The result of this change is acceptable to me (can do simple text editing), but it may make some operations that were previously possible with the touch screen unavailable (the toolbar is not clickable).