It can’t have started happening earlier than 2016-03-11, which is when touch selection landed in the browser :) That said, I’m aware that this is annoying for the common use case, and we need this additional API in oxide to fix it in the browser.
It can’t have started happening earlier than 2016-03-11, which is when touch selection landed in the browser :)
That said, I’m aware that this is annoying for the common use case, and we need this additional API in oxide to fix it in the browser.