Jump to content

ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5.2036 rebuild 1


Recommended Posts

On 5/22/2023 at 4:43 PM, Dave-H said:

Not the gretest result.

Clipboard-1.thumb.jpg.b55949844fb8c552cf4860aae8793b8c.jpg

The highest I got in Speedometer 2.1 is 24.8, but despite that result, 360Chrome is still smooth for me, and all of that is under a XP SP3 virtual machine with just 2 GB RAM.

Link to comment
Share on other sites


10 hours ago, mina7601 said:

The highest I got in Speedometer 2.1 is 24.8, but despite that result, 360Chrome is still smooth for me

It's kind of a self-comparing benchmark.

What do you get with NM27 or NM28 or St52 or St55 or BNav, for example?

 

On Win10, I run Marmaduke Ungoogled v113 and it scores twice as high with the same network speeds as 360Chrome v13.5.

It doesn't "feel" twice as fast, but I prefer to run whatever browser can quantitatively score the highest and take "feelings" out of the equation.

image.thumb.png.b041c388909d6347bd3221112a593ed0.png

Link to comment
Share on other sites

12 hours ago, NotHereToPlayGames said:

What do you get with NM27 or NM28 or St52 or St55 or BNav, for example?

I will test later with St52 and St55, and tell the results. If you want me to test 1 of these browsers, then I'll go with St52.

Edited by mina7601
Link to comment
Share on other sites

not that important i think but ...
https://developer.mozilla.org/en-US/docs/Web/CSS/:is
the :is() CSS pseudo-class can be enabled with chrome://flags/#enable-experimental-web-platform-features
https://caniuse.com/css-matches-pseudo - hover mouse on chrome 68-87 (1-4)

https://developer.mozilla.org/en-US/docs/Web/CSS/:where#examples
although not mentioned here : https://caniuse.com/?search=%3Awhere
i think the :where() CSS pseudo-class is also enabled with the experimental chrome flag.

Edited by rereser
Link to comment
Share on other sites

This Proxomitron filter solves https://www.lner.co.uk/ by removing the "level 4" selector arguments and reverting to "level 3".

Technically speaking, https://www.lner.co.uk/ is NOT using a "Level 4" selector.
They're just using a 3rd Party CSS file written in a SLOPPY way to "protect" any possible 1st Party CSS declarations with the same name from 'accidentally' being applied to the 3rd Party same-name declaration.
I do NOT classify this one (and so far only one!) example web site as any pre-v88 Chromium Fork as "requiring" a :not() Level 4 polyfill.
It's just a sloppily-written CSS file striving to "protect" 3,954 declarations (which in and of itself is just an INSANE number of CSS declarations).

Very simple and should probably add a URL test to only kick in at https://www.lner.co.uk/

Name = "CSS: :not()     (style) [sj] (o.1)"
Active = TRUE
URL = "($TST(hCT=*html)|$TYPE(css))"
Limit = 128
Match = ":not(\1,\2\*)"
Replace = ":not\1"

Link to comment
Share on other sites

  • 2 weeks later...

seems the internal "translate to english" function is broken since last week.
tested in new unpacked 360ChromePortable_13.5.2036_r1_regular without modifications or extensions.
google must have changed something.

Edited by rereser
Link to comment
Share on other sites

tried them all but found only one extension that can replace the simple chrome internal translate option as close as possible.
in the sense that it also works on logged in pages and stays in the current tab with a similar translate bar at the top.
all the others have font issues , don't work , log you out or ask ( again ) for cookies on the translated site.
tested against the msfn forum page ( for retaining login ) and many others ( for function ).
can translate to 109 languages , last setting in the bar is kept until you change it.

Edge Translate : https://chrome.google.com/webstore/detail/edge-translate/bocbaocobfecmglnmeaeppambideimao
or here : https://www.crx4chrome.com/crx/142425/
-----------------------------------------------------------------------------------
optional :

a rather large extension that has many more options i do not want or use.
tweaked the settings a bit to leave only the "Translate this page" in the context menu.
hidden the extension button as it is no longer needed.
when all below is done the simple right click translate option is back again.

Content Settings : disable all 8 options.
Hybrid Translator Config : set all to "google translate".
Other Settings : disable "Enable Select Translate" , "Use Built-in PDF Viewer" , "Provide statistics to help improve the extension".

Delete in : Chrome\User Data\Default\Extensions\bocbaocobfecmglnmeaeppambideimao\2.4.1_0\_locales
all but the "en" folder.
Delete in : Chrome\User Data\Default\Extensions\bocbaocobfecmglnmeaeppambideimao\2.4.1_0\google\lans
all but the "lan_en.js" file.
Delete in : Chrome\User Data\Default\Extensions\bocbaocobfecmglnmeaeppambideimao\2.4.1_0\google\main
all but the "main_en.js" file
Delete the complete "Chrome\Chrome\User Data\Default\Extensions\bocbaocobfecmglnmeaeppambideimao\2.4.1_0\pdf" folder.

these settings with the files and folder deletes works best for me.
this extension makes a connection to deepl.com on browser start.
have added "127.0.0.1     www.deepl.com" to the windows hosts file to correct that as i don't use deepl.

will see if google restores the function for 360chrome.
if not , the original translate context menu can be removed with the change below in the chrome.dll.

Function : Drop Translate to English from Chrome mode page context menu (1 occurrence)
replace : C0 FB 8D 86 F0 02 00 00 50 E8
with : C0 FB E9 E6 00 00 00 90 50 E8

https://mh-nexus.de/en/hxd/
in HxD : file open "chrome.dll" / search-replace / hex-values / all / copy the above codes in first and second field / replace.
save the file and delete the "chrome.dll.bak" file.

for all of the above , make sure 360chrome is closed.
to be safe , copy the complete 360chrome folder to another location and perform the above in that folder first to try.
after the changes , launch 360chrome with the 360loader from that folder and not with your regular shortcut to see the results !

Link to comment
Share on other sites

Is this now happening with all versions of 360Chrome do we know?
:dubbio:
I seem to remember there was a hack which had to be done to chrome.dll before to get the translate function to work.
Perhaps it hasn't been done with the version with 13.5.2036?
:dubbio:

Link to comment
Share on other sites

No hack was required that I am aware of.

Rather, we had to become more precise and selective with telemetry removal.

If you read through Humming Owl's "notes.txt" files, you will see that ALL occurrences of "googleapis" and "gstatic" were replaced, "without prejudice".

My builds started out that way also, but then the more familiar I became with the program code, the more precisely I was able to remove telemetry without casting a "catch-all very-wide just-catch-EVERYTHING" net that caught the fish we weren't trying to catch.

One of the unintended consequences of that "just-catch-EVERYTHING" net is that things were BROKEN all in the "name of" preventing unwanted telemetry.

One of those unintended breaks was the translation feature (which I myself do not use, so can't speak toward - other than maintaining functionality for the users that do/did use that feature).

Edited by NotHereToPlayGames
Link to comment
Share on other sites

tested all v13 regular ArcticFoxie builds ( 1030 , 2022 , 2036 )
also used a chrome.dll with all googleapis and gstatic restored.
all versions fail on translate as of a week ago , v13.5.2036 worked just fine before.
so it is just a change google made that can be restored by an extension.
from google search results :
"Edge Translate is a simple and practical translation plugin that supports mainstream browsers such as Chrome, Firefox, and 360 Secure Browser".

did some more tests :
changed dns server has no effect.
a latest chrome useragent override in the 360loader.ini does not work.
cmd / ping translate.googleapis.com returns ip addresses , so no help there.
added the ip addresses in the windows hosts file without effect.
so it maybe a delayed effect from this : https://techcrunch.com/2022/09/30/google-appears-to-have-disabled-google-translate-in-parts-of-china/
i am not in china so it appears google just disabled the build in translate function for older browsers.

have removed the original translate context menu from the chrome.dll.
edge translate injects files from local storage when translate is used.
injection.js , element.js , main_en.js , element_main.js and lan_en.js. ( F12 - network )
the extension works faster anyway with more options so i will use just that.

Edited by rereser
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...