Re: Intent to Ship: Ignore custom cursors over 32 pixels intersecting UI

2019-03-13 Thread Emilio Cobos Álvarez
On 13/03/2019 01:46, flor...@rivoal.net wrote: > On Wednesday, March 13, 2019 at 8:36:17 AM UTC+9, Emilio Cobos Álvarez wrote: >> On 13/03/2019 00:22, Florian Rivoal wrote: >>> Given that this is not merely setting a limit because you find that >>> implementation more convenient, but actually a

Re: Intent to Ship: Ignore custom cursors over 32 pixels intersecting UI

2019-03-12 Thread florian
On Wednesday, March 13, 2019 at 8:36:17 AM UTC+9, Emilio Cobos Álvarez wrote: > On 13/03/2019 00:22, Florian Rivoal wrote: > > Given that this is not merely setting a limit because you find that > > implementation more convenient, but actually a case of considering it > > desirable to ignore

Re: Intent to Ship: Ignore custom cursors over 32 pixels intersecting UI

2019-03-12 Thread Emilio Cobos Álvarez
On 13/03/2019 00:22, flor...@rivoal.net wrote: > Given that this is not merely setting a limit because you find that > implementation more convenient, but actually a case of considering it > desirable to ignore large cursors in certain cases (and for security reasons > even), I wonder if this

Re: Intent to Ship: Ignore custom cursors over 32 pixels intersecting UI

2019-03-12 Thread florian
Given that this is not merely setting a limit because you find that implementation more convenient, but actually a case of considering it desirable to ignore large cursors in certain cases (and for security reasons even), I wonder if this is something that we should consider including in the

Intent to Ship: Ignore custom cursors over 32 pixels intersecting UI

2019-03-12 Thread Emilio Cobos Álvarez
Hi, just some email I forgot to send a while ago. Summary: Block cursor images larger than 32 pixels wide that intersect the Browser UI, by falling back to the default cursor (as if no cursor image could be loaded). This prevents malware sites from hijacking the cursor and look as if the cursor