New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 131 users
Status: Fixed
Owner:
Last visit > 30 days ago
Closed: May 2012
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
Excessive layerX/layerY deprecation messages
Reported by dave.met...@gmail.com, Oct 26 2011 Back to list
Chrome Version       : 16.0.912.4
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: OK
  Firefox 4.x: OK
     IE 7/8/9: OK

What steps will reproduce the problem?
1. Load jQuery 1.6.4 or earlier.
2. Note the messages "event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future."
3.

What is the expected result?

At most, a single message indicating deprecation.

What happens instead?

The messages occur for *every* event processed, filling the console.

Please provide any additional information below. Attach a screenshot if possible.

jQuery 1.7rc1 does not attempt to reference event.layerX/layerY but existing jQuery users will see a flood of messages and have no way to eliminate them other than upgrading.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1



 
Comment 1 by jry...@gmail.com, Nov 3 2011
I can confirm that this happens with Chrome version 17.0.926.0 for Ubuntu 11.04.

As shown on this test page (http://jsfiddle.net/jryans/kaRJg/1/) after clicking the test div, the warning mentioned above is produced twice on each click, likely due to jQuery checking the mentioned properties.

With the latest version of jQuery (http://jsfiddle.net/jryans/kaRJg/2/), the message is no longer shown.
Comment 2 by Deleted ...@, Nov 4 2011
Yes, after updating jQuery to the latest version 1.7 (http://code.jquery.com/jquery-1.7.js), this warning no longer shown in Chrome.
By the way, does that mean older jQuery versions will be broken in upcoming versions of Chrome?
@dvdsv..., older jQuery versions will not be "broken" in the sense that the web page should function fine. However, your console will have a LOT of those deprecation messages, and new ones will appear in the console each time jQuery handles an event. This ticket is requesting that Chrome only generate one of those per page.

dave.met... : I'm sorry, maybe I'm getting it wrong - did you mean it's gonna be like that, I mean with warning messages even when layerX/Y is actually dropped ("undefined")?
In jQuery 1.7: No layerX/Y messages from Chrome.

In older versions: The number of layerX/Y messages in Chrome depends on the resolution of this ticket. I have no idea how the Chrome team will resolve the ticket. They could remove the message entirely, reduce it to a single message per page, or leave it as-is where there is a message every time jQuery handles an event.
Comment 7 by anyr...@gmail.com, Nov 8 2011
In my opinion you have to look at it from the users (user of the browser) point of view as well. 
In that scenario upgrading the jQuery version to 1.7 is not really relevant. 
The user has to use what ever jQuery version the page has to offer. I have experienced really bad performance on heavy jQuery sites because of this extensive warning reporting in the console.
If the page has some kind of jQuery event hooked to the mousemove event, the userinterface is pretty much useless and I have to switch back to firefox to get the work done.
Reporting the warning once per page sounds like a good solution to this issue.
Comment 8 by nor...@gmail.com, Nov 8 2011
Is there a need for this warning?
Comment 9 by bla...@gmail.com, Nov 9 2011
Can the chrome team please remove this warning message?  It is ridiculous especially when it triggers on every tick of a mouseover event.
Comment 11 by jry...@gmail.com, Nov 10 2011
As noted in the jQuery release notes above, they've removed these properties specifically because Chrome generates so many messages.

However, the reporter's issue still stands, as sites with older versions of jQuery will experience the behavior.
using Gmail, I just got 79460 (yes, more than seventy-nine thousand) of these.
by the way, this issue is not Windows specific.
Comment 13 by jry...@gmail.com, Nov 29 2011
Cc: jry...@gmail.com
Totally agree. One deprecation warning per each pixel is simply a bug IMHO
I am not using jQuery and I scoured my code and there isn't a single reference to layerX or layerY!
Comment 16 by adys...@gmail.com, Dec 16 2011
Warnings can be triggered by extensions using jquery.
Same here.. Why this warning?
It's fixed in jquery, but should be fixed in chrome aswell  +1
Comment 19 by Deleted ...@, Dec 19 2011
@17 for exactly the reason specified: the `event.layerX` and `event.layerY` properties have been deprecated in Webkit, so it warns callers of these properties (~~ developers using them) that it's not going to work anymore.

The issue is that instead of warning once (per session/page) it warns on each access, leading to spam even in code which does not effectively need these properties (merely tests if they exist), such as jQuery pre 1.7
Comment 20 by volom...@gmail.com, Dec 20 2011
I'm a web developer. I'm now getting this like mad in the very latest stable release of Google Chrome for Ubuntu Linux (16.0.912.63). Please fix. I upgraded to the latest stable release of jQuery 1.7.1 and I'm still encountering this bug like crazy. It could lead my customers to think something is broken when it's not.
Comment 21 by latch...@gmail.com, Dec 20 2011
Why would your customers be looking at the devtools console in order to evaluate your product?

Sure, I'm annoyed by this as well, but at this point, I pretty much just ignore it.
Comment 22 by Deleted ...@, Dec 20 2011
For what reason is Chrome even removing support of the layerX and layerY ?  Is it to fix that god forsaken dropdown menu?  Is it because someone on the chrome team got all pissy and decided he/she wanted it removed?  I would like to know why it is being removed and how it is going to "help" the browser.

If there is not a single improvement, or if the layerX and LayerY doesn't hamper any future development, then the better question is: why is the Chrome team removing it?

Obviously this is something that is going to break many many many versions of a widely used language, not to mention bring Google into playing the same game of "we break the internet cuz we can" that microsoft played (and LOST)...

Everytime I think we're getting closer to cross-browser compliance, stupid crap this just pisses me off.
Comment 23 by adys...@gmail.com, Dec 20 2011
@jhibb
layerX/layerY are non-standard properties. Removing them has everything to do with cross-browser compliance, and nothing to do with "breaking the internet".

Put the tinfoil hat away because honestly, it's extremely annoying to read comments like that that border on trolling.

Triagers?
+OS-All
+Area-Webkit
Comment 24 by aven...@gmail.com, Dec 20 2011
@adys

I think this sort of bug is drawing a lot of attention to this issue and thus quite a few people (myself included) are being brought here after starring the issue...

Could we at the very minimum change such frequently displaying to display once? I appreciate those are deprecated properties and as such should be removed.

Think about the impact be on sites running older versions of libraries such as jQuery that are locked in due to versioning/testing constraints. People can't just upgrade away to fix this message...
Comment 25 by adys...@gmail.com, Dec 20 2011
As the message itself shows, layerX/layerY will be eventually removed, getting rid of the warning.
Comment 26 by aven...@gmail.com, Dec 20 2011
@adys

When Chrome 17 ships, which will be in 3-4 weeks soonest? I think the general consensus here is that nobody wants to wait that long and a hotfix release is needed to reduce the error message's occurrence.
Comment 27 Deleted
Comment 28 by Deleted ...@, Dec 22 2011
@adys:
layerX/layerY may be non-standard properties, but the fact is the properties were available (and responded correctly!) through webkit, giving an impression it was there to stay (thus giving the jQuery team an understanding to use it within every build prior to the 1.7.1 series)..

With that being said, cross-browser compliance is great and all, but if that's the case then they need to remove all web-kit calls.. but i'll stop there before this truly turns into a troll ;)

If they are removing the options for standards purposes, great.  Just wish that if the layerx/layery were always non-standard properties that they wouldn't have introduced it.  it's obviously a huge annoyance that they'd wait until version 17 of chrome to decide to remove it =\ oh well... 

As for the troll comment, I'd appreciate you to cease from attempts at belittling those you have never met nor know anything about.  The majority of people posting here are looking for answers and hopefully solutions to a very irritating issue, not for someone to try and start personal attacks and turn this into a pissing contest.
Labels: -Area-Undefined -OS-Windows Area-WebKit OS-All
Comment 30 by kareng@google.com, Jan 24 2012
Owner: pfeldman@chromium.org
Status: Assigned
Please remove warnings
Comment 32 by Deleted ...@, Feb 16 2012
This warning is repeated even without jquery.
I tried to add eventListener as it is described in Mozilla web site. As I remember I got the warning :(
Just noticed this problem today, someone said to update my jQuery to 1.7.1 on the website I'm currently working on to solve the issues... the problem being is that I'm already running that so seems to signal a Chrome issue
Is anyone on the Chromium team addressing this bug? I'm on jQuery 1.7.2 with no extensions and still have this error on Ubuntu Linux 10.04 with Google Chrome 18.0.1025.142.

If I knew C++ and how to compile GCC well enough along with all the dependencies, I'd be trying to fix this myself by simply commenting out the error. But I don't.

Is the warning showing Ubuntu at this link?
http://jsfiddle.net/jryans/kaRJg/2/
Its the same link that is shown above near the top. It doesn't show with jquery 1.7.1 or 1.7.2 in windows + chrome
Not for me.
Chrome 18.0.1025.142 Ubuntu 11.04
Comment 37 by dtc....@gmail.com, Apr 8 2012
18.0.1025.142 (Developer Build 129054 Linux) Ubuntu 11.10 (default chromium from repositories).
Fixed in jsfiddle.net link above, but older versions of jQuery still cause these messages on few other sites - so it's not fixed in Chrome itself.
I am running Ubuntu 10.04.4 LTS (2.6.32-40-generic #87-Ubuntu SMP Mon Mar 5 20:26:31 UTC 2012 i686 GNU/Linux). I clicked the http://jsfiddle.net/jryans/kaRJg/2/ link as directed, and then clicked the Click Me link. I do not encounter the error in that case. It just says, "click". However, clicking around on the other buttons on that page, I get the layer error.

As well, I am using the very latest jQuery on a custom website I made, with no other jQuery libs loaded, and I still encounter the error.

Cc: pfeldman@chromium.org
Owner: jchaffraix@chromium.org
Status: Fixed
We decided to remove this warning from WebKit and re-evaluate our position on the deprecation / removal.

See https://bugs.webkit.org/show_bug.cgi?id=86264 and http://trac.webkit.org/changeset/117335.
Good! Maybe a debug console? Like: All (incluing or not Debug, on config) | Errors | Warnings | Logs | Debug... So can list debug terms too, like deprecated or something like that.
The deprecation was done without considering real-world usage, the availability of a replacement and the cost of maintaining the feature (which is pretty low). Once you consider those 3 points, the consensus was for removing the warning, keeping layerX/layerY (ie not deprecating them anymore) and re-evaluating once someone has enough time to do a proper investigation.

For the record, the change was merged on the M20 so the warning should disappear with the next M20 release (> 20.0.1132.8).
"We decided to remove this warning from WebKit and re-evaluate our position on the deprecation / removal."

Remove this warning, keep layerX/Y. Removing or thinking about removing this necessary feature was a not that great of an idea.
Project Member Comment 43 by bugdroid1@chromium.org, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 44 by bugdroid1@chromium.org, Mar 11 2013
Labels: -Area-WebKit Cr-Content
Project Member Comment 45 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Sign in to add a comment