WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 2 years ago

#42912 closed defect (bug) (wontfix)

JavaScript Error with Emoji Script

Reported by: Presskopp Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Emoji Keywords:
Focuses: Cc:

Description

In rare cases, I get the following error after logging in, but can't force it to reproduce so I will wait sometimes a day or more until it happens again:

Failed to execute 'observe', parameter 1 is not of type 'Node' in this line:

https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/wp-emoji.js#L116

.observe( document.body, {

Attachments (3)

NODE-ERROR.jpg (28.7 KB) - added by Presskopp 4 years ago.
still.jpg (22.8 KB) - added by Presskopp 3 years ago.
Screenshot (1).png (299.2 KB) - added by simplyniknaks 3 years ago.
Screenshot of error message for this problem when opening console

Download all attachments as: .zip

Change History (5)

@Presskopp
4 years ago

@Presskopp
3 years ago

#1 @simplyniknaks
3 years ago

Yes I get the same error as well sometimes so would be interested in a solution.

So far it has only happened when using the Chrome browser - changing to a different computer or a different browser on same computer and it does not happen. Sometimes it goes away after a few days but I have 1 laptop where it has not gone away (but again only when using Chrome).

I think it may be some caching issue but do not know where to start looking looking or how to resolve.

@simplyniknaks
3 years ago

Screenshot of error message for this problem when opening console

#2 @pento
2 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I'm not sure how to reproduce this: the load() function (where this error is occurring), is only called after the DOMContentLoaded event fires, so document.body should be ready at that point.

Without a clear method to reproduce this, I'm going to close this issue for now. It can be reopened if a reliable method to reproduce this issue is discovered.

Note: See TracTickets for help on using tickets.