ChatGPT keeps asking for permission to store data in persistent storage
Categories
(Firefox :: Site Permissions, defect, P3)
Tracking
()
People
(Reporter: mozilla, Assigned: mconley)
References
(Depends on 1 open bug, Regression, )
Details
(Keywords: regression, webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat:sightline][webcompat:japan])
User Story
user-impact-score:600 platform:windows,mac,linux,android impact:annoyance configuration:general affects:all branch:release diagnosis-team:privacy
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:142.0) Gecko/20100101 Firefox/142.0
Steps to reproduce:
- Open https://chatgpt.com/
- I receive a notification if content should be stored permanently. Screenshot: https://snipboard.io/nMVRBS.jpg
- I click block
Actual results:
Firefox remembers this for the current session but next time I get the message again.
Expected results:
Firefox should permanently remember that I have blocked this website from using permanent storage.
Comment 1•19 days ago
|
||
Thanks for the report. asuth pointed out an older bug that sounds similar, but asuth suggested we keep this separate for visibility. I'll mark it for the WebCompat flag, as this is a popular site and this sounds like it would be annoying for some privacy-conscious users.
Updated•18 days ago
|
Updated•17 days ago
|
Updated•17 days ago
|
Updated•17 days ago
|
Updated•17 days ago
|
Comment 2•16 days ago
|
||
I can not reproduce it on Win11x64 using FF builds 142.0.1, 144.0b1 and 145.0a1. I am not receiving the notification. I even used a localized DE 142.0 build.
Robert Orzanna, do you use any specific settings? Thank you.
Reporter | ||
Comment 3•16 days ago
|
||
Nothing special. I have a normal free account, not even Pro.
I keep seeing this message every time I open chatgpt.com.
I use ublock Origin add-on if that matters.
(In reply to Robert Orzanna from comment #3)
Nothing special. I have a normal free account, not even Pro.
I keep seeing this message every time I open chatgpt.com.
I use ublock Origin add-on if that matters.
I've been having the exact same issue as well, for maybe the last month or so. Doesn't matter how I configure my browser. It always prompts me, regardless of how I answer. I tried completely disabling it, in about:config, that that's not a solution, as it causes other sites to break.
If it's useful, I'm on macOS 15.6.1 (24G90). Firefox version 143.0.1 (aarch64).
Updated•13 days ago
|
Updated•13 days ago
|
Updated•12 days ago
|
Comment 8•12 days ago
|
||
:mconley, since you are the author of the regressor, bug 1697903, could you take a look?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 9•12 days ago
|
||
I don't think bug 1697903 is really the right regressor here. That bug removed the checkbox, but the checkbox (iirc) was completely non-functional before, which is why we removed it.
Comment hidden (off-topic) |
Comment hidden (off-topic) |
Comment 12•5 days ago
|
||
diagnosis-team:privacy, following the component change.
Comment 13•5 days ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #9)
I don't think bug 1697903 is really the right regressor here. That bug removed the checkbox, but the checkbox (iirc) was completely non-functional before, which is why we removed it.
The checkboxe allowed users to do a persistent block. With the linked patch users lost the capability to set a persistent block directly through the prompt. Maybe we should bring it back?
Assignee | ||
Comment 14•4 days ago
|
||
(In reply to Emma Zühlcke [:emz] from comment #13)
(In reply to Mike Conley (:mconley) (:⚙️) from comment #9)
I don't think bug 1697903 is really the right regressor here. That bug removed the checkbox, but the checkbox (iirc) was completely non-functional before, which is why we removed it.
The checkboxe allowed users to do a persistent block. With the linked patch users lost the capability to set a persistent block directly through the prompt. Maybe we should bring it back?
I was under the impression that the old checkbox was completely non-functional, which is why it was removed. Is that assumption false? If it is, then yes, by all means let us bring it back.
Assignee | ||
Comment 15•4 days ago
|
||
If the old checkbox was non-functional, I can confirm that adding it back causes it to behave as expected. I personally think it makes sense to put this back.
Assignee | ||
Comment 16•4 days ago
|
||
Updated•4 days ago
|
Comment 17•4 days ago
|
||
Set release status flags based on info from the regressing bug 1697903
Updated•12 hours ago
|
Description
•