NotHereToPlayGames

My no-print issue is Win10 and seems to be ONLY in Win10. I can print from 360Chrome in Win10 with build 2044.

emojis working for me

The preview feature would slow my computer to a crawl to the point of forcing a hard-shutdown without the ability to close anything that was open at the time. My Win10 won't print even with the preview re-enabled.

Nobody has pointed it out before but printing from 360Chrome build 2036 (and perhaps all previous builds) does work in XP but fails in Win10. May not be true for "all" systems. This has been resolved in the upcoming build 2044.

If anyone wants the "error codes" page restored, please provide a screencap of when any errors were encountered with the errorpage.zip that another member submitted. All I am seeing is a sh!tlo@d of www. so. com, www. dd. browser. 360. cn, and browser. 360. cn chinese telemetry crap and ZERO "value-add". But maybe I just don't know "how" to FIND any of the errors that some want an "error code page" for ???

The first post in that thread will have a download link once I get it all put together. I was originally targeting this weekend but it may end up being next weekend instead. As far as "primary differences", they're all minor and there has been no "significant" advancements with 360Chrome in over two years. It's v86. Nothing more. Still the best there is for XP but users of newer OSs have more "modern" alternatives to choose from. That said, I actually prefer v86 over everything "newer" and it does EVERYTHING that I actually throw at it. It's not going to do "everything" - but nor does its XP competitors.

From what I am finding, uBOs "badge" is cut off on the bottom and right on even the 13.0 look. Also cut off on Ungoogled Chromium latest-and-greatest on Win10. For now, I'm keeping the XP skin "as-is", the badge cut-off issue is being cut off in over a dozen different skins tried from the 360Chrome's skin page and even Official Ungoogled Chromium does this cut off.

Original build 2036 options.zip is identical to original build 2044 options.zip so our already-modified version from build 2036 can be carried over to build 2044 as-is.

The first-launch ONLY after each and every reboot or resume from hibernate "can't" be a browser issue. *EVERY* browser that I use on *ANY* of the seven computers *ALL* do this first-launch delay. I don't really have a good debug method for this issue, but none of the seven computers have the same video cards. Serpent 52, NM27, NM28, 360Chrome, Ungoogled Chromium - they *ALL* have this first-launch delay, each and every one of them. edit - it would be nice to know why **ALL** browsers on **ALL** of my computers have this first-launch only delay, but since **ALL** browsers do this on my computers, it's perhaps "off-topic" for this thread. edit2 - perhaps I should also point out that **ALL** of my browsers are *portable*, none of my computers are set up with a "default" web browser and none of them use "installed" browser versions.

I'm aware that it's not "normal". But even Ungoogled Chromium does that delay on *ALL* of my *SEVEN* computers.

<disregard, still testing>

The en-us.pak file can be copied from build 2036 as all indexes remain the same. It can not be copied from build 1030 as over 300 translation files are indexed differently than from build 1030.

If you truly want to edit the "Add to favorite" in this context menu, this is the 5386 file inside en-us.pak. My release will continue to use "Add to bookmarks..." (with three dots versus one ellipsis) as it has in the past.

Because I will continue to use the "loader" .exe/.ini and this is obtained from the Russian Repack set of files. Agreed. I do not use the snapshot tool and have it removed in all of my releases.

Yep. I prefer to avoid cmd files for this and use the Official Pale Moon Portable loader and file structure and replace the "bin" filder with the extracted fork files.

Works in 360Chrome v13.5.

In that case, use a WinPenPack or PortableApps Chrome and *replace* the bin folder with the extracted Ungoogled Chromium v109. I can compile more detailed "how-to" if needed.

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