Note: Not for "how do I...?" Questions!
Tutorials and Howtos should only relate to Pale Moon, and not to third party applications. e.g.: Don't post a Howto for configuring your firewall.
If you have a question how to do something, you should use one of the support boards, not this board. It is meant for people to document and post instructions.
There were a number of problems with newer versions built from source that I have tried to patch myself, but I must first admit that I am a complete and utter noob with no experience other than playing around in python for personal use. In particular things like the referer spoofer and as you've noticed blocking inline scripts were broken, I think I have fixed those but cannot be sure I haven't made any mistakes. I hope someone can look at my code (in legacy firefox branch) and look for anything obvious or bad style or the like.
Anyways, I was going to ask if there is anyone with more experience who might be able to assist with a proper fork so people who are unable to build from source can still use it . I have attached my patches that I have so far to be applied to version 1.2.0, with the only bug I know of being that blocking web workers doesn't work in Pale Moon (it works fine in Firefox 52, but I think it can't be made to work until support for child-src in Content Security Policy is added for those interested). Test at your own risk!
- (5.72 KiB) Downloaded 41 times
- Pale Moon guru
- Posts: 20643
- Joined: Sun, 28 Aug 2011, 17:27
- Location: 58.5°N 15.5°E
tnx for your work!
Ketmar I don't think you were far wrong, you were looking in the right places at least. Thanks for your patches so far, I wouldn't have been inspired to look without your first patch
ketmar wrote:no, it doesn't.
Are you going to be punch or judy...?..lol.
Pale moon 27.7.1
no, it doesn't.
it`s not perfect, had an error in Console, yes...
Code: Select all
Метка времени: 04.03.2018 15:43:18
Ошибка: uncaught exception: Error opening input stream (invalid filename?): chrome://umatrix/content/js/contentscript-end.js
and this is not very good, but works; blocking scripts and xhr, all options shown correctly - which is exactly what I need.
To fix this error would be good, of course. But I have not yet noticed any consequences.
line 306: // lss(this.contentBaseURI + 'contentscript-end.js', sandbox);
Who is online
Users browsing this forum: No registered users and 1 guest