Bugzilla

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

In an existing website that uses Turbolinks, I recently (v75) started to notice form fields begin to be filled in with values from similar form fields on different, prior visited urls.

A simple example is https://horse-eastern-coral.glitch.me/ if you do the following:

1. view index.html and select a value from the dropdown (like "Mustard")
2. refresh the page; prior value is filled in
3. navigate to one.html
4. refresh the page; prior value from index is filled in
5. (optional) navigate to two.html which pre-selects `Barbecue` from the html
6. refresh the page; prior value from index is filled in

More info can be found at https://github.com/turbolinks/turbolinks/issues/536 where it was assumed there may be an issue with Firefox's cache performing differently when history state is pushed/replaced.

I did not notice an issue until recently and I'm on Mac Catalina 10.15.4


Actual results:

A selected dropdown value from an old page is pre-filled as the `<select>`'d option even if I am on a different url.


Expected results:

I would not expect any of the situations to pre-fill an existing form field value after I refresh the page. It would probably be fine for the value to be pre-selected on the same url (step 2), but I would not at all expect that value to show up on other pages (step 4 and 6).

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

In an existing website that uses Turbolinks, I recently (v75) started to notice form fields begin to be filled in with values from similar form fields on different, prior visited urls.

A simple example is https://horse-eastern-coral.glitch.me/index.html if you do the following:

1. view index.html and select a value from the dropdown (like "Mustard")
2. refresh the page; prior value is filled in
3. navigate to one.html
4. refresh the page; prior value from index is filled in
5. (optional) navigate to two.html which pre-selects `Barbecue` from the html
6. refresh the page; prior value from index is filled in

More info can be found at https://github.com/turbolinks/turbolinks/issues/536 where it was assumed there may be an issue with Firefox's cache performing differently when history state is pushed/replaced.

I did not notice an issue until recently and I'm on Mac Catalina 10.15.4


Actual results:

A selected dropdown value from an old page is pre-filled as the `<select>`'d option even if I am on a different url.


Expected results:

I would not expect any of the situations to pre-fill an existing form field value after I refresh the page. It would probably be fine for the value to be pre-selected on the same url (step 2), but I would not at all expect that value to show up on other pages (step 4 and 6).