Meta.com: Nuisance

Mar 9, 2025 by ADMIN 19 views

Prerequisites

Before reporting this issue, please ensure that you have read and understood the policy about what is a valid filter issue. This is not a report about a YouTube, Facebook, Twitch, or a shortener/hosting site issue. If you are experiencing problems with one of these sites, please click on the respective link to report the issue.

Additionally, please verify that this issue is not a duplicate by using the button to find out. Comment in the old issue threads even when they are closed or even if you have a different problem.

URL address of the web page

The URL address of the web page that is causing the issue is https://www.meta.com/blog/ray-ban-meta-coperni-limited-edition-debut/.

Description

The issue is related to a cookie notice that is being displayed on the web page.

Other extensions used

The other extension used is Cookie AutoDelete.

Screenshot(s)

Configuration

uBlock Origin: 1.62.0
Firefox: 136
filterset (summary):
 network: 436719
 cosmetic: 246669
 scriptlet: 57974
 html: 2611
listset (total-discarded, last-updated):
 added:
  https://big.oisd.nl: 168468-229, 1m
  adguard-generic: 103639-8888, now
  adguard-spyware: 148796-5847, now
  curben-phishing: 1647-592, 1m
  adguard-cookies: 33550-120, 1m
  ublock-cookies-adguard: 3635-49, 1m
  fanboy-cookiemonster: 44772-3717, 1m
  ublock-cookies-easylist: 3635-3635, 1m
  adguard-social: 23730-60, 1m
  fanboy-social: 16637-777, 1m
  fanboy-thirdparty_social: 68-18, 1m
  adguard-popup-overlays: 28838-2273, 1m
  [8 lists not shown]: [too many]
 default:
  user-filters: 19-0, never
  ublock-filters: 40734-115, now
  ublock-badware: 11917-940, now
  ublock-privacy: 2691-56, now
  ublock-unbreak: 2620-3, now
  ublock-quick-fixes: 328-13, now
  easylist: 70596-26622, now
  easyprivacy: 53402-31338, now
  urlhaus-1: 26200-373, now
  plowe-0: 3468-2459, 1m
filterset (user): [array of 21 redacted]
trustedset:
 added: [array of 7 redacted]
 removed:
  chrome-extension-scheme
userSettings:
 advancedUserEnabled: true
 cloudStorageEnabled: true
 largeMediaSize: 70
 userFiltersTrusted: true
 webrtcIPAddressHidden: true
hiddenSettings:
 cloudStorageCompression: false
supportStats:
 allReadyAfter: 1578 ms
 maxAssetCacheWait: 753 ms
 cacheBackend: indexedDB
popupPanel:
 blocked: 2
 network:
  conversionsapigateway.com: 1
  facebook.net: 1
 extended:
  ##.AdBox
  ##.post-ads
  ##.RectangleAd
  ##a[href^="https://twitter.com/intent/tweet/?"]

Issue Details

The issue is related to a cookie notice that is being displayed on the web page. The notice is being displayed even after the user has accepted the cookies. This is causing a nuisance for the user as they are being repeatedly asked to accept the cookies.

Reproduction Steps

Open the web page https://www.meta.com/blog/ray-ban-meta-coperni-limited-edition-debut/ in Firefox.
Enable the uBlock Origin extension.
Accept the cookies on the web page.
Reload the web page.
The cookie notice will be displayed again.

Expected Result

The cookie notice should not be displayed again after the user has accepted the cookies.

Actual Result

The cookie notice is being displayed again after the user has accepted the cookies.

Additional Information

The issue is not related to any custom filters or rules. The issue is also not related to any additional filter lists. The issue is also not related to any network wide/DNS blocking or VPN.

Configuration Details

The configuration details are as follows:

uBlock Origin version: 1.62.0
Firefox version: 136
filterset (summary):

network: 436719
cosmetic: 246669
scriptlet: 57974
html: 2611

listset (total-discarded, last-updated):

added:

https://big.oisd.nl: 168468-229, 1m
adguard-generic: 103639-8888, now
adguard-spyware: 148796-5847, now
curben-phishing: 1647-592, 1m
adguard-cookies: 33550-120, 1m
ublock-cookies-adguard: 3635-49, 1m
fanboy-cookiemonster: 44772-3717, 1m
ublock-cookies-easylist: 3635-3635, 1m
adguard-social: 23730-60, 1m
fanboy-social: 16637-777, 1m
fanboy-thirdparty_social: 68-18, 1m
adguard-popup-overlays: 28838-2273, 1m
[8 lists not shown]: [too many]

default:

user-filters: 19-0, never
ublock-filters: 40734-115, now
ublock-badware: 11917-940, now
ublock-privacy: 2691-56, now
ublock-unbreak: 2620-3, now
ublock-quick-fixes: 328-13, now
easylist: 70596-26622, now
easyprivacy: 53402-31338, now
urlhaus-1: 26200-373, now
plowe-0: 3468-2459, 1m

filterset (user): [array of 21 redacted]
trustedset:

added: [array of 7 redacted]

removed:

chrome-extension-scheme

userSettings:

advancedUserEnabled: true
cloudStorageEnabled: true
largeMediaSize: 70
userFiltersTrusted: true
webrtcIPAddressHidden: true

hiddenSettings:

cloudStorageCompression: false

supportStats:

allReadyAfter: 1578 ms
maxAssetCacheWait: 753 ms
cacheBackend: indexedDB

popupPanel:

blocked: 2
network:

conversionsapigateway.com: 1
facebook.net: 1

extended:

##.AdBox
##.post-ads
##.RectangleAd
##a[href^="https://twitter.com/intent/tweet/?"]
meta.com: nuisance Q&A =========================

Q: What is the issue with the meta.com website?

A: The issue is related to a cookie notice that is being displayed on the web page. The notice is being displayed even after the user has accepted the cookies.

Q: Why is the cookie notice being displayed again?

A: The cookie notice is being displayed again because the user's acceptance of the cookies is not being properly stored or recognized by the website.

Q: Is this issue related to any custom filters or rules?

A: No, this issue is not related to any custom filters or rules. The issue is also not related to any additional filter lists.

Q: Is this issue related to any network wide/DNS blocking or VPN?

A: No, this issue is not related to any network wide/DNS blocking or VPN.

Q: What are the reproduction steps to reproduce this issue?

A: The reproduction steps are as follows:

Open the web page https://www.meta.com/blog/ray-ban-meta-coperni-limited-edition-debut/ in Firefox.
Enable the uBlock Origin extension.
Accept the cookies on the web page.
Reload the web page.
The cookie notice will be displayed again.

Q: What is the expected result?

A: The expected result is that the cookie notice should not be displayed again after the user has accepted the cookies.

Q: What is the actual result?

A: The actual result is that the cookie notice is being displayed again after the user has accepted the cookies.

Q: What are the configuration details?

A: The configuration details are as follows:

uBlock Origin version: 1.62.0
Firefox version: 136
filterset (summary):

network: 436719
cosmetic: 246669
scriptlet: 57974
html: 2611

listset (total-discarded, last-updated):

added:

https://big.oisd.nl: 168468-229, 1m
adguard-generic: 103639-8888, now
adguard-spyware: 148796-5847, now
curben-phishing: 1647-592, 1m
adguard-cookies: 33550-120, 1m
ublock-cookies-adguard: 3635-49, 1m
fanboy-cookiemonster: 44772-3717, 1m
ublock-cookies-easylist: 3635-3635, 1m
adguard-social: 23730-60, 1m
fanboy-social: 16637-777, 1m
fanboy-thirdparty_social: 68-18, 1m
adguard-popup-overlays: 28838-2273, 1m
[8 lists not shown]: [too many]

default:

user-filters: 19-0, never
ublock-filters: 40734-115, now
ublock-badware: 11917-940, now
ublock-privacy: 2691-56, now
ublock-unbreak: 2620-3, now
ublock-quick-fixes: 328-13, now
easylist: 70596-26622, now
easyprivacy: 53402-31338, now
urlhaus-1: 26200-373, now
plowe-0: 3468-2459, 1m

filterset (user): [array of 21 redacted]
trustedset:

added: [array of 7 redacted]

removed:

chrome-extension-scheme

userSettings:

advancedUserEnabled: true
cloudStorageEnabled: true
largeMediaSize: 70
userFiltersTrusted: true
webrtcIPAddressHidden: true

hiddenSettings:

cloudStorageCompression: false

supportStats:

allReadyAfter: 1578 ms
maxAssetCacheWait: 753 ms
cacheBackend: indexedDB

popupPanel:

blocked: 2
network:

conversionsapigateway.com: 1
facebook.net: 1

extended:

##.AdBox
##.post-ads
##.RectangleAd
##a[href^="https://twitter.com/intent/tweet/?"]

Q: How can I help to resolve this issue?

A: You can help to resolve this issue by providing more information about the issue, such as the exact steps to reproduce the issue, the configuration details, and any other relevant information. Additionally, you can try to reproduce the issue on a different browser or device to see if the issue is specific to a particular browser or device.