Pale Moon forum

Posted: **2022-06-20, 03:29**

Using Pale Moon version 31.1.0 64 bit under Windows 7 64 bit.

This latest release of Pale Moon has fixed the issue as outlined here. Thank you!

But another website mitre10 is not working properly.

On selection of "DEPARTMENTS" text near the top left side of the main web page brings up a drop down menu of departments for further selection. But on selection of any of the departments, the drop down menu closes and nothing further happens!?

This is the Developer Tools Web Console output for the website:

Code: Select all

None of the “sha512” hashes in the integrity attribute match the content of the subresource.  
www.mitre10.co.nz
scout-to-render: timer started
bvapi.js:1
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "tk-myriad-pro-n7" style:normal weight:bold stretch:normal src index:0) source: https://use.typekit.net/af/1b1b1e/00000000000000000001709e/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=n7&v=3  
www.mitre10.co.nz:1:634
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "tk-myriad-pro-n6" style:normal weight:600 stretch:normal src index:0) source: https://use.typekit.net/af/80c5d0/00000000000000000001709c/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=n6&v=3  
www.mitre10.co.nz:1:2503
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "tk-myriad-pro-i6" style:italic weight:600 stretch:normal src index:0) source: https://use.typekit.net/af/d50a1b/00000000000000000001709d/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=i6&v=3  
www.mitre10.co.nz:1:3126
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "myriad-pro" style:normal weight:600 stretch:normal src index:0) source: https://use.typekit.net/af/80c5d0/00000000000000000001709c/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=n6&v=3  
uha4gat.css:45:12
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "myriad-pro" style:normal weight:bold stretch:normal src index:0) source: https://use.typekit.net/af/1b1b1e/00000000000000000001709e/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=n7&v=3  
uha4gat.css:27:12
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "myriad-pro" style:italic weight:600 stretch:normal src index:0) source: https://use.typekit.net/af/d50a1b/00000000000000000001709d/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=i6&v=3  
uha4gat.css:51:12
downloadable font: OS/2: Adjusting head.macStyle (regular) to match fsSelection (font-family: "tk-myriad-pro-i4" style:italic weight:normal stretch:normal src index:0) source: https://use.typekit.net/af/d32e26/00000000000000000001709b/27/l?primer=7fa3915bdafdf03041871920a205bef951d72bf64dd4c4460fb992e3ecc3a862&fvd=i4&v=3  
www.mitre10.co.nz:1:1257
ReferenceError: event is not defined[Learn More]  
scripts.js:33:24688
	megaMenuNavigation/< https://www.mitre10.co.nz/_ui/responsive/theme-blue/js/scripts.js:33:24688
	dispatch https://www.mitre10.co.nz/_ui/responsive/theme-blue/js/scripts.js:2:20088
	add/q.handle https://www.mitre10.co.nz/_ui/responsive/theme-blue/js/scripts.js:2:16888

Javascript issue again?

Thank you.

Posted: **2022-06-20, 05:20**

ReferenceError: event is not defined

The site is using a deprecated property (Window.event) which Pale Moon doesn't support.

Posted: **2022-06-23, 03:48**

Noted, thanks.

So, ideally the website should be "re-coded" in order to allow Pale Moon (and maybe some other browsers as well) to fully navigate that site(?)

In the meantime, it is back to using an alternative browser if wanting to browse that website properly it seems.

Posted: **2022-06-23, 08:12**

meeshu wrote: ↑
2022-06-23, 03:48
So, ideally the website should be "re-coded" in order to allow Pale Moon (and maybe some other browsers as well) to fully navigate that site(?)

Yes. But it's not just for Pale Moon's benefit. Ambiguous global events were only added for MSIE compatibility to begin with (it's a quirk) to mainstream browsers. Pretty late in the game too, actually. It still works in them because as usual Chromium is reluctant to a fault to change or god forbid remove anything that has been implemented (unless it furthers the agenda to replace it with something incompatible their devs came up with as a replacement, of course).

Fixing this doesn't require recoding anything, actually. It just requires a small change to the affected event handler(s) and is literally a no-risk, 1 minute job.

Posted: **2022-11-27, 09:56**

Moonchild wrote: ↑
2022-06-23, 08:12

meeshu wrote: ↑
2022-06-23, 03:48
So, ideally the website should be "re-coded" in order to allow Pale Moon (and maybe some other browsers as well) to fully navigate that site(?)
. . .Fixing this doesn't require recoding anything, actually. It just requires a small change to the affected event handler(s) and is literally a no-risk, 1 minute job.

I did note this sometime ago, but I assumed something would be done to later releases of Pale Moon to enable browsing 'problem' websites such as www.mitre10.co.nz.

But as of PM release 31.4.0 64 bit for Windows I still can't browse the problem websites properly.

So how does one implement this "1 minute" job exactly in order to enable proper browsing of these websites?

Posted: **2022-11-27, 12:44**

No, it won't magically change. And we aren't planning to implement something declared deprecated, an MSIE quirk actually, that websites shouldn't be using.
Mainstream is just too afraid to actually switch it off in their browsers.

Posted: **2022-11-27, 18:06**

meeshu wrote: ↑
2022-11-27, 09:56
So how does one implement this "1 minute" job exactly in order to enable proper browsing of these websites?

Ususally the wrong event handlers are written like so:

Code: Select all

function listener() {
  event.preventDefault();
  /* rest of code follows */
}

The one-minute no-risk change is writing them like this:

Code: Select all

function listener(event) {
  event.preventDefault();
  /* rest of code follows */
}

Posted: **2022-11-28, 01:30**

Moonchild wrote: ↑
2022-11-27, 12:44
No, it won't magically change. And we aren't planning to implement something declared deprecated, an MSIE quirk actually, that websites shouldn't be using.
Mainstream is just too afraid to actually switch it off in their browsers.

Noted, thanks.

That is an unfortunate stance on PM's part. That means PM users are effectively blocked from visiting websites that have (old standard?) script that PM can't handle properly.

It is not the fault of users that some websites use (old?) script, and users shouldn't be inconvenienced because of PM's shortcomings.

This ultimately means that users will have to resort to use other browsers instead of PM. I'm mainly using Vivaldi which works quite well with 95% + of websites. In rare cases where Vivaldi doesn't work properly with some websites, I resort to using Firefox.

I would have liked to have supported PM more by using it, but due to its present limitations in being unable to browse a few websites due to (script handling?) issues, I no longer use PM. And I've now regrettably uninstalled PM indefinitely.

Posted: **2022-11-28, 01:42**

vannilla wrote: ↑
2022-11-27, 18:06

meeshu wrote: ↑
2022-11-27, 09:56
So how does one implement this "1 minute" job exactly in order to enable proper browsing of these websites?
Ususally the wrong event handlers are written like so:
Code: Select all
function listener() {
  event.preventDefault();
  /* rest of code follows */
}
The one-minute no-risk change is writing them like this:
Code: Select all
function listener(event) {
  event.preventDefault();
  /* rest of code follows */
}

Thanks for this detailed reply!

But frankly I have no idea regarding scripts? If it is an "easy" fix to enable browsing those websites with old(?) script, then why on earth can't PM incorporate this fix?

How exactly does one incorporate this "fix"?

From previous response by Moonchild, it is my understanding that PM is not really interested in incorporating this easy or quick fix as they say that (new) websites shouldn't be using (old?) script to begin with. Then why inconvenience/punish PM users by users not being able to browse those old scripted websites? It is not the fault of PM users that some websites use old script still.

Posted: **2022-11-28, 03:08**

Official standard https://dom.spec.whatwg.org/#ref-for-dom-window-event
Marked as legacy

Web developers are strongly encouraged to instead rely on the Event object passed to event listeners, as that will result in more portable code. This attribute is not available in workers or worklets, and is inaccurate for events dispatched in shadow trees.

It is also usually more error prone that the parameter that is always passed to the function related to that event that will never be incorrect.

I would say it still boils to down to that a browser should follow a standard for the best interoperability, one of the problems with something like Chrome is exactly that it doesn't follow standards (or implements drafts that are not for production (i.e. actual use)) creating it's own functionality and then web developers jump on that and implement it anyway generating errors on every other one, like Pale Moon.
So in that case Pale Moon is also ""inconvenience/punish PM users""?
One of the reasons some websites use old script still is exactly that it is still allowed and most browsers are just too afraid to actually switch it off to inconvenience you since you will blame the browser instead of the web developer of that website. (this global event functionality is deprecated for a long time counted in years, so the web site owner could have updated it long ago)

Posted: **2022-11-28, 08:18**

meeshu wrote: ↑
2022-11-28, 01:42
How exactly does one incorporate this "fix"?

You get in touch with the website developers, show them that to make their site work with Pale Moon they just need to add an argument called "event" to their handlers in a safe and quick way, and wait for their reply.

Posted: **2022-11-28, 09:19**

meeshu wrote: ↑
2022-11-28, 01:30
That means PM users are effectively blocked from visiting websites that have (old standard?) script that PM can't handle properly.

No, as it was never part of the standard to begin with. It has always been an engine-specific quirk.

Posted: **2022-11-29, 22:30**

Moonchild wrote: ↑
2022-11-28, 09:19

meeshu wrote: ↑
2022-11-28, 01:30
That means PM users are effectively blocked from visiting websites that have (old standard?) script that PM can't handle properly.
No, as it was never part of the standard to begin with. It has always been an engine-specific quirk.

I hope this sane view continues to be taken in development. It's for the better. Mentality like firefox-chrome dev mentality is dangerous. Internet Explorer is dead and gone as a relic of a dangerous internet where it was exploited to the death, and if mainstream browsers still accept that because they want to cater to specific websites and users that are using MSHTML quirks in their code, it means their code and architectural decisions in general are likely very dirty (it brings me even more concern this could be so easily removed from their code but they stubbornly refuse to) and may bring security issues to their users.

Pale Moon forum

www.mitre10.co.nz Website Selection Not Working

www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working

Re: www.mitre10.co.nz Website Selection Not Working