I can reproduce as well using FF 127.0.2 on x11, ubuntu. But I can make it even odder. Select the text, right click, copy is grayed out. Hit the back button without any other interaction, then go forward again from google.com and the text will still be selected. Hit right click again, and copy is now possible. Select any other text, and it is working as expected.
So I opened dev tools and saw there were network requests for google.com and play.google.com on the ftp page when it loaded even though there is nothing in the page source that would make those requests. When I force reload with cache disabled, these requests are not present. This looks like bad behavior by google.com somehow leaking into the next page.
Is it the lack of js, not something more arcane in the ftp templating on those sites? I can reproduce all of this at http://motherfuckingwebsite.com/ which is js free, and also at https://news.ycombinator.com/, which has js (be careful to select something like "### points" below a post, which has no hyperlink)
EDIT: I guess my theory was wrong, because I read at the bottom of the bugzilla:
So the issue here is that when a page goes to BFCache, it'd set the active browsing context to null, and the page that is about to show would update the active browsing context to itself. And these two operations are racy because they are triggered in different processes with different actionId. We are going to explore some potential solutions.
Based on the comments there, by setting BFCacheInParent to false in about:config, this bug is gone for me.
heavyset_go|1 year ago
hunter2_|1 year ago
sgc|1 year ago
So I opened dev tools and saw there were network requests for google.com and play.google.com on the ftp page when it loaded even though there is nothing in the page source that would make those requests. When I force reload with cache disabled, these requests are not present. This looks like bad behavior by google.com somehow leaking into the next page.
So I found another random ftp page, and I can reproduce all of this there: https://ftp.wildfire.gov/public/incident_specific_data/
Is it the lack of js, not something more arcane in the ftp templating on those sites? I can reproduce all of this at http://motherfuckingwebsite.com/ which is js free, and also at https://news.ycombinator.com/, which has js (be careful to select something like "### points" below a post, which has no hyperlink)
EDIT: I guess my theory was wrong, because I read at the bottom of the bugzilla:
So the issue here is that when a page goes to BFCache, it'd set the active browsing context to null, and the page that is about to show would update the active browsing context to itself. And these two operations are racy because they are triggered in different processes with different actionId. We are going to explore some potential solutions.
Based on the comments there, by setting BFCacheInParent to false in about:config, this bug is gone for me.