Разобраться с консольными ошибками в Firefox
TatianaFokina opened this issue · comments
В чём проблема?
Консольные ошибки (без включённых браузерных расширений).
Система: Windows 11.
Браузеры: Chrome Version 123.0.6312.107 (Official Build) (64-bit), Firefox 124.0.2 (64-bit).
Firefox
InstallTrigger is deprecated and will be removed in the future. tag.js:177:424
Some cookies are misusing the recommended “SameSite“ attribute
4Cookie “metrika_enabled” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite tag.js:161:13
Cookie “metrika_enabled” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite tag.js:161:13
Cookie “_ga_GH8FX28ET0” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 js:314:899
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js:314:899
Ignoring unsupported entryTypes: longtask. tag.js:401:56
Request to access cookie or storage on “)” was blocked because it came from a tracker and content blocking is enabled.
2Request to access cookie or storage on “https://mc.yandex.ru/clmap/83244811?page-url=https%3A%2F%2Fdoka.guide%2Fcss%2Fcascade%2F&pointer-click=rn%3A594426269%3Ax%3A26410%3Ay%3A50461%3At%3A44%3Ap%3AA1%3BQdA%7F%3AX%3A153%3AY%3A41&browser-info=u%3A1634062203943616919%3Av%3A1310%3Avf%3Adgbrch0rxdnnjvl5wkfze2i1r%3Arqnl%3A2%3Ast%3A1713186706&t=gdpr(14)ti(1)” was blocked because it came from a tracker and content blocking is enabled.
The resource at “https://doka.guide/fonts/graphik/graphik-regular.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. doka.guide
The resource at “https://doka.guide/fonts/spot-mono/spot-mono-light.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. doka.guide
Chrome
Uncaught (in promise) TypeError: s.request.startsWith is not a function
at sw.js:1:11550
at Generator.next ()
at sw.js:1:196
at new Promise ()
at o (sw.js:1:16)
at sw.js:1:11512The service worker navigation preload request was cancelled before 'preloadResponse' settled. If you intend to use 'preloadResponse', use waitUntil() or respondWith() to wait for the promise to settle.
8sw.js:1 Uncaught (in promise) TypeError: s.request.startsWith is not a function
at sw.js:1:11550
at Generator.next ()
at sw.js:1:196
at new Promise ()
at o (sw.js:1:16)
at sw.js:1:11512
js:1Failed to load resource: net::ERR_NAME_NOT_RESOLVED
tag.js:1Failed to load resource: net::ERR_NAME_NOT_RESOLVED
7sw.js:1 Uncaught (in promise) TypeError: s.request.startsWith is not a function
at sw.js:1:11550
at Generator.next ()
at sw.js:1:196
at new Promise ()
at o (sw.js:1:16)
at sw.js:1:11512
Как решить?
InstallTrigger
Не использовать вообще.
- Deprecate InstallTrigger, Bugzilla
- Intent to deprecate InstallTrigger, Google Chrome Groups
SameSite cookies
Issues with blocked SameSite cookies in local development environments can be fixed by temporarily disabling sameSite policies in Firefox and Chrome.
Blocked request to access cookie or storage
This is broken on Firefox 109 and later. Individual sites can be allowlisted by users by disabling Enhanced Tracking Protection for the given site. This can be done via the toggle in the shield panel or via "Manage Exceptions" in about:preferences#privacy.
Link preload was not used
Typically you need to include crossorigin in your preload. Check to see if the font loads twice in the network report. If it does, add/remove crossorigin and it may fix it.
Also check that the preload uses as="font" type="font/woff2".