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

[Guest]

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

Not the gretest result.

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.

[NotHereToPlayGames]

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.

[Guest]

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 May 25, 2023 by Guest

[rereser]

.

Edited Friday at 01:13 PM by rereser

[NotHereToPlayGames]

I forgot about the "experimental" flags.

I wonder if they enable :not() Level 4?

 

edit:  Nope, they do not.  No :not() Level 4 without a polyfill.

Edited May 31, 2023 by NotHereToPlayGames

[rereser]

.

Edited Friday at 01:13 PM by rereser

[NotHereToPlayGames]

1 hour ago, rereser said:

https://philipwalton.github.io/polyfill/
maybe this can be used , don't have the knowledge.

I see nothing there specific to converting :not() Level 4 back to natively compatible :not() Level 3.

[NotHereToPlayGames]

https://www.lner.co.uk/

For reference because it always takes two minutes to find.

Edited June 1, 2023 by NotHereToPlayGames

[NotHereToPlayGames]

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"

[rereser]

.

Edited Friday at 01:13 PM by rereser

[Dave-H]

Confirmed here, I'm just seeing a server error reported after a long delay.

[rereser]

.

Edited Friday at 01:12 PM by rereser

[Dave-H]

Is this now happening with all versions of 360Chrome do we know?

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?

[NotHereToPlayGames]

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 June 10, 2023 by NotHereToPlayGames

[rereser]

.

Edited Friday at 01:12 PM by rereser