Re: [csswg-drafts] [css-ui] Be more precise about event dispatching of pointer events on the ellipsis

There is more to it than just whether the "..." generated content has pointer-events:none set to it or not. 

Edge's current behavior is explained as we simply do not render anything so when you click the ... or beyond the ... there is no element to meet your click, which is not interoperable. We _might_ want to rethink this. If we do, I prefer Firefox's behavior and I think it matches the spec more closely. In Chrome, spans that are displayed after the ... (in the padding) are able to get :hover so the "..." eating the click is more likely an oversight than an actual design choice.

![image]( ![image]( ![image](

GitHub Notification of comment by FremyCompany
Please view or discuss this issue at using your GitHub account

Received on Friday, 21 July 2017 19:57:00 UTC