- Issue created by @ulethjay
I was able to reproduce this—once. On subsequent tries the problem didn't occur. That's odd.
- 🇮🇳India vinmayiswamy
Hi, I’m able to reproduce this issue across multiple browsers and in a fresh Drupal 10.3.2 installation, following the steps mentioned in the issue summary. Here’s what I found:
- The issue occurs consistently in Chrome, Firefox, and Safari in both node edit and node add scenarios.
- No JavaScript errors or network issues were observed in developer tools, and there are no relevant entries in the "Recent log messages".
I’ve attached recordings showing the issue occurring in Chrome, Firefox, and Safari. If there are any further steps we should take or additional information needed, kindly please let me know.
Thanks!
No JavaScript errors or network issues were observed in developer tools
That got me wondering... If I turn off Javascript in Firefox and then visit the node form, click "Preview", then use the browser's back button, the action buttons retain their functionality.
On a whim, I've also tried turning off CSS and JS aggregation. Doing so doesn't seem to fix anything. Doesn't hurt to try.
- 🇺🇸United States mortona2k Seattle
We have some clients reporting this issue, saying the form was broken.
If you refresh, the form should keep your input and allow you to save.
However, if you change your input after previewing/clicking browser back button, then refresh, those will be lost.
Autocomplete entity reference fields keep their values after refresh, but text input does not.
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.