How to understand what is the cause of the glitch in ff?

Question

JavaScript

In ff (the last one, it is on auto-update), I observe an incomprehensible glitch.
There is a simple html page with a form that is loaded along with the page and sent via Ajax, but before submitting the form, the fields are disabled (disabled) so that there are no edits while the request is being processed.
If, after such a submission, you simply refresh the page with f5, then the page is reloaded, the form is loaded along with the page, but the form fields remain disabled, and for example, the radio buttons retain their selection, which was made when submitting the form. It feels like ff somehow cached this block and inserted it.
If you look at the source code of the page after loading, then the form is clean, there is no disabled in html, if you look at the result of loading through the console or firebug, you can see that the page also comes clean. All headers and meta are spelled out so that the page is not cached. You can only reset it by resetting the cache by pressing CTRL+F5.
At first I sinned on javascripts, but between pressing F5 I delete all javascripts from the page, refresh the page, the page is returned in its original form along with the form, not a single script is executed, but the form is miraculously displayed with disabled fields and with selected radio buttons.
How does this happen and how to overcome it? I didn’t notice this in other browsers, and in ff it doesn’t always happen, I wouldn’t have noticed if I hadn’t tested the page.
How else can you tell ff to never cache a page under any circumstances?..

Answer 1

here is my personal psychic will come out of vacation then and help
in the meantime the code to the studio