I'm using Firefox, updated to version 140.0.4, on my Windows 11 laptop. Since Edge is my primary browser, I normally only use Firefox for two particular websites that don… (read more)
I'm using Firefox, updated to version 140.0.4, on my Windows 11 laptop. Since Edge is my primary browser, I normally only use Firefox for two particular websites that don't work well in Edge. Beginning in March 2025, I've had a strange problem with one of those websites. In certain situations, words or phrases pop up in text boxes, meaning that if I want to type something, I first have to delete the word or phrase. Since it's a game website (not a video type game -- actually contract bridge) and the game is somewhat time-sensitive, this is very annoying. The words and phrases are ones that are appropriate to the website (i.e., not random), and seem to be the same in each session. That's why I labeled this as a "clipboard-related" issue.
Clearing the cache seems to help for a short time, but the problem always returns. <Ctrl>-F5 also helps, but seems to work for some text boxes but not others. In fact, <Ctrl>-F5 works for one type of text box, the type that I use most often, for the remainder of that session. But if I use one of the other text boxes, it doesn't help.
If that isn't strange enough, there are two additional oddities: For the other text boxes, the ones that are unaffected by <Ctrl>-F5, if I continue to use them, they eventually stop popping up words and phrases, again just for the remainder of that session.
The other oddity is that I'm using the free version of the LastPass plugin, and every time one of these words or phrases pops up, the LastPass symbol (a red box with three white dots) also appears at the right of the text box. This is completely inappropriate, since these text boxes have nothing to do with logging in or passwords. For this reason, I'm going to try to contact LastPass to ask about the same issue. However, their support isn't very responsive, so I'm hoping that somebody in the Mozilla forum will have a solution.
As I said, the problem only occurs on this one bridge website, and although I've been using Firefox to access it for several years, the issue never occurred before March 2025.