Web Compatibility Support • Buttons Unclickable On Webpage

The issue is the use of the ambiguous global "event" in an event handler, i.e. it's a problem on the calix website.

22:52:42.519 ReferenceError: event is not defined
Stack trace:
onSignin@https://calixcloud.calix.com/main-es201 ... :1:6997176
O/<@https://calixcloud.calix.com/main-es201 ... :1:6993263
wu@https://calixcloud.calix.com/main-es201 ... s:1:169146
i@https://calixcloud.calix.com/main-es201 ... s:1:169308
T/<@https://calixcloud.calix.com/main-es201 ... s:1:310232
r/</u</e.prototype.invokeTask@https://calixcloud.calix.com/polyfills- ... .js:1:8026
onInvokeTask@https://calixcloud.calix.com/main-es201 ... s:1:241044
r/</u</e.prototype.invokeTask@https://calixcloud.calix.com/polyfills- ... .js:1:7947
r/</c</t.prototype.runTask@https://calixcloud.calix.com/polyfills- ... .js:1:3105
r/</f</t.invokeTask@https://calixcloud.calix.com/polyfills- ... .js:1:9158
y@https://calixcloud.calix.com/polyfills- ... js:1:21845
_@https://calixcloud.calix.com/polyfills- ... js:1:22075
1 main-es2015.458d459a6be77e2e6318.js:1:6990516

The silly thing is that they are passing the event into the function ("e"), but then try to call the global alias "event" for "preventDefault()". they should have used "e" there as well.

The global "event" should not be used. See the warnings on window.event on MDN, for example.
As a temporary workaround for the site (if you need it right now) until the calix webmaster fixes it, you can tell Pale Moon to accept the window.event ambiguity by flipping the preference "dom.window.event.enabled" in about:config and restarting the browser.

---