Forums

WordPress › Support » Plugins and Hacks

Front-end Editor
FEE with 3.3 (3 posts)

  1. DRSK
    Member
    Posted 5 months ago #

    Hello,

    I was previously on version 2.1.3 of FEE and I got plenty of these errors:
    event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.

    So I figured perhaps 2.2 could solve it but I was wrong. Instead of occuring every now and then these errors happen when moving the cursor around on the website:
    10002 event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.

    Where this error has repeated 10.002 times, my guess is it's because WP 3.3 uses jQuery 1.7 where event.layerX/Y produces this error. If this is already known feel free to remove this thread.

    I really like FEE and I'd love to use it with WordPress 3.3 without these warnings!

    Best regards,
    DRSK

    http://wordpress.org/extend/plugins/front-end-editor/

  2. scribu
    Member
    Posted 5 months ago #

    This is caused by the Aloha Editor that FEE uses. The issue has been reported upstream:

    https://github.com/alohaeditor/Aloha-Editor/issues/381

    It shouldn't affect your usage of FEE, though.

  3. DRSK
    Member
    Posted 5 months ago #

    Update:

    This log message is related to jQuery 1.6.x (was fixed in 1.7.x; Removed Features @ http://blog.jquery.com/2011/11/03/jquery-1-7-released/ ) -- with the next update of jQuery in Aloha this will be fixed.
    - evo42 @ github

    From jQuery blog

    REMOVED FEATURES

    event.layerX and event.layerY: We have removed these non-standard properties in version 1.7. Although we normally would have gone through a deprecation notice period for these, Chrome version 16 generates a flood of console warning messages on the page. Because of this, we decided to remove them immediately. On platforms that still support these properties, they are available through event.originalEvent.layerX and event.originalEvent.layerY.

    Thought it was worth updating for people wondering!

Reply

You must log in to post.

About this Plugin

About this Topic

Tags