Bug 223632 - CORS error on ResizeObserver loop
Summary: CORS error on ResizeObserver loop
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-23 03:49 PDT by vitekio
Modified: 2021-03-23 23:58 PDT (History)
0 users

See Also:


Attachments
CORS error on ResizeObserver loop (134.73 KB, image/png)
2021-03-23 03:49 PDT, vitekio
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description vitekio 2021-03-23 03:49:21 PDT
Created attachment 424008 [details]
CORS error on ResizeObserver loop

'ResizeObserver loop completed with undelivered notifications' error is causing the CORS error why?
User sees only 'Script error. Error in cross-origin script..'.
It looks like a default message when an error has no file, line, or column, which is usually the case for security reasons on CORS error.
The 'ResizeObserver loop' error shouldn't cause an artificial CORS error.
Comment 1 Alexey Proskuryakov 2021-03-23 15:54:00 PDT
The ResizeObserver error appears to be an uncaught exception, and some JavaScript code (possibly in window.onerror) reports it. There is no evidence of a browser engine bug here, this all looks normal.

The link displayed by the handler (https://blog.sentry.io/2016/05/17/what-is-script-error) has some reasonable looking explanation too.
Comment 2 vitekio 2021-03-23 23:58:29 PDT
(In reply to Alexey Proskuryakov from comment #1)
> The ResizeObserver error appears to be an uncaught exception, and some
> JavaScript code (possibly in window.onerror) reports it. There is no
> evidence of a browser engine bug here, this all looks normal.
> 
> The link displayed by the handler
> (https://blog.sentry.io/2016/05/17/what-is-script-error) has some reasonable
> looking explanation too.

Initially, the issue is, why does 'cross-origin' error occur on ResizeObserver loop?