NotHereToPlayGames

NEITHER DO I !!! I can only offer assistance where I can duplicate the claimed scenario here - which I have been unable to do. I have no special cache settings and I do not use virtual memory. I'm on an i7-4770 with 16GB RAM, running 32-bit 360Chrome v13 build 2206 on WinXP x64. I have 32 bookmarks so opened them all SIX times (ie, I opened 192 tabs). I then reviewed Task Manager and only saw 86 .exe's opened. So I then opened all 32 bookmarks in a new window (so now one window has 192 tabs and the other has 32 tabs). I opened two more sets of 32 so now that second window has 96 tabs open. So I now have a total of 288 tabs open. But Task Manager still only shows 86 .exe's (if I counted correctly - I screencap'd below as witness to my test-run). You did cite v11 - how many .exe's does v11 show when you have a *sh!t-L0ad* of tabs open ???

You have UNREALISTIC expectations. Plain and simple. Either you need Chrome and the VAST amounts of web that only CHROME can give you or you do not. Give us a LIST of these 150 to 300 tabs so we can inspect them ourselves. I have a strong hunch that MyPal v27 can handle those 150 to 300 tabs better than anything "newer". "Newer" is simply NOT always "better". Throwing 300 tabs at an i3 - come on man, you can't be serious! Disable ALL .js, disable ALL .css, disable ALL images, view ONLY the TEXT on those 300 tabs and you might be fine that way. I'm with @Vistapocalypse "The solution is obvious. There is no need for 150 open tabs!" NOT ON AN i3 !!! I'd be interested in seeing that list of 150 to 300 tabs so I can gauge for myself which browser can handle that task best.

Out of curiosity and being new to the world of Tampermonkey/Greasemonkey/Violentmonkey, what userscripts are users here using?

Didn't say it was for "everyone". In the case of my Autofill extension, the lightning bolt still turns yellow when it performs its tasks - I do NOT need the "badge" also. In the case of my Redirector extension, I only disabled the "on" indicator, it still displays "off" when it is off. I'm providing a means-to-an-end for OTHERS that see those badges as EYESORES. If that isn't you, no skin off my back My extensions are ALL OR NOTHING - either I browse with ALL of them on/enabled, or I browser with ALL of them off/disabled (ie, Incognito Mode). But like I say, "not for everyone". Guess I forgot to put my "mileage may vary" footnote, lol.

Here's a new find I thought I'd share (at least new to me). I don't use a "ton" of add-ons/extensions but one of the eyesores for the few that I do use is the "badge" that some extension authors provide a config setting to disable and other extension authors do not . Without diving "too deep" into the details, Chrome extionsion .crx files and Firefox extionsion .xpi files both can be extracted via 7-Zip (to name just one program). We do it quite a bit around here to modify manifest.json for min/max browser versions, for example. Once you extract the .crx/.xpi for the extension you seek to modify, you'll find several .js files (sometimes just dropped in a root directory, sometimes in their own sub-folder). Drag-and-drop all of the .js files into Notepad++. Now do a Ctrl-F (find) for "badge" (without the quotes) and select the "Find All in All Opened Documents" button. In the results, you'll likely see Text/Color and Background/Color items in only one of all of the .js files - that is the .js file we will modify. Look for text: contained within parentheses followed most likely by a varialble name or actual text/number inside of single-quotes. To turn the "badge" OFF, replace the variable name with two single-quotes and no space between, ie '' . If the text: contains actual text inside of single-quotes, simply delete the actual text but keep the two single-quotes. Save and repack the .crx/.xpi and install into your browser. Or, simply just modify the .js file in the browser's Extension folder/sub-folder.

Um, is this a "real" post/enquiry ???

Much appreciated, @VistaLover NONE of your suggestions worked - BUT they were enough to get me moving in the right direction with a little over two hours of trial-and-error, so many thanks! And I may have inadvertently mislead (apologies) - I cited two about:config settings from my MyPal / New Moon profiles (one for autorefresh, one for onbeforeunload). I couldn't post a test URL because I only allow javascript on a whitelist basis so I actually only encounter this "nuisance" on one of my requires-login web sites. And the "nuisance" is only after I log out. Admittedly, I tried over a dozen extensions from the Chrome Web Store before posting my enquiry - I couldn't get any of them to work and in frustration I gave up and posted my enquiry. I have been using Stylem/Stylus for years and it's one of my biggest must-have add-ons. I've never bothered with Greasemonkey/Tampermonkey and therein was the FIX for this nuisance - again, many thanks! The cited archived userscript did not do the trick because unbeknownst to me at the time, the nuisance was a META refresh. And I was able to find a UserScript at Greasy Fork to disable it -- https://greasyfork.org/en/scripts/16079-disable-autorefresh/code

Assistance, please. I've always used these two about:config entries to block browser redirects. 1) accessibility.blockautorefresh boolean true 2) dom.disable_beforeunload boolean true Does anyone know how to block "beforeunload" redirects in Chrome-based browsers?

The standard unpacker ( https://github.com/myfreeer/chrome-pak-customizer ) does work on YandexPortable 19.6.1.153, but it does not work on YandexPortable 17.4.1.919. My Yandex download source is SourceForge - https://sourceforge.net/projects/thumbapps/files/Internet/Yandex Browser/ So I tried YandexPortable 17.11.1.988 (last of the v17 but does not work in XP, 17.4.1.919 is last XP as far as those hosted on SourceForge) and it did unpack with the standard unpacker. So then I tried YandexPortable 17.6.0.1633 (the first release not available to XP users) and it did unpack with the standard unpacker. Then I tried YandexPortable 17.4.0.2383 (first in the 17.4 series) and it did not unpack. So it appears the non-standard resources.pak format is only with the XP versions.

Agreed! @Dixel, I was not pushing some conspiracy, I was attempting to decompile Yandex Browser in the same fashion I have done with 360Chrome, nothing more. @i430VX - when you open Yandex's resources.pak in EditPad, you had to scroll down several rows to get to your screencap. Here's what I see when I open Yandex's resources.pak in EditPad. Basically, those blue horizontal lines are separations between File #1, File #2, File #3, et cetera. What I want to be able to do is open File #1, for example - but you can NOT without UNPACKING resources.pak. 360Chrome's resources.pak has 1,561 files contained inside it (at least my modified resources.pak, I may have deleted some resources), and I can open each and every one of them, edit, and repack as a .pak. There's some .json, some .js, some .html, some .png, and several hundred files without an extension - all of them can be opened and studied, modified if desired, saved and repacked. ungoogled-chromium-86.0.4240.198-1_Win32's resources.pak has 1,622 files contained inside it - I can open every single one of them. Chromium v49.0.2623.112's resources.pak has 1,647 files contained inside it - I can open every single one of them. Conspiracies aside, I should be able to unpack Yandex's resources.pak so I can see what's inside - but the standard unpackers will not unpack it. My curiosity exists solely in attempting a new skin/theme and moving the tabs to the middle and perhaps even bypassing the "tableau" altogether. I'm NOT a fan of Yandex - but I do like to "tinker" and reconstruct software here and there - but Yandex doesn't follow the historical norm of Chrome-based browser files as far as unpacking and repacking.

That's exactly what I use for 360Chrome (where resources.pak for build 2206 is 5.2 MB). But it does not work for Yandex (where resources.pak for version 17.4.1.919 is close to FOUR TIMES the size at 20.2 MB). So I can't help but be curious as to what is HIDDEN inside resources.pak that the creator doesn't want us to see by using conventional unpack methods. I also have to wonder if creating a resources.pak that cannot be unpacked by the end user is even in agreement with terms between Yandex and Chrome/Chromium.

Speaking of Yandex -- do you know of any way to unpack resources.pak, the method I use for 360Chrome does not work for Yandex?

MSFN is here for US (the "tweaker", the "beta tester"). I assure you that our/your parents have never heard of MSFN, are completely LOST two sentences into MSFN content, et cetera.

Ah, Flash is another story. My dad visits a crossword puzzle site that used to be Flash but the web site has since updated. Our family had the opposite as far as Flash compatibility - it wasn't the in-their-70s parents that couldn't live without it but the Gen X sister! And for her it was her SCREEN SAVER program that she felt she "couldn't live without". So I logged her CPU temperatures and showed her how her laptop runs right around 34 to 38 degrees C and SKYROCKETS to 82 to 84 degrees C when the SCREEN SAVER is running. She, THANKFFULLY, hasn't used a (d@mn) screen saver since

Hmm, how to reply without stepping on toes? And apologies in advance if a toe gets stepped on. My parents are in their 70s. When it comes to computers and a parent in their 70s, you can not teach an old dog new tricks. And the very mention of "Classic Theme Restorer" tells me that your parents are the same way, correct? So you've compromised by providing an "updated" browser but adding an add-on so the parents "see what they used to see", correct? "Up-to-date" can mean so many things. They're running Win7 which ended support over a year ago! But you've provided them with a "warm fuzzy" feeling of being "secure" and "up-to-date" by having them use a BETA browser? Yes, I said BETA - because that IS what the RT1 browsers are! I mean, the decision is obviously yours. But I can tell you what me and my brothers and sisters were all but "forced" to do. Answering computer questions from a parent in their 70s that doesn't "use" the computer for anything but email, reading news web sites, and playing solitaire gets OLD very very very quickly! Teaching the old dog to use any "add-on" turned out to be even worse! We bought them a Win10 computer, installed Chrome, and *FORCED* them to the *LEARN* Chrome. What used to be 30 questions per week is now only 3 per month - so THAT, my friend, is PROGRESS A *beta* browser is NOT for a 70yr old! (there are exceptions!) The average 70yr old has ZERO use for an "add-on", they require pretty much everything "default". Not likely the "two cents" you were hunting for -- but I am speaking from experience, I gave up a long time ago trying to "teach" my parents MyPal, Pale Moon, New Moon, Firefox. "Mileage may vary"

Here's my WinXP skin if anyone is interested. Install steps -- 1) Download the WinXPskin file from here -- https://www.dropbox.com/s/83mdky3jup73l59/WinXPskin.zip?dl=0 2) Go to the official skin download page and install the "base skin" that my WinXP skin builds on top of -- https://skin.chrome.360.cn/new/index.php (this step is important because it sets registry and config settings). 3) Scroll down and install the "chrome经典" skin -- it is between "Optimus Prime" and "Pink Colour". 4) Exit 360Chrome. 5) Use your file manager of choice and navigate to (I use the PORTABLE so your location may differ) -- ...\360Chrome\Chrome\User Data\skin 6) Delete the "geekkoedlankmgbjiogodoaibieloiep.srx" file (this is the skin file installed in Step 2 -- we needed to install it for other config settings to be set). 7) Open 360Chrome -- it will revert to a default skin but keeps other needed config settings saved. 8) Exit 360Chrome. 9) Unzip the "WinXPskin.zip" file downloaded in Step 1. 10) Copy/replace the extracted "en_skin.srx" to replace the existing "en_skin.srx" (save a copy of the old if you prefer) at this location -- ...\360Chrome\Chrome\Application\13.0.2206.0\skin 11) Copy/replace the extracted "skin.srx" to replace the existing "skin.srx" (save a copy of the old if you prefer) at the same location as Step 10. 12) Copy the extracted "geekkoedlankmgbjiogodoaibieloiep.srx" (need to keep this file name!) and place at this location -- ...\360Chrome\Chrome\User Data\skin 13.1) Edit the "360chrome_1.reg" (again, this guide is for the PORTABLE version) file at this location -- ...\\360Chrome\Chrome\User Data\Registry 13.2) Do a Ctrl-F (Find) for "skin" TWICE in the .reg file opened for editing in Step 13.1 -- change the "SkinPath"="skin\\jisu11.srx" line to read "SkinPath"="skin\\geekkoedlankmgbjiogodoaibieloiep.srx" 13.3) Save and Close "360chrome_1.reg" 13.4) For those with the INSTALLED version versus the PORTABLE, you "should" be able to edit the SkinPath at [HKEY_CURRENT_USER\Software\360chrome\default\ui_persist_value] (but I did not personally try this). 14) Open 360Chrome and the new skin will be installed. Note: still on the To-Do List - correct maximized versus windowed tabs on top 8-pixel height difference (I seldom use windowed versus maximized so didn't notice this until writing install instructions). Update: Windowed versus maximized now resolved. Link in Step 1 updated.

Here's a brief height comparison for a WinXP skin I've come up with for 360Chrome. I focused primarily on tabs in the middle as I prefer my WinXP applications to have a standard title bar and standard XP min/max/restore/close icons. I'll post files and instructions over the next day or two.

Added an "update pack" to first page. "Mileage may vary".

DISREGARD. This release is a GIGANTIC step BACKWARD as far as an English release goes. "Inspect" has reverted to Chinese. And "simple" (albeit minor) fixes no longer properly attribute themselves to the embedded "lookup tables" (ie, capitalizing the "s" in the Options Page "UI style" and "Personal stuff"). Minor, I know, but evidence that "lookup tables" no longer work (which I suspect is the root cause for the Chinese contained within "Inspect" but I'll not be digging into it myself. I will be sticking with build 2206 for now and may revisit when the next repack is released.

Updated to v13.0.2212.0 https://lrepacks.net/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html

Sorry, I have no interest in Yandex. For starters, the portable version I found (17.6.0.1633) requires Win7 as opposed to XP. And secondly, it's only as new as Chrome 58 [April 2017] whereas 360Chrome v13 is Chrome 86 [October 2020]. But based on file structure of portable 17.6.0.1633, NOPE, the method can NOT be applied to Yandex.

I have a "WinXP skin" that I can upload and provide installation instructions if there are enough folks interested.

Here's one -- https://lrepacks.net/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html

Odds are it is the website you are downloading from. Try a different download from a different website.

There's a "million" reasons that give that cert warning. Proxy server, revoked certificate, lack of WinXP updates, et cetera ad nauseam. google.com.hk shows up perfectly fine for me. Also, your screencap shows an instance of Mypal / New Moon / Pale Moon running -- what does it show for google.com.hk? And if you Mypal / New Moon / Pale Moon is NOT using a Proxy, then make sure that 360Chrome is also NOT using a Proxy.