NotHereToPlayGames

Depends on your definition of "portable". Some people want to login from one computer from a browser stored on a thumb drive, carry the thumb drive to another computer, and still be logged in. That isn't easy to do. If by "portable" you are only seeking no registry entries on the host computer, no favorites stored on the computer, favorites travel with the thumb drive, as examples, then *ANY* Chrome-based browser can do that.

I don't even waste my time trying user agents these days, that's "old school" and modern designers basically only rely on UA for "mobile" version versus "real computer" version. This polyfill will fix that web site for you - // ==UserScript== // @name Inject Change Array by Copy .toSorted() Polyfill [110] // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!Array.prototype.toSorted) { Array.prototype.toSorted = function (compareFn) { return this.slice().sort(compareFn); }; }

Changing skins/wallpaper function works without change_wallpaper.zip - cannot find purpose for this file.

setdefbrowser.dll is required in XP and Win10 in order to set as default browser from within settings. In the past, the Russian Repack removed this file therefore it was not included in my builds of the past. Humming Owl also did not include this file in 13.0.2310, did not check other versions.

??? On The Same Page ???

Skin mute/unmute in XP requires 360base.dll and audiomute.dll - in the past, I removed both of these .dll's (Humming Owl also removed both of these files in 13.0.2310, did not check other versions). During this rebuild, I have isolated these files to be required if we want to be able to mute/unmute from the skin's "speaker icon". Win10 doesn't require either one of these two files in order to mute/unmute. Have not tested in Win7 (do not have access to Win8 or Vista). The mute/unmute from the skin's "speaker icon" may have been a topic of discussion many many MANY months ago. I can restore that function but I will need to isolate additional "features" of 360base.dll - it may be safe but I'm not going to "assume" it to be safe.

Note to self - Audio mute/unmute in Win10 does not require additional files for tab function or for skin function (audiomute.dll not required). Audio mute/unmute in XP works from tab without additional files but from skin requires additional files (in addition to audiomute.dll). Note 2 -- khtn.dat Note 3 -- Humming Owl also KEEPS both sets of libEGL.dll and libGLESv2.dll in 13.0.2310, did not check other versions

More noticeable with a two-digit "badge".

Technically yours is also cut off on the right and bottom edges. Both the uBO "3" and the other extension's "4" are both cut off on the right and bottom edges.

Even in the top, the right edge is "cut off".

It changes the linear flow, but there is a "trick". Any number of people can post without any flood control within any given thread and can "discuss" back and forth with ZERO delay. The trick is to post something, let the other person post their reply, then you can reply to their reply by editing your first post, then they edit their post, you can talk all day long with ZERO "flood control" because EDITS do not have a time limit. You have to refresh/reload for the edits to appear and you don't get the nice notification bubble for "Show Reply" when reading and somebody adds a post. The discussion doesn't read "top to bottom" like it normally would, but you can "discuss" without the delay. I probably wasn't supposed to make that "public", but technically it already is. Quite common actually if you've been on forums like this over the years and had to "suffer through" these sorts of spam assaults. I'm confident they will get the spam assaults back under control so all of this should only need to be short-term. Fingers crossed.

The Flood Control didn't work, by the way. This morning's spam assault of HUNDREDS of spam was done by HUNDREDS of NEW MSFN MEMBERS, unlike yesterday where the HUNDREDS of spam was all done by a "few" NEW MSFN MEMBERS. So Flood Control doesn't do anything if a NEW MEMBER posts ONE spam, then a DIFFERENT new member posts another ONE spam, then a THIRD new member posts another ONE spam. HUNDREDS of times.

Same here! We are finally on to something instead of this "circular" debate! UCyborg, seven4ever, and myself all run 64-bit XP!

@UCyborg - The .dll's will remain, regardless of what Cocodile has to say. You and I have already been over this, it has become pointless to discuss further. Again, and I shouldn't have to keep repeating myself, those that do not want the .dll's are free to remove them on THEIR system, *MY* system **NEEDS** them. And I know that I'm not the only one!

Not yet. I'm targeting to have one ready by Saturday.

If I recall, WebGL also requires them. I cannot test from work.

As I've stated, 360Chrome crashes without these dll's for me and for a few other members (first launch after each and every restart or resume from hibernate). You can delete them if you don't want them. But your debate will not convince me to remove them because again, as I have stated, 360Chrome crashes on MY COMPUTER without them. Debate for the sake of prolonged argument is not helping anyone.

lol, all I knew "today" is that I don't have "filename.txt" so I kind of had to "assume" that since you do, I must have deleted it "with no side effects". I use Directory Opus for folder/filename export.

D.Draker made that MISTAKE also. The files are not "only" for Vulkan! Anything higher than v13 build 2206 crashes on MY system when the so-called "Vulkan" files are removed. Other members have also presented issues when they are removed. They will stay. You are free to remove them on your end, of course.

nocoin.dat is not needed but references to it likely need removed from chrome.dll before we remove the .dat, I'm not that far in yet libegl.dll and libglesv2.dll ARE NEEDED for some computers but do not seem to be needed for others, these will remain in my releases I remove the "snap" module from my releases I also remove the wallpaper content I've removed audiomute in the past and tabs still mute, this could be something that XP does not need but newer OSs do, will need to test I removed filename.txt and have seen no side effects upon its removal, will verify

Yep. I still think the FLOOD CONTROL needs to remain in place (I kind of hope this is also tied to the abused "like" also). But today they just opened a "hundred" accounts and posted their "hundred" spams all one at a time. I can't help but LMFAO at all of the ANTIVIRUS / SECURITY names in today's spams.

The remaining-files list is the same as all previous versions of 360Chrome. SOME users will *NEED* the Vulcan .dll's, some users will not. They will remain INCLUDED.

My apologies in advance, but I will "likely" veto any vote on this. I'm not saying that I'm not listening to user feedback, I am. But I cannot find any browser that uses the word favorite or favourite, they all use bookmark. Firefox 115.3.1 ESR uses bookmark throughout its gui. Ungoogled Chromium 117 uses bookmark throughout its gui. Official Pale Moon 32.4.1 uses bookmark throughout its gui. Opera One 103 uses bookmark throughout its gui. Serpent 52.9.0 uses bookmark throughout its gui. Mypal and New Moon both use bookmark throughout their gui. I know that I have SEEN the word "favorite" in browsers of the past, but I cannot find one at the moment. Opera One did use the word "favourite" DURING SETUP, but once installed, it uses bookmark throughout its gui. I honestly cannot FIND a web browser that refers to bookmarks as "favorites". Perhaps it was decided long ago that "bookmark" is UNIVERSAL ??? Maybe even because of discussions exactly like this - ie, "favorite" versus "favourite". Granted, all of these installed browsers during this little test all are on the same Win10 OS and it is an "en-us" install. But on this side of the pond, favorites WITH the U is just not what we do here. We don't put a U in COLOR either. Nor in HONOR.

Along the lines of US versus GB, @Anbima's "fix" does not change the gui's context menu. Or wouldn't your context menu show "favourite" which is what started this whole "discussion"? The "accept_languages" setting in the Preferences file would effect web page content only, not the gui.

As far as that goes, users of my builds may be interested in knowing that while I will still include an XP Skin, I will actually default to a Win10 Skin. While XP x64 remains to be my workhorse OS, my two "recreational" computers now run Win10.