NotHereToPlayGames
Content Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
Agreed. Plus, "se" and "ee" are two different branches. 360Chrome has basically had three different v86 engines - 86.0.4195.1 86.0.4240.112 86.0.4240.198 As far as a true scientific quantitative approach goes - The .1 engines were the FASTEST. The .112 engines saw a very slight performance degradation. The .198 engines (everything newer than v13.0 build 2206 and all of the v13.5 builds) saw another very slight performance degradation.
-
Same here!
-
It's only enabled because you were using in an unintended fashion (that I do not recall you admitting to prior to today). So you have to blame yourself for that. You chose to use by your own rules, so no, of course it didn't work as it was intended. The topic of your WebGL being enabled or disabled can hereby be considered CLOSED. Further discussions only confuse new visitors. Bottom line - you used it in your own way, so you didn't get the results you were supposed to get because of using it in your own way. Q.E.D.
-
If it's any consolation - A year or two ago when I started these public-share rebuilds, I opted to disable WebGL based on "security vulnerabilities" associated with WebGL. Most of those "security" reports with WebGL are dated circa 2011. Most of the "vulnerabilities" were later addressed by way of "same-origin policy" restrictions coded into the web browser. How "insecure" is a web browser in 2023 because of WebGL coupled with same-origin policy restrictions that did not exist in 2011 when these "security vulnerabilities" were first raised? Should I be "paranoid" about WebGL exposing OpenGL to JavaScript when I only allow specific whitelisted javascript? I have currently opted to enable WebGL and maybe, just MAYBE, I was a bit too "paranoid" to disable it in the first place.
-
If you do not use the loader.exe, then the loader.ini does NOTHING. If you are trying to DISABLE WebGL, then you either must use the loader.exe or the --disable-webgl startup command. You are not using EITHER and then you wonder why WebGL is still enabled ??? ??? ???
-
Before I can assist any further, I need all of the following in ONE screencap - 1) Task Manager showing "360Loader.exe" 2) File Manager window showing the 360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-xp-skin contents of "360Loader.exe" and "360Loader.ini" 3) Notepad showing "--disable-webgl" 4) ONE tab open and ONE tab ONLY showing top section of "chrome://gpu"
-
The irony there is that I once called up Chase and CLOSED my account with them all on account of Chase.com no longer working in NM28. That would have been about four years ago or so. Little did I know at the time just where the "web" was headed and just how many "no longer working" sites I would encounter in the following years. With Chase, NM28 no longer working was my last straw because that was the THIRD browser in just two short years that "no longer worked" with Chase.
-
That's because a Win10 "Jump List" is like a programs "Recent File" list. Clearing those lists do not send them to the Recycle Bin because they are all stored in the Windows Registry. A deleted registry key is not sent to the Recycle Bin just like clearing a program's recent file list is not sent to the Recycle Bin.
-
I believe Win10 calls those "Jump Lists" and they are managed by Win10's "mui / jump lists" registry keys. By deleting the white scare icon, I suspect you have also deleted the Win10 registry keys that "track" the mui / jump lists. At any rate, that's managed by Win10.
-
Ah, thanks. Forgot about this. I'm assuming Win10?
-
My Browser Builds (Part 4)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
lol Though not sure I'd really brag about three tiny months. Firefox v94 was released on November 2, 2021. Chrome v98 was released on February 1, 2022. I suppose if we want to play that game, shouldn't we dig deep into any other have/have-nots between the two versions? And shouldn't we then call this a "Mozillaism" since everything else is always called a "Googleism"? -
My Browser Builds (Part 4)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
A reminder-link for those that may be interested -- https://msfn.org/board/topic/183484-polyfill-whats-all-this-then/?do=findComment&comment=1216125 Thanks again, @UCyborg -
My Browser Builds (Part 4)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
Would you happen to have a breakdown of what polyfills are resolved via your palefill that are newer than Chrome v86? -
It has also been reported on some forums that ECC certs in XP have been FALSIFIED as "secure" by some XP web browsers.
-
If you are talking about these, I would advise against checkmarking these two options. You essentially INTRODUCE a man-in-the-middle to "check" if you have a man-in-the-middle.
-
In my opinion, one should NEVER "manually update" certificates. While other MSFN Members would equally swear the exact opposite as their opinion. I've NEVER updated my "certificates" and I have no problem whatsoever with the web site in question. Chrome/Chromium uses XP's "certificate store". I let XP manage that "certificate store". "Opinions are like butts. Everybody has one, not everybody wants to hear them."
-
That could be your problem. I have never in my entire life "updated" system certificates. How they update "behind the scenes" is unknown, but I have never in my entire life "manually updated" system certificates.
-
Also, unless I'm mistaken, you run XP x86 SP2. XP x86 SP2 was released in August 2004!
-
Did you try in an INCOGNITO WINDOW? And without setting any extensions to be allowed during Incognito Mode.
-
Yes. Chrome/Chromium support for CSS 3D pre-dates v86 by over a DECADE. Chromium v86 was released 06/10/2020 (day/month/year, I sure as Hades wish there was a universally-accepted date format!).
-
You have your files criss-crossed and you confuse the flow of this thread until that criss-cross is resolved on your end.
-
As I suspected. You have WebGL enabled! So you seem to NOT be using the loader.ini CORRECTLY because you screencap'd that your loader.ini has WebGL "disabled".
-
Open chrome://gpu and post this section as a screencap -
-
Your geolocation is perhaps being served html5 instead of webgl. Open chrome://gpu and post this section as a screencap - (crap, can't paste an image... have to delete some profile pics...)