Re: [pointerevents] [touch actions] handwriting manipulation type to distinguish panning (#516)

The way it was laid out in the explainer (and how the [affected pages counter was implemented](https://crrev.com/c/6005047)) is that having a parent that disables handwriting between the writable element and the root of the document would disable handwriting, more in line with how `pinch-zoom` works [[1](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Handwriting/HandwritingIntentCSSValue.md#determining-enablement)]. For example:
```
<style>
body {
    touch-action: none;
}
</style>
<div style="overflow: auto;background-color:lightblue;height:300px;width:300px;touch-action: auto;">
    <div style="touch-action: auto;width:500;height:500;" contenteditable="true">
        This element can pan due to the scroller allowing it, but it wouldn't have handwriting.
        The UA doesn't consume pointer events in the rest of this document.
    </div>
</div>
```
Would disable `pinch-zoom` and `handwriting` in the entirety of the page, but the div would still be touch-pannable, because the top level scroller allows it.

I think changing the enablement to work as panning does would be very effective to mitigate how many pages we cause issues for. I'll start discussing this with Olga. Thanks for the comment 👍

-- 
GitHub Notification of comment by gastonrod
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/516#issuecomment-2641135729 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 6 February 2025 21:48:36 UTC