Fix TypeErrors related to uBlock Origin
Users who use uBlock Origin and try to log in to RefWorks are unable to do so. (Tested in Firefox and Chrome.) The devtools console reports a TypeError
regarding some tracking structures found unexpectedly undefined
at login time. There are very simple ways to handle such cases gracefully in the code, and should be a simple fix for any modern website.
Right now, there is a help document at https://knowledge.exlibrisgroup.com/RefWorks/Knowledge_Articles/RefWorks_Browser_Best_Practices, to which a support representative will send users, upon request. This document explains that RefWorks does not play well with the likes of uBlock Origin, and requests that users disable these while using ProQuest and Ex Libris products.
On principle, to fix a broken product is better than to maintain a supporting document and support staff for the sole purpose of explaining away the product's brokenness. The site ought at least to present an error message, rather than silently break until the user checks the debug logs themselves. If monetization is the reason that RefWorks depends so heavily on the offending tracker code, I would much prefer the option to pay a fee, rather than disable my anti-tracking plugins.
As a web developer myself, I understand the benefit of some analytics. But a good product does not depend so fully on these analytics that the product breaks entirely when these analytics are disabled. Considering that I proactively contacted RefWorks Support regarding this issue, analytics would not have been more useful than that real communication. Anti-tracking plugins give users control over who follows their online browsing.
RefWorks is so far the only website I've found that breaks at the presence of uBlock Origin and the like since several months ago when I began using ad blockers. RefWorks may not be unique with this issue, but this behavior certainly is not the norm.