NotHereToPlayGames

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.

Thanks. I have been able to track down why some skins do not have a .srx "override" file and others do. That trick lies within [HKEY_CURRENT_USER\Software\360chrome\default\ui_persist_value] keys stored in "360chrome_1.reg". Doesn't answer your original question but I learned more of the inner workings of 360Chrome :) I think your original question still seems to revolve around "http_nosafe_bar.xml" and "browser_strings.xml", both of which still contains a lot of Chinesse.

For your "skin.srx", what is your 'modified' date via file properties? Are you running the "installed" v13 or the "portable" v13?

Both of these "features" (as I understand them) sends your trackable data to a third-party, the third-party analyzes that data and then reports back if it is 'safe' or not (by their definition, not yours), then the browser proceeds based upon that reply. But WHO is this third-party, WHERE is this third-party ??? I simply do NOT "trust" either one because I don't have ANY information on HOW / WHERE / WHO "behind the scenes". When you rely on an extension such as Adblock Plus, uBlock Origin, uMatrix, Ghostery, Privacy Badger, et cetera, you have a community of users and a plethora of online reviews and critiques to base your "trust" on. In my view at least, relying on something built-in to the browser is like actually thinking that some petty "Do Not Track" 'feature' is really doing anything or that "blocking third-party cookies" actually blocks third-party cookies. I highly prefer my blacklists and my whitelists to be "local" and not sent who-knows-where and analyzed by who-knows-who. I use uMatrix and one-and-only-one list - https://gitlab.com/curben/urlhaus-filter/raw/master/urlhaus-filter.txt Then I use NoScript and only whitelist PARTIAL javascript on a small handfull of websites. If you go to 360Chrome -> Chrome -> User Data -> skin (at least that's the folder structure for the "portable repack") you should find one file with an .srx extension. If you can provide the file name for that .srx file, I might be able to see if that skin is the culprit. Or you could do so some digging on your end, the .srx will unzip with 7-Zip, PeaZip, IZArc, et cetera. There will be an .xml file (maybe two, depending on skin) and a bunch of .png files. The .xml file can be opened in Notepad++ -- look to see if the .xml references OTHER .xml files (if it does, it/they likely reside within 360Chrome -> Chrome -> Application -> 13.0.2206.0 -> skin -> skin.srx which itself will need unzipped. Which also contains http_nosafe_bar.xml and browser_strings.xml, either of which still contains a lot of Chinesse. Hope that helps.

@dencorso Are you using the "anti-tracking privacy protection" 'feature'? Or the "protect you and your device from dangerous sites" 'feature'? (I don't trust either one of them, to be honest.) Have you looked at "http_nosafe_bar.xml" that is contained inside "skin.srx" which exists in 360Chrome -> Application -> 13.0.2206.0 -> skin folder? Very close to what you have above so could be altered by alternate skins by the looks of it. What skin are you using?

You could try Roytam's "loader" and maybe it fits your needs better -- http://o.rthost.win/palemoon/palemoon-portable-loader.7z I've never actually used it so feel free to report back your opinion of it.

From what I can gather, the "libGLESv2.dll" file is needed for older graphics cards for 3D rendering. Not sure "how old", per se, as none of my computers seem to be old enough to "require" this file for 3D rendering. I don't really do a lot of 3D graphics via web browser. I used this as a test - https://www.wirple.com/bmark/ Mypal 27.9.4 scored 461. palemoon-27.9.7.win32-git-20210220-3b1d2cdd8-xpmod scored 384. palemoon-28.10.3a1.win32-git-20210220-729367b92-uxp-2b6effbf2-xpmod scored 618. bnavigator.win32-20210220-355db4de-uxp-2b6effbf2-xpmod scored 608. basilisk52-g4.8.win32-git-20210220-d9301c4-uxp-2b6effbf2-xpmod scored 645. And, drum roll, please -- 360Chrome v13 build 2206 scored 2941. 360Chrome v12 build 1592 scored 2565. 360Chrome v11 build 2251 scored 2457.

I benchmarked x86 versus x64 once-upon-a-time and x86 has better performance than x64, not the other way around. I do admit that this was a couple years ago, but the results were so CONVINCING and UNDENIABLE that I've never bothered with an x64 browser ever since.