16

I just updated Chrome to version 16.0.912.63 and now I get hundreds of errors using jQuery 1.7.1. Seems to fire whenever the mouse is moved...

event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.

Should I be worried about this? Is anyone else getting these errors?

My useragent:

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7

UPDATE: In my case it was the Chrome extension "Search by Image (by Google) 1.1.0". I just had to disable it, it had nothing to do with my application.

Greg
  • 8,574
  • 21
  • 67
  • 109
  • possible duplicate of [WebKit issues with event.layerX and event.layerY](http://stackoverflow.com/questions/7825448/webkit-issues-with-event-layerx-and-event-layery) – weltraumpirat Apr 01 '12 at 09:15

3 Answers3

11

You should only worry about this if it is:

  • your website and
  • you are planning to upgrade jQuery to a version > 1.7 in the future and
  • you are using layerX and layerY all over the place

The message is just telling you that those two properties are deprecated (at least in Webkit) and will be removed from jQuery in the near future.

BoltClock
  • 700,868
  • 160
  • 1,392
  • 1,356
devnull69
  • 16,402
  • 8
  • 50
  • 61
  • It is my site. Should I wait for the next version of jQuery? or should I downgrade to version 1.7 of jQuery? – Greg Dec 15 '11 at 08:05
  • If you replace 1.7 with a newer version, layerX and layerY will stop working. So you should replace layerX and layerY in your code with whatever is supposed to replace it. Webkit will stop supporting layerX and layerY sometime in the future so you should no longer rely on them – devnull69 Dec 15 '11 at 08:08
  • Any ideas as to how I could find out what is using layerX and layerY? – Greg Dec 15 '11 at 08:48
  • Open the Javascript source code file(s) and search for "layerX" and/or "layerY" – devnull69 Dec 15 '11 at 10:22
  • 1
    I'm dumb, it wasn't my application at all, it was caused by an extension. Sorry for wasting your time. – Greg Dec 15 '11 at 11:01
  • which extension? I think I'm having the same problem, and am horribly sick of the warning messages – Kevin Dec 16 '11 at 02:34
  • @Kevin, in my case it was `Search by Image (by Google)1.1.0` that caused it! Disabling that fixed the thousands of warnings. – Christopher Dec 16 '11 at 18:58
  • damn, the famous "always-the-very-last-jquery-version.js"-thing will just kill sites with "old" styles. i never thought that this update thing will make websites unuseable ? very nice bad side-effect of a good idea. – Sliq May 16 '12 at 20:40
4

In my case it was the Chrome extension "Search by Image (by Google) 1.1.0"

Nothing to do with my application.

Disable it and you'll be free of these annoying errors.

Greg
  • 8,574
  • 21
  • 67
  • 109
-2

add js to js file footer:

(function(){
    //remove layerX and layerY
    var all = $.event.props,
    len = all.length,
    res = [];
    while (len--) {
      var el = all[len];
      if (el != 'layerX' && el != 'layerY') res.push(el);
    }
    $.event.props = res;
}());

you can try it.

Zuul
  • 16,217
  • 6
  • 61
  • 88
mdowen
  • 17
  • 2