NoScript makes Pale Moon crash opening MP4 pages

[Mæstro]

As this has happened to me, and I notice that there is an open issue on the matter, I would like to offer some more information on this. While it has been mentioned elsewhere, I still hope this informs. Pale Moon v32·2 with NoScript installed will crash, even if scripts are disabled through NoScript on the relevant page, on opening any address ending in .mp4 within the browser. (This does not occur when downloading .mp4 files, such as on an Invidious instance.)

I am pleased to hear that the root of this problem child’s bad behaviour has been discovered; I know it was unclear only a few months ago. I am surprised and delighted to learn that the Pale Moon team is addressing it.

[moonbat]

NoScript has always been problematic, so no surprises there.

[vannilla]

NoScript has always been problematic, so no surprises there.

From what I could gather it would happen even without NoScript given the right conditions, so it seems to be a more general problem.

[dbsoft]

From what I could gather it would happen even without NoScript given the right conditions, so it seems to be a more general problem.

The crash I fixed would only occur when some extension was blocking script execution of browser provided scripts (in the case of MP4 files the video player script). This really should not be allowed, so it is possible that other extensions might do that besides NoScript, but really they shouldn't. I don't think this crash would ever occur with no extensions installed.

[Moonchild]

it is possible that other extensions might do that besides NoScript, but really they shouldn't.

With great power (XUL browser extensions) comes great responsibility (please know what you are doing when interfacing with the browser guts).

I don't think this crash would ever occur with no extensions installed.

It would not. This is entirely NoScript throwing a wrench in the gears of the browser itself.

P.S.: why did you create a new thread for the same thing you were already aware of?

[Mæstro]

P.S.: why did you create a new thread for the same thing you were already aware of?

My vague memory of board etiquette guides from the noughts tells me that it is better to create a new thread on the same topic than bump one weeks old.
If the preference is different here, I am happy to learn.

[moonbat]

My vague memory of board etiquette guides from the noughts tells me that it is better to create a new thread on the same topic than bump one weeks old.

You're right when it comes to regular banter, but when troubleshooting it's best to not continue existing threads unless the problem is totally different or for a different site. We often end up with multiple threads about say Github or Youtube not working despite the same problems being already discussed. Else when searching the boards, one gets multiple results for the same topic.

[Moonchild]

when troubleshooting it's best to not continue existing threads unless the problem is totally different or for a different site.

I'm sure you meant to say "It's best to continue existing threads"

[moonbat]

Oh right