Jump to content

NotHereToPlayGames

Member
  • Posts

    5,194
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by NotHereToPlayGames

  1. 6 hours ago, D.Draker said:

    I have a question for you, how did you (or didn't?) solve the problem with gawdly awful (eye fatiguing)

    fonts in newer chromes, since disable direct write was removed ?

    For Win7 this doesn't seem to be sufficient.  But for Win10, all I needed to do was disable the OS's "Segoe" font using a registry "font substitute" and replace Segoe with Tahoma.

    Then use uMatrix to not allow third-party fonts.

  2. 2 hours ago, msfntor said:

    This website: https://www.popularmechanics.com/

    - doesn't work properly in all Chrome and Firefox forks...

    - no content - except for links to articles only, and if click on these links - we've article rendered  not properly.

    They're using an overlay so that only "members" can read the articles.

    I was able to get the site to work by opening 360Chrome's Dev Tools and deleting the "journey-blocker" element.

    On some of the articles, they had GIGANTIC image sizes and they "hid" the scrollbars.

    Best fix there was a user-style to "unset" ALL img tag height and width settings.

  3. 360Chrome v11 and 360Chrome v12 both do perform regex unicode property escapes.  But these will require "polyfill" addons to PARTIALLY resolve the other TWO of THREE categories mentioned earlier.

    Those same TWO of THREE can also be PARTIALLY resolved or have been built-in-resolved in Serpent 52, Serpent 55, and NM28 - but not in K-Meleon, NM27, ArcticFox.  Unsure on BNavigator (I opt to not update my BNav).

    But that ONE of the THREE (regex unicode property escapes) is the "modern" javascript function that will break your XP browser and has NO FIX if that browser does not handle it on its own.

  4. Here are two example browsers that "work" on XP and also can perform regex unicode property escapes.
    One is based on Chromium 86.  One is based on Chromium 75.  You should decide for yourself if you want 75 or 86.
    Open Task Manager and sort your columns by "Mem Usage".  One will use more RAM then the other.  You should decide for yourself if this is important to you.

    image.thumb.png.837e0a86e0486cf08bd11d8004e89256.png

  5. You basically MUST take the TIME to try them YOURSELF, to be perfectly honest.
    Browser choice is, and always has been, a PERSONAL PREFERENCE.
    There are Firefox Folks that cannot be UNBIASED regarding Chromium Forks.
    And there are Chromium Folks that cannot be UNBIASED regarding Firefox Forks.
    It's been that way for twenty years (in my opinion, the very essence of that opinion alone can be debated by those standing in their respective "corners").

    My only suggestion can actually be isolated to ONE web site as a "test".
    There are a lot of "modern" javascript 'functions' that older browsers simply can not "perform" - this is why the computer that you cite has its browser "holding him back".

    I can break these "modern" javasctipt functions into THREE categories but let's use only ONE of those three for starters.
    That "function" is called regex unicode property escapes.

    You only need ONE website to "test" if your brower can perform this function or not.
    It's a bank account website and you do not need an account to "test" - either the username/password fields "show up" or they do not.
    If you opt to use a browser where this web site does NOT work, then you only leave yourself open for OTHER unknown websites that you have NOT ENCOUNTERED YET to also NOT WORK!

    There are several Google web sites that require regex unicode property escapes and sure, you can "boycott" Google web sites - but Google "code" is used by non-Google web sites "all the time".
    My ONE "test" is this web site - https://secure.ally.com/
    Go to that web site without any extensions installed.
    If you get an error on that web site, the browser cannot perform regex unicode property escapes - if you cannot perform regex unicode property escapes then you WILL encounter other websites that also do not work on that browser.

  6. 2 hours ago, SC7601 said:

    Just going to put a LTS(C) version of Windows 10 and call it a day.

    Agreed.  I was 100% XP (some x86, some x64) just a few months ago on eight of all nine of my computers (with that one exception being Win7).

    The Win7 laptop is still on 7.  But four of the eight that were on XP all now run a WinReducerEX'd and NTLite'd Win10 LTSB.  I could get an LTSC from work but so far I prefer LTSB.

    I'm still "testing" Firefox versus Chrome/Chromium versions (I do not support "newer is better" and run older if they perform better).

    So far each and every time I test a Firefox version, it suffers miserably compared to Chrome/Chromium - I feel like I keep wasting my time even trying them.

    But agreed, we should not let one browser/engine take over the entire web.

  7. 15 hours ago, msfntor said:

    Why why...

    I hope more and more, that our beloved @Humming Owl will hear our chorus!

    If you read through this entire thread, Humming Owl posted that he will no longer be updating any of these and there's been at least a dozen, if not two dozen, of these types of comments since.  None of them have been replied to by Humming Owl.

    So keep on hoping until you turn blue, but these have been abandoned.

    The instructions have been provided for somebody else to pick up the torch and carry it.

    But I'm with Humming Owl on this, there are way too FEW of people that use these browsers for us to spend such a large amount of time on them.

    I think also that too many folks around here don't really fully understand what me and Humming Owl did with these browsers - we did not recompile the "engine", so that needs done by the original developer which has also (seemingly) abandoned these browsers.

  8. 39 minutes ago, Sampei.Nihira said:

    Unfortunately, it is not possible to track which of my modifications can do this "magic".
    All of the changes in settings I've made to Edge relate to privacy/security,but honestly that's too many settings I should check.
    21 flags......various Command-Line,Appcontainer,Sandbox......honestly impossible in an acceptable time to come to an exact conclusion.:no:

    My hunch is that you've only been able to trick the RESULT.

    But the amount of TIME that the test takes should still tell you something for one browser versus another.

×
×
  • Create New...