However, given the above, I'll leave it up to you to decide whether unrecognized entries should still be manually added or not. I have no guess as to why that might not be there, outside of the possibilities I've offered above. But in this case (knowing the browsers were compiled with them disabled by default.Īnd in AF I'm just bewildered by, as that also should have been a basic and universal component in the Mozilla codebase and forms the entirety of what is essentially foxPEP's built-in ad blocker. , which controls the state of WebRTC (a security hazard), and should have been a known component of the Mozilla codebase for a similarly long time, unless the browsers were simply compiled with them disabled by default. , which is a basic preference and has been around in the Mozilla codebase for a long time and should not have been unrecognized, again unless the feature was for some reason removed outright. However, there are still sometimes some outliers that continue to confuse me (not necessarily unborn out of my own ignorance) why the browser won't acknowledge, such as:ī, which shouldn't typically depend on version or environment, unless it was either implemented in a newer version than what AF / SW are derived from (unlikely), or were removed outright. I believe fingerprinting and cryptomining protection are features (again) native to Quantum-derived (FF57+) codebases. ![]() is a feature inherited from Servo (R.I.P.), and is only relevant for Quantum-derived (FF57+) codebases. is a vanilla Pale Moon-only preference, and is only included to fully turn hardware acceleration on there (it won't work with just force-enabled). Later down the line, I realized that the browser does not make certain changes as according to the patch most of the time because A), it is compiled without support for that preference due to a version misalignment or operating environment dependency, or B), the given altered preference has already been set that way as the browser default.Īpparently, gl.multithreaded is an OS X-exclusive preference (I have yet to personally confirm this). He chose to try fighting an uphill battle with The UOC Patch and came up with the Enforcer idea to counteract this 'stubborn preference' issue, while since I was committed to the all-in-one installation model, there was nothing I could do, so I had to end up trusting the browser that it was overriding the patch for a reason. Yes, looking4awayout and I encountered this problem in PowerUOC's (foxPEP's) infancy. In that case, that is a library / compilation issue. I believe SpiderWeb does not support hardware acceleration due to an endianness anomaly, but I'm not totally 100% on that. If you are going to make a custom rendition for the aforementioned browsers, then it serves no place there. The backend "cg" stands for Core Graphics, a native rendering library exclusive to OS X (which is faster than Cairo, but slower than Skia). And as for cg, it sees it as an unknown and instead falls back onto Cairo. ![]() ![]() I hope that some information could be useful to the future of the Although neither Arctic Fox nor SpiderWeb are officially supported browsers for foxPEP (for the reasons you discovered), I applaud your diligence and experimentation to attempt a working state in addition to compiling this information.Īrctic Fox does not launch with 'Skia' clarified as a content / canvas backend because the browser has been compiled without any support for Skia. There is any problem with manually inset any if the aren't present in the original? So far the performance and fluidity on the SpiderWeb exceed my expectations. Below are the specific lines there wasn't present in each browser.ĭ, false Since I aways copy the prefs.js to the destination folder and both of the browsers had some issues I tested every single entry on the about:config to isolate the problems but some lines wasn't present until I manually inserted on the prefs.js file. #!!! ABORT: Could not initialize mScreenReferenceDrawTarget: file /home/matt/Development/Arctic-Fox-27.10.1/gfx/thebes/gfxPlatform.cpp, line 521 In Arcticfox if I use ("", "direct2d1.1,skia,cg,cairo") the program crashes without starting (see crash below) but if I use on this specific preference the value "cg,cairo" works fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |