Firefox doesn't remembers form data (OCLC's WMS forms)
Categories
(Toolkit :: Form Autofill, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox139 | --- | wontfix |
| firefox140 | --- | wontfix |
| firefox141 | --- | wontfix |
| firefox142 | --- | wontfix |
People
(Reporter: wynd.kathleen, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
154.34 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
I enter the same notes again and again in fields . Example, the date, info and my intials. So Usually, I start entering the same note and I will see a list of previous notes I have entered that start with the same like 2025-04-10...I click on the one I want.
Actual results:
Tuesday Firefox was updated and the fields no longer remember the information we we enter so we have to do every note manually. The new data is no longer being remembered by the form history.
Expected results:
The new data should be remembered by the form history and should be proposed when we start entering data.
Comment 1•1 year ago
|
||
Have you already checked the History settings in Privacy and security section?
https://support.mozilla.org/en-US/kb/delete-browsing-search-download-history-firefox
| Reporter | ||
Comment 2•1 year ago
|
||
Yes, the settings are as it should be and I am not the only one experiencing this. Another colleague sees the same thing at work and at home just like me.
Comment 3•1 year ago
|
||
I haven't seen similar bug reports, for 137 or other versions.
Does it happen to any website or a specific website? For example, do you see values when clicking in the form here (Try it section), or do you see any after submitting the form and going back? https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/form
If it doesn't work also on MDN, please attach to the bug the raw content of your about:support:
- Type about:support in the address bar, press enter.
- Click
Copy raw data to clipboard. - Come back to this bug, click the
Attach new filebutton above your first comment. - Paste the content from your clipboard, add a description and hit
Submitat the bottom.
| Reporter | ||
Comment 4•1 year ago
|
||
Ah it works in MDN.
I guess it is specific to OCLC's WMS forms. Is there something to do when the problem is in a website and it only happens with Firefox? Colleagues of mine that use Edge and Chrome do not have this problem.
Thank you
Comment 5•1 year ago
|
||
I guess it is specific to OCLC's WMS forms.
This one? https://www.oclc.org/en/home.html
Is there a form available online to test? Without it, it's hard to tell why Firefox would behave differently.
Comment 6•1 year ago
|
||
Hello,
I have the same problem. I work for the website www.ofdb.de. There I fill out a lot of form lines every day with many different recurring contents. Since version 137, Firefox no longer remembers new entries. The old ones are still there. It does not work even in the same session.
Example: https://www.ofdb.de/eintragen/review/366886/
Please enter any word in the 2nd line. Then close the page and open it again. Previously, the word was suggested when you clicked in the field. Now it no longer does.
Translated with DeepL.com (free version)
Comment 7•1 year ago
|
||
The severity field is not set for this bug.
:dimi, could you have a look please?
For more information, please visit BugBot documentation.
Comment 8•1 year ago
|
||
Hi Ailea,
could you help check if you can reproduce this issue? thanks!
Comment 10•1 year ago
|
||
There are no extensions installed on both.
Its between [9c70867f, ac367fb8].
log is attached
pushlog_url:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9c70867f63dbaa2414f4d9279a83d69382155a0b&tochange=933bfbddaf61376385fb1efae72d62d81e6f8b91
Comment 11•1 year ago
•
|
||
I tried to reproduce it using the webpage from comment 6 but I am unable to create an account and log in.
Comment 12•1 year ago
|
||
The severity field is not set for this bug.
:dimi, could you have a look please?
For more information, please visit BugBot documentation.
Comment 13•1 year ago
|
||
For more information:
I have installed a fresh Windows 11 on a notebook. Everything works perfectly with version 136.0b9.
With version 137.0.1 it no longer works. Is this perhaps a help?
I tried to reproduce it using the webpage from comment 6 but I am unable to create an account and log in.<<
The problem is: it doesn't work without access data, I can't post it publicly on the net.
But I could do a test with a certain Firefox version to see if it works.
Comment 14•1 year ago
|
||
Supplement:
With version 137.0b1 it no longer works, too.
Comment 15•1 year ago
•
|
||
Hi again,
I have manage to reproduce the issue in Nightly 140.0a1, and as Dirk said, the issue is not reproducible in Fx137. Mozregression points to Bug 1949439 as the regressor.
Thanks for the details and for trying it in multiple Fx versions!
Comment 16•1 year ago
|
||
Hi Edgar, could you help take a look to see if this is related to Bug 1949439? thanks
Comment 17•1 year ago
|
||
Set release status flags based on info from the regressing bug 1949439
Updated•1 year ago
|
Comment 18•1 year ago
|
||
(In reply to Dimi Lee [:dimi] from comment #16)
Hi Edgar, could you help take a look to see if this is related to Bug 1949439? thanks
Bug 1949439 changed how the internal DOMFormBeforeSubmit event is dispatched: It is now only dispatched when the form is actually going to be submitted, whereas previously it was also dispatched whenever a submit button was clicked, even if the click didn't result in a form submission.
The site prevents the form submission when the submit button is clicked, and instead handles "submitting" the data on its own.
So yes, this is related to bug 1949439. I can make the event dispatch again whenever a submit button is clicked, but my question is: is that the expected behavior in such case? And perhaps we would need to consider other similar case if any.
Comment 19•1 year ago
|
||
:edgar, since you are the author of the regressor, bug 1949439, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 20•1 year ago
|
||
Could we get a priotity and severity set on this bug? Thanks
Updated•1 year ago
|
Comment 21•1 year ago
|
||
(I think it is S3, but feel free to correct me if you think this should have higher severity, :dimi)
Comment 22•1 year ago
|
||
We had a similar problem with our WebSite written with PrimeFaces to our customer. Unfortunately page is not available publicly.
Already asked for support, but with no answer. I can confirm however that problem started with 137 version of Firefox.
https://support.mozilla.org/en-US/questions/1531658
Comment 23•1 year ago
|
||
Edgar(In reply to Edgar Chen [:edgar] from comment #21)
(I think it is S3, but feel free to correct me if you think this should have higher severity, :dimi)
It looks like problem is still not resolved at least in our case... You can increase priority then :-)
Description
•