Re: Intent to ship: MouseEvent.offsetX/Y

2015-03-02 Thread Robert O'Callahan
On Tue, Mar 3, 2015 at 8:49 AM, Mike Taylor wrote: > On 3/1/15 17:58, smaug wrote: > >> Haven't changes from integer to doubles caused issues in some cases. >> Boris might recall some examples. >> > > IE just reverted from using doubles on MouseEvent for compat reasons: > https://www.w3.org/Bugs/

Re: Intent to ship: MouseEvent.offsetX/Y

2015-03-02 Thread Mike Taylor
On 3/1/15 17:58, smaug wrote: Haven't changes from integer to doubles caused issues in some cases. Boris might recall some examples. IE just reverted from using doubles on MouseEvent for compat reasons: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28029#c6 -- Mike Taylor Web Compat, Mozill

Re: Intent to ship: MouseEvent.offsetX/Y

2015-03-02 Thread Robert O'Callahan
On Mon, Mar 2, 2015 at 7:00 PM, Chris Peterson wrote: > Gecko's offsetX/Y could return doubles, for compatibility with the spec, > that are always snapped to whole numbers, for compatibility with other > browsers. > > Or Gecko could add random noise to the low bits of offsetX/Y so they are > *nev

Re: Intent to ship: MouseEvent.offsetX/Y

2015-03-01 Thread Boris Zbarsky
On 3/2/15 1:00 AM, Chris Peterson wrote: Gecko's offsetX/Y could return doubles, for compatibility with the spec, that are always snapped to whole numbers, for compatibility with other browsers. How, precisely, is this different from returning integers? Remember, this is JS we're talking abou

Re: Intent to ship: MouseEvent.offsetX/Y

2015-03-01 Thread Chris Peterson
On 2/27/15 7:25 PM, Robert O'Callahan wrote: On Sat, Feb 28, 2015 at 8:30 AM, Jeff Muizelaar wrote: >On Fri, Feb 27, 2015 at 2:21 PM, Robert O'Callahan >wrote: > >Oh, another issue is that I've followed the spec and made offsetX/Y > >doubles, whereas Blink is integers, which introduces a small

Re: Intent to ship: MouseEvent.offsetX/Y

2015-03-01 Thread smaug
On 02/28/2015 05:25 AM, Robert O'Callahan wrote: On Sat, Feb 28, 2015 at 8:30 AM, Jeff Muizelaar wrote: On Fri, Feb 27, 2015 at 2:21 PM, Robert O'Callahan wrote: Oh, another issue is that I've followed the spec and made offsetX/Y doubles, whereas Blink is integers, which introduces a small a

Re: Intent to ship: MouseEvent.offsetX/Y

2015-02-27 Thread Robert O'Callahan
On Sat, Feb 28, 2015 at 8:30 AM, Jeff Muizelaar wrote: > On Fri, Feb 27, 2015 at 2:21 PM, Robert O'Callahan > wrote: > > Oh, another issue is that I've followed the spec and made offsetX/Y > > doubles, whereas Blink is integers, which introduces a small amount > compat > > risk. > > > > IE also

Re: Intent to ship: MouseEvent.offsetX/Y

2015-02-27 Thread Jeff Muizelaar
On Fri, Feb 27, 2015 at 2:21 PM, Robert O'Callahan wrote: > Oh, another issue is that I've followed the spec and made offsetX/Y > doubles, whereas Blink is integers, which introduces a small amount compat > risk. > IE also uses integers. Wouldn't it be better to change the spec to follow the exis

Re: Intent to ship: MouseEvent.offsetX/Y

2015-02-27 Thread Robert O'Callahan
On Sat, Feb 28, 2015 at 8:15 AM, Robert O'Callahan wrote: > Summary: CSSOM Views specify offsetX/Y properties on MouseEvent. Other > browsers implement them. Many sites use it with a fallback for Firefox, but > I've found at least one site that doesn't have a fallback. It's trivial to > implement

Intent to ship: MouseEvent.offsetX/Y

2015-02-27 Thread Robert O'Callahan
Summary: CSSOM Views specify offsetX/Y properties on MouseEvent. Other browsers implement them. Many sites use it with a fallback for Firefox, but I've found at least one site that doesn't have a fallback. It's trivial to implement. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=69787 Spec: ht