You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching for cookies in the website, there are several instances where it's supposedly referenced, but when searching for it, it's not there. And example of which is in "Loading data" section of the SvelteKit documentation. The link is there, it shows up in the "On this page" section, but it's simply not present and the link leads to no where. Another place I saw this is in Reference > @sveltejs/kit. Cookies is, once again, in the "On this page" section, but doesn't actually lead to anywhere on the page.
The text was updated successfully, but these errors were encountered:
I think this is an ad blocker interfering and hiding the <h2 id="Cookies">. I don't know whether we should try to come up with another name for these sections because of that. It's arguably the adblock lists' fault for being too broad in their selectors.
Yup, confirmed. This doesn't happen with uBlock Origin's default set of block lists, but it does if you enable the "EasyList/uBO – Cookie Notices" one. (It does not happen with the "AdGuard/uBO – Cookie Notices" list.) That it doesn't happen with the default set of adblocking filters makes me less inclined to do anything about this. If you're seeing this happen on the site, you've presumably additionally opted into blocking cookie notices, along with whatever other false positives that may result in.
When searching for cookies in the website, there are several instances where it's supposedly referenced, but when searching for it, it's not there. And example of which is in "Loading data" section of the SvelteKit documentation. The link is there, it shows up in the "On this page" section, but it's simply not present and the link leads to no where. Another place I saw this is in Reference > @sveltejs/kit. Cookies is, once again, in the "On this page" section, but doesn't actually lead to anywhere on the page.
The text was updated successfully, but these errors were encountered: