plasico.bg #200
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wanhose/cookie-dialog-monster#200
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue information
🖥️ Browser
Chrome (121.0.0.0)
📝 Reason
Popup showed up
🔗 URL
https://plasico.bg/laptopi-i-aksesoari/laptopi/filter-B39-B38-B40-pricestart:1600.99-priceend:1924.99-182389-180883-180882-29907,183483,183209,113703,137475,145201,185918-1271_1-154600
🏷️ Version
8.0.2
@wanhose, hi mate
I got an anomaly that I had read happens with
Firefox
.I'm using
Ungoogled Chromium v.130.0.6723.96 x64
(https://github.com/macchrome/winchrome/releases/tag/v130.6723.96-M130.0.6723.96-r1356013-Win64/).Ungoogled Chromium v.130.0.6723.96 x64
is brand new and doesn't have any ported settings, everything is default. I installedCookie dialog monster v.8.0.3
from https://chromewebstore.google.com/detail/cookie-dialog-monster/djcbfpkdhdkaflcigibkbpboflaplabgSo far it's clear.
I opened: https://plasico.bg/laptopi-i-aksesoari/laptopi/filter-B39-B38-B40-pricestart:1600.99-priceend:1924.99-182389-180883-180882-29907,183483,183209,113703,137475,145201,185918-1271_1-154600
And here is the anomaly:
The picture shows that the installed version of your extension is the latest version 8.0.3, but it says that I need to update to the latest version. There is no newer version. It's strange why it shows this message on
Ungoogled Chromium
.However, I restarted
Ungoogled Chromium v.130.0.6723.96 x64
several times to make sure, but now the extension only saysAn issue has been reported for this page. The extension may not work as expected temporarily. Follow the issue, or add more information
.Hi @Rusenche,
I see, sorry for the inconveniences. I've tried to use a native way to show that update message, but it's creating so much trouble for you. I'm going to reimagine it soon, creating an specific endpoint in our API instead of using what Chrome/Firefox provides us.
In a more technical way, the update seems to be done in the background somehow by the browser. So, one of the extension listeners responsible of hiding that message didn't listen there was an update... result, the message always displays.
I'm going to mark this as enhancement, will be ready for the next update!
Hi @Rusenche,
The issue regarding the versioning should be fixed now. Please, update to the latest version.
I'll keep it open for the other issue regarding the cookie consent dialog. Thanks again!