NotHereToPlayGames

@mixit We can disregard the file 13570 differences that resulted in our resources.pak (ungoogled) files being different sizes. My local file had some cosmetic changes to the extensions page (personal preference) and to the settings/content page (to correct anomolies on laptops with 768px max vertical resolution) and all of these changes were within file 13570. Apologies for any confusion. edit: discussion concluded, removed images from profile attachments

for reference (I seek to REMOVE these from the context menu completely - these "features" are intentionally broken in my default ungoogled releases). edit: copied images to Dropbox host instead of using profile attachments

for reference (special thanks to @rereser). edit: copied images to Dropbox host instead of linking directly to rereser's profile attachments

Link to new thread -- https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/ (have not provided download links at the time of this posting, will be doing so shortly). Please consider this my last post in this thread. I kindly request that our new thread be dedicated to v13.5 build 2022. References to anything outside of v13.5 build 2022 should be considered as "off-topic". (ie, members wanting a v11 thread, for example, should kindly start their own thread.) Citing any web page that "does not work" and also does not work in Official Chrome v86 should also be considered as "off-topic". Please do not view this as "micro-managing", but rather as a CLEAN NEW START - I invite any-and-all to join me in our new thread.

for reference - https://chromium.googlesource.com/chromium/src/+/refs/tags/86.0.4240.198/chrome/browser/renderer_context_menu/render_view_context_menu.cc (special thanks to @mixit).

<reserved>

<reserved>

<reserved>

Instructions to restore "Translate to English" context menu feature. Note that this works for both the "ungoogled" and the "regular" versions. Obtain HxD Hex Editor from here - https://mh-nexus.de/en/downloads.php?product=HxD20 Copy 360Chrome's chrome.dll from the base "ungoogled" version to a temporary folder and open in HxD. Perform a REPLACE (Ctrl+R) and enter ttps://translate........... (there are 11 dots) in the "Search for:" field and enter ttps://translate.googleapis in the "Replace with:" field. Note the h in https is intentionally skipped so that the instructions do not get mangled by forum reply box or by web browser viewing. Make sure that "All" is selected for "Search direction" and that "Text encoding" is set to "(Editor encoding)". Also make sure that "Case sensitive" is not selected. Click the "Replace all" button. TWO occurrences should be replaced. Save chrome.dll and replace in 360Chrome's folder while 360Chrome is not running.

Instructions to convert "ungoogled" to "regular". Note that this is not required to restore the "Translate to English" context menu feature (next post). Obtain and extract chrome-pak-customizer. https://github.com/myfreeer/chrome-pak-customizer/releases/download/2.0/chrome-pak.7z Copy 360Chrome's resources.pak file to a temporary folder. The easiest way to use chrome-pak-customizer is to have two File Manager windows open and use drag-and-drop. Drag-and-drop the resources.pak file and drop it onto unpack.bat. This will create a folder named resources_unpacked. Inside the resources_unpacked folder, open 155.json using Notepad++ or similar (I do not suggest Window's regular Notepad because carriage-returns/new-line-characters will not drop to a new line). I personally prefer a version called 5.8.6 Minimalist but any Notepad++ or similar will do. Edit the two 9oo9le entries to google to restore Chrome Web Store functionality but note that this enables a persistent Google cookie that will never delete and is shared across all browser sessions. Save the edited 155.json. After editing and saving 155.json, locate the pak_index.ini file from inside the same resources_unpacked folder and drag-and-drop onto pack.bat. This will create a file inside resources_unpacked folder called pak_index_packed.pak. RENAME pak_index_packed.pak to resources.pak and REPLACE 360Chrome's resources.pak (while 360Chrome is not running).

Download link (base version is the "ungoogled" version, instructions provided to convert to "regular" version in following posts) - https://www.dropbox.com/s/fuxzyehctard5aa/360ChromePortable_13.5.2022_rebuild_2_ungoogled_MSFN.zip?dl=1 Last updated: Fri, Nov 25, 2022 @ 8:05AM EST Updated links - https://www.dropbox.com/s/ezipnov6wqgiirr/360ChromePortable_13.5.2022_rebuild_3_ungoogled_MSFN.zip?dl=1 https://www.dropbox.com/s/w4n9q2kuz6gtjrn/360ChromePortable_13.5.2022_rebuild_3_regular_MSFN.zip?dl=1 Last updated: Sat, Dec 3, 2022 @ 8:00PM EST Reminder - this project does NOT "backport". If a web site does not natively run in Chrome/Chromium v86, it will not run in 360Chrome v13.5. This project does bring "modern" capabilities up-to-and-including Chrome/Chromium v86 [October 2020] to Windows XP/Vista. Reminder that Chrome/Chromium dropped XP/Vista support with v49 [March 2016]. Some useful links: Last version of ChromiumPortable v49 as a .paf that works in XP/Vista - https://sourceforge.net/projects/crportable/files/ChromiumPortable_49.0.2623.23.paf.exe/download Official Ungoogled Portable v86 (will not work in XP/Vista but if a web site does not work with this in Win7 or Win10 [can not test in Win11], then it will not work in 360Chrome v13.5) - https://github.com/portapps/ungoogled-chromium-portable/releases/download/86.0.4240.193-7/ungoogled-chromium-portable-win64-86.0.4240.193-7.7z

The excessive use of words like "evil", "crap", "god", et cetera is extremely nagative and toxic to the environment, in my humble opinion. I intentionally "404'd" all download links about a week ago or so (and is also why I have not uploaded my most recent resources.pak and options.zip). The negativity had/has me seriously pondering my future here at MSFN - again, this started as a project for ME to solve MY needs at the time, it was not to set out and be the next roytam1. There is a need for this project to continue. We are all intelligent and knowledgeable and assist at times we have the time to do so - but do our "positive" days act as a balance to offset our "negative" days? No, not in my opinion! You only get one chance to make a first impression. No amount of "positive" any of us ever does should be in the back of the mind of any moderator thinking "ignore the negative, s/he posts positives also". We have a lot of "alpha dogs" here and they (sometimes even me) think the world revolves around said "alpha dogs" and their topics and posts. I do not have any answer on how to resolve said "atmosphere". Most here just add the "negative" posters to their "ignore list" (and moderators even suggest this approach). Okay, "having said that" and being generally "solutions-oriented", I am hereby abandoning this thread. roytam1 has the "power" to request his threads be locked and I would request the very same for this thread - please lock this thread. v11, v12, and v13 should be considered abandonware. I have removed them from my Dropbox and all links are "404'd". v13.5 build 2022 shall be considered the only version that I am still "involved" in. This thread has reached 130 pages and has "served its purpose". We can lock this thread for use as "reference", but I do not see the need to keep this thread "alive". v11 and v12 lack too much funtionality in the "modern" web to devote any time to "going forward". v13 and v13.5 are too "identical" to warrant maintaining both. I'll start another thread for continued discussions on v13.5 build 2022. Let's please all respect each other and stay positive and that thread should serve a better purpose "to infinity and beyond".

It's possible that file 13570 may have been modified on my end AFTER build 2022 was shared online - not sure, this may be my options.zip difference in my local version versus the uploaded version. One change I have done locally but that has not been uploaded is the chrome://settings/content page. On laptops with a webcam, the settings/content page would drop below the bottom border of the inset box. Also, laptops with only a 768px display height would not display the settings/content page with the same bottom padding, so that has also been fixed locally but has not been uploaded yet. I thought those changes were all in options.zip, but I cannot say as I am 100% on that at the moment - too much going on with holiday "crap" 'stealing' portions of my "focus", lol.

My file manager's synchronize feature also indicates file 13570 is not identical between our two paks. Investigating... But will not be until later this evening.

Indexing is different. Your ungoogled resources.pak has a 688 byte file indexed as 25522 and has no indexed 25527 (when unpacked using chrome-pak-customizer, which I prefer over Python batch extract). Mine has no 25522 but has a 25527. The 688 byte file is identical in both paks. Both paks contain 1,558 files (when unpacked using chrome-pak-customizer).

I'm more interested in trying to track down where the "Translate to English" and "Share URL QR Code" context menus are coming from. Have you been able to isolate them?

I don't plan on tracking down the tiny difference. It's basically all a matter of "identical content" and how different compression/decompression packages handle "identical content".

Yep, I noticed that. It's kind of common when dealing with compression software. You get a smaller end-result if you don't "repeat" 'identical content'.

Zero interest here. I actually prefer to use 32bit web browsers even on my 64bit Win10s. And as previously mentioned, there are better alternatives once we exclude support for XP. Another reason this thread (in my opinion) should be for XP users "only".

Performing these three file changes and these three only, our resulting resources.pak file are not the same size. I'm not overly concerned as I don't criss-cross anything on what I use for me-myself. Mentioning it only for the sake of those here that may be criss-crossing.

We are all aware. As I've mentioned, I really wish that XP users had their own subset of this thread. I really dislike Win7, Vista, and XP users all being lumped into the same thread.

Nope! Nothing! I posted all 249 files in an uncompressed format so that anybody and everybody can browse through them themselves, for their own peace of mind.

Holy crap! I'd throw the computer out the window if I had to encounter that all the time, lol.

But I tried to capture a video deomonstrating the delay and the delay is less than 200ms and impossible to catch. I actually never even noticed the delay until somebody else on the forum mentioned it. I suspect the delay was much larger then 200ms on their end.

I get the delay with ALL skins. But only in XP.