Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Firefox Stops Working with JavaScript Links

  • 4 svar
  • 0 har detta problem
  • Senaste svar av SSSea

more options

Hi,

The newest Firefox has an issue with properly parsing the javascript links in the ACS research journal articles. In these research articles, citations are clickable numbers in parenthesis. Clicking on them leads to a pop-up frame that gives detailed reference article information.

However, with the latest version of Firefox these citation links will only respond properly to the first click ever on the page. After you close the pop-up frame, any subsequent clicks on any of these links will have no response.

I attach an example article below. This bug has been repeated under Trouble Shoot Mode and I do not encounter the same issue with Chrome brower. https://pubs.acs.org/doi/10.1021/jacsau.2c00048

Hi, The newest Firefox has an issue with properly parsing the javascript links in the ACS research journal articles. In these research articles, citations are clickable numbers in parenthesis. Clicking on them leads to a pop-up frame that gives detailed reference article information. However, with the latest version of Firefox these citation links will only respond properly to the first click ever on the page. After you close the pop-up frame, any subsequent clicks on any of these links will have no response. I attach an example article below. This bug has been repeated under Trouble Shoot Mode and I do not encounter the same issue with Chrome brower. https://pubs.acs.org/doi/10.1021/jacsau.2c00048
Bifogade skärmdumpar

Alla svar (4)

more options

What OS? I'm not having any issues with the pop-ups. I can also navigate using the Next and Previous option on some of the pop-up windows.


Operating System: openSUSE Leap 15.6 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.4.0-150600.23.25-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 6850HS with Radeon Graphics Memory: 62.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 865 16 inch G9 Notebook PC

Ändrad av jonzn4SUSE

Hjälpsam?

more options

Hi @jonzn4SUSE It's Windows 10. User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0 OS Windows_NT 10.0 19045

Hjälpsam?

more options

No problems here as well.

You can check the Web Console for possible JavaScript issues.

You seem to have several content blocking extensions. Did you try to reload and page and bypass the cache in Troubleshoot Mode?

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl+F5" or press "Ctrl+Shift+R" (Windows,Linux)
  • press "Command+Shift+R" (Mac)

Hjälpsam?

more options

cor-el said

No problems here as well. You can check the Web Console for possible JavaScript issues. You seem to have several content blocking extensions. Did you try to reload and page and bypass the cache in Troubleshoot Mode?

Hi cor-el, thanks for the message. As I mentioned in the original post, I have tried Troubleshoot Mode. I continue to encounter the same behavior as I use Troubleshoot Mode + force reload: (note that the first click will apparently work for some reason, but any subsequent clicks will not respond on my system. Adding much confusion) `these citation links will only respond properly to the first click ever on the page. After you close the pop-up frame, any subsequent clicks on any of these links will have no response.`

When I opened the web console, any clicks (including the first click) would give the following error, and no pop-up windows showed up: ``` Uncaught ReferenceError: ga is not defined

   clickHandler rqv.js:51
   jQuery 2
       dispatch
       handle

``` Let me know if you have the same behavior on your Windows 10 -- the inconsistency across devices made it even more puzzling to a non-developer like me (especially as this issue only appeared after the version update).

Ändrad av SSSea

Hjälpsam?

Ställ en fråga

Du måste logga in på ditt konto för att svara på inlägg. Vänligen starta en ny fråga om du inte har ett konto ännu.