Jump to content

feodor2

Member
  • Posts

    181
  • Joined

  • Last visited

  • Days Won

    2
  • Donations

    0.00 USD 
  • Country

    Ukraine

Posts posted by feodor2

  1. So here I give more information.

    I did same path as firefox did, and put 74 version because this is where I stopped of clean of xul, yes not all xull stuff has been removed, this essential about interfere new functions, remember wrong icons on permissions.

    Also you may want to learn yourself what and when removed between 68-74. For everybody else this is unnecessary junk information waste to discuss.

  2. @AstroSkipper may be you missed something, do it again carefully and do not forget about purgecaches

    If any other fellow use custumbuttons too please confirm.

    I say again that other your written page is irrelevant, also I thing this is unnecessary information here for others too, so may considered as spam or flame whatever.

  3. This hubbub is all irrelevant.

    Nevertheless one place checks MOZ_APP_VERSION

    So you can fix this

    diff --git a/chrome/custombuttons/content/SelfHelper/SelfHelper.jsm b/chrome/custombuttons/content/SelfHelper/SelfHelper.jsm
    index 8e009ac..42807e7 100644
    --- a/chrome/custombuttons/content/SelfHelper/SelfHelper.jsm
    +++ b/chrome/custombuttons/content/SelfHelper/SelfHelper.jsm
    @@ -52,7 +52,7 @@ var AC, SelfHelper = {
     		this.platform = ["win", "linux", "macosx"]
     			.includes(platform) ? platform : "linux";
     
    -		this.version = parseInt(AppConstants.MOZ_APP_VERSION);
    +		this.version = 74;
     		if (this.version >= 95) {
     			var pref = "extensions.custombuttons.prefersColorSchemeOverride";
     			var pb = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch);

    I shall think out what to do with the version discord.

  4. Custumbuttons rely on the platformVersion, if the value was left 68 it thinks that the xul is preset therefore fails, thats why I lift platformVersion to 74.

    But it rely not only the version, but other things which is silly I thing,  I am to investigate further.

  5. On 12/18/2024 at 9:16 PM, dapgo said:

    are you using Multi-Account Containers? IMO isolate cookies is musttohave

    Though v8.0.1 is compatible with FF67, it produces an error during installing "...appears to be corrupt"

    set extensions.allowPrivateBrowsingByDefault to false and it will install

  6. 10 hours ago, D.Draker said:

    One example, CatsXP supported XP up to Chrome 87 (or so), Chrome 87 is far more advanced than FF 68, yet CatsXP had a fully working sandbox under XP, how so?

    Okey this is not CatsXP, not a chrome at all.

    What do you mean "fully working", as I know mozilla has push to the firefox the very same cromish "sandbox" (flash and drm for xp) I already told that consider it useless.

    From the beginning I did only 32bit versions and not bothered with its "sandbox", but if you want I may enable it for х64 and shall see, no point in saving resources there.

  7. You keep gnawing this why, what do you want actually?

    Flash has gone, DRM is not possible.

    And yes firefox 68 has many win10 specifics, while that mostly was removed from mypal.

    3 hours ago, D.Draker said:

    And the dude here wrote you globally disabled the sandbox. Why?

    The same reason he told

  8. security.sandbox.content.level is not a sandbox actually. Also I can say for 115 firefox also not really do sandbox with this.

    Yes do not get to the delusion with this setting, If you want true sandbox use proper software.

  9. Seems nobody noticed before

    19 hours ago, AstroSkipper said:

    starting the browser with the about:addons page, it takes nearly 8 seconds after DOM is loaded

    Sure multiprocess starts slower, and on yours old pentioum 4 this is it noticeable may be, so that why I keep single process. Remember not to rely on xul things, I begin to remove them, xul addons page has gone already.

  10. On 2/1/2025 at 1:25 PM, AstroSkipper said:

    the user would also have to familiarise themselves with the special JavaScript language and its syntax provided by the Custom Buttons extension

    Not necessary - here the custumbutton already published by you

    /*Initialization Code*/ var prefName = "security.csp.enable"; var enabledImage = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAO1JREFUOE9jZPgPhFQFIAOpCalqGNi31HQdfQz8R6Gb4drVwLGNwGlQGWQxWAC5Iqnjg7LnwtSD/G0GFYSFpzSQzwTEfWjiIANhPgCx7aGG6COpg6bD/wxuWLzagWYgcgSCDDSG6pmHzcBuHGEH83IEmjxI3A4qpoDNQJBrcMFcpDCDqYFZFACV248chiBJayzGgcLrA5I4SF0tTCOQNsCiByxkBLXlJVTBOSCdA8RiaGEIMnADkoGmuAwEGSqO5C2QxlYgPg8VY4bSoCQCgqFIasPQDMViB2ZI/iFKFUQfCUqJy/WjBhIXTnhUAQCxF7FzNVSQlgAAAABJRU5ErkJggg=="; var disabledImage = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAOlJREFUOE9j/M/AAERUBCADqYlBzhvpBv6jMAjgYagGiW04ToMajCwGYoPC3BVJHR+UPRemHqTADCoIiyBpIJ8JiPvQxEEGwnwAYttDDdFHUgd2IUjSDYtXO9AMRE4RID3GUD3zsBnYjSPsYF6OQJMHidtBxRSwGQhyDa40mYsUZjA1MIsCoHL7kcMQJGmNxUBQeH1AEgepq4VpBNIGWPSAw9AIastLqIJzQDoHiMXQwhBk4AYkA01xGQgyVBzJWyCNrUB8HirGDKVBSQSkNhRJbRiaoUTl5T94whc93IkykJQCZNRAygtbAOb2sXODGkDmAAAAAElFTkSuQmCC"; this.onclick = function (aE) { if (aE.button === 0) { Services.prefs.setBoolPref(prefName, !Services.prefs.getBoolPref(prefName)); setSelfImage(); } }; function setSelfImage() { if (Services.prefs.getBoolPref(prefName)) self.image = enabledImage; else self.image = disabledImage; } setSelfImage();

    replace "security.csp.enable" with the desired thing

     

    On 2/1/2025 at 1:25 PM, AstroSkipper said:

    I have neither ruled out nor promised a release of the PMT - Process Mode Toggler custom button even though I generally create custom buttons for personal use.

    Why to tease then?

×
×
  • Create New...