Our aging version of Dojo threatens Chrome support

[Dan Scott]

Trying out the new autosuggest functionality in master in Chromium generates many of the following warning messages:

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

The Dojo team already knows about this (http://bugs.dojotoolkit.org/ticket/14114) and has a fix for current Dojo (http://bugs.dojotoolkit.org/changeset/27949/dojo), but the musty old Dojo 1.3.x that we still depend upon isn't going to be getting any love.

[Lebbeous Fogle-Weekley (lebbeous)]

So while in the abstract I agree with the seriousness of this, since we have a plan in place for our GSoC student to help us make the transition to a newer version of Dojo, we don't really want to leave this set to "High" importance, blocking the official 2.2.0 release, agreed?

Since Joseph's going to help us after 2.2, I'm lowering this to medium for now.

[Dan Scott (denials)]

Sure. At the time I opened this bug, I don't think we had agreed on "High" == "Blocker".

Also note that this bug was deliberately not targeted at any particular release. It's simply meant to track an important infrastructural concern for the project.

I'm looking forward to Joseph propelling us into the future!

[Lebbeous Fogle-Weekley (lebbeous)]

Totally! Very excited here about Joseph freeing us of some old chains and enabling better things.

[Dan Scott (denials)]

From the Dojo trac ticket (5 months ago):

"""
Webkit is having a change of heart on this matter:

 https://bugs.webkit.org/show_bug.cgi?id=21868#c21 states:

"
For the record, we have decided to remove the warning for several reasons:

    we need to assess the web-compatibility issues.
    we need to engage the standard bodies to get a replacement.
"
"""

[Ben Shum (bshum)]

Sounds like this issue is past. Marking bug invalid.