Apple.com's dev console is perfectly clean with no errors or warnings

> (warning x13) Some cookies are misusing the recommended “SameSite“ attribute

> (note x9) Referrer Policy: Ignoring the less restricted referrer policy “no-referrer-when-downgrade” for the cross-site request: https://is1-ssl.mzstatic.com/image/thumb/tPJwMGtsAr_psAVlyf2...

> (warning) InstallTrigger is deprecated and will be removed in the future.

Anyways, it's suprising how many sites flat-out console errors, although they work fine. Some warnings and log messages seem reasonable and in some cases I can see them being unavoidable, but you'd think an uncaught JS exception would be addressed. google.com has 7

> (error) Uncaught TypeError: can't redefine non-configurable property "rwt"

> (error, x3) Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://play.google.com/log?format=json&hasfast=true&authuse.... (Reason: CORS request did not succeed). Status code: (null).

> (error, x3) Content-Security-Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).

Meanwhile Hacker News has 1

> This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”.

EDIT: Github has 1 error and a lot of notes

> (error) XHR GET https://github.com/settings/two_factor_authentication/holida...

I wonder what that's supposed to be.

    setInterval(function() {
        console.clear();
    }, 10);

Safari: (none)

Brave:

1. Failed to load resource: net::ERR_BLOCKED_BY_CLIENT (Brave blocking tracking image https://securemetrics.apple.com/b/ss/applestoreww/...)

2. BubbleGum::addComponent unsupported component 'TouchHoverComponent'. Reason: 'TouchHoverComponent.IS_SUPPORTED' returned false main.built.js:1

3. A form field element should have an id or name attribute on <input placeholder="Search apple.com"

Chrome:

1. A form field element should have an id or name attribute on <input placeholder="Search apple.com"

Firefox:

1. Some cookies are misusing the recommended “SameSite“ attribute (4 instances)

2. InstallTrigger is deprecated and will be removed in the future.