XPerceniol Posted January 9 Share Posted January 9 (edited) On 9/28/2022 at 9:57 AM, Hunterw said: Guys, how about this. Reviews on Yelp.com. Cannot read them. Map does not load, addresses do not load, reviews do not load. A lot of buttons on the site don't select when you push them. Pretty thoroughly broken. I tried a few browsers and nothing. Then I tried on my phone. Yelp will serve the first few characters and if you want to read the whole comment, and click read more, it loads an ad for their "app" which is apparently mandatory for reading reviews of anything. Seems like a real trash company. Can anyone load it? Had you any luck by chance? My question is the last one on the previous page Edited January 9 by XPerceniol Link to comment Share on other sites More sharing options...
XPerceniol Posted January 9 Share Posted January 9 (edited) Actually it would appear something was wrong with my 360 Chrome because now yelp results come up fine in: @NotHereToPlayGames 360ChromePortable_13.5.1030_Redux_1_ungoogled_MSFN but still not in Mypal. Edited January 9 by XPerceniol Link to comment Share on other sites More sharing options...
NotHereToPlayGames Posted January 9 Share Posted January 9 (edited) Whenever you encounter anything "map-related", that always suggests WebGL to me. Many folks disable WebGL and my releases used to disable it also. But 9 out of 10 "this web site does not work" was pretty much always WebGL so my releases now enable it by default and leaves it to the end-user to disable it if they so choose. Perhaps Mypal has WebGL disabled by default? Edited January 9 by NotHereToPlayGames 1 Link to comment Share on other sites More sharing options...
XPerceniol Posted January 9 Share Posted January 9 (edited) Moved to the Mypal thread. Edited January 9 by XPerceniol Link to comment Share on other sites More sharing options...
Hunterw Posted February 1 Share Posted February 1 On 1/9/2024 at 7:32 AM, XPerceniol said: Had you any luck by chance? My question is the last one on the previous page It's 13.5 only now. =( Link to comment Share on other sites More sharing options...
VistaLover Posted February 15 Share Posted February 15 (edited) As most following these threads probably know already , all the XP/Vista compatible 360EE variants (v11/12/13/13.5) are NOT compatible with MV3 Chrome extensions (which require at least Chromium 88) and, in the same vein, are NOT compatible with the "new" Chrome Web Store (CWS) ... Since sometime on Feb 13th, 2024 (depending on your location), "old CWS" URIs for extensions/themes/etc., of the format: https://chrome.google.com/webstore/detail/* now auto-redirect to the "new CWS" URIs for the same extensions/themes/etc., of the format: https://chromewebstore.google.com/detail/* This isn't a first occurrence, the same thing used to take place during the autumn of 2023, when the eventual migration to the new CWS was announced beforehand: https://support.google.com/chrome/thread/231812199 https://blog.google/products/chrome/google-chrome-web-store-redesign/ https://9to5google.com/2023/11/20/google-chrome-web-store-redesign-preview/ In late December 2023, this auto-redirection (old -> new CWS) in non-supported Chrome versions stopped taking place, but in the loaded old CWS appeared a top info-banner indicating that: Quote This version of the Chrome Web Store will be discontinued in January (2024). Visit the new store now. The user could disregard/remove this banner and continue as usual ... Well, Jan 31st 2024 came and went, but the "status quo" remained in place until Feb 13th, when the auto-redirection to the new CWS resumed ... Google staff seem to have a perverse sense of "humour" , because after the auto-redirection has been completed, in non-supported Chrome versions, a new in-page banner is being displayed, stating: Quote To add this item to Chrome, please update your browser or visit the legacy store. Visit legacy store However, clicking on the "Visit legacy store" area (JS-controlled button) will only start a vicious circle , resulting in that same "new CWS" page ... Issues with the "new CWS": The older the 360EE version you have, the more page rendering issues you'll get ; below, a screengrab with 360EEv11 (Ch69-based): Apart from the overlapping fonts, all "carousels" in the page are absent/non-functioning, because they require JS+CSS code not supported there ; these rendering issues are less/absent on higher versions of 360EE (v12+) ... But the main issue is that you can't install/download extensions from the "new CWS", because the "Add to Chrome" button is greyed out ... Mitigations This third party userscript, when installed (requires a userscript manager, e.g. Violentmonkey, Tampermonkey, etc.), will make the "Add to Chrome" button active again, however its functionality will now be limited, in that it will only enable a .crx file download to disk, not proper installation (as was the case with the "old CWS"); after saving to disk, the user has to drag-n-drop the saved file onto the "chrome://extensions/" internal tab, for the installation to proceed... The problem with that userscript is that the "name" of the downloaded extension always comes up as "undefined" (the "version" comes up correctly), so some renaming is in order after the download (perhaps one savvy person here could fix the script in that regard? ) ... Another solution I've been using is based on this extension ; the problem is that the latest version, 1.51, compatible with the "new CWS", is of the MV3-type, thus incompatible with 360EE (and Kafan MiniBrowser); here's an MV2 custom patch that will install and function as expected under Ch<88: https://www.mediafire.com/file/on5h2vit08a1xk6/1.51-mgdjkephahlgejakcnbooghhocmoppai-MV2.crx/file BTW, this is an "anonymous" upload that will expire after 2 wks of inactivity ; once installed, use the context menu on a "new CWS" tab to fetch a .CRX file to disk... Caveats of the two solutions above is that the "new CWS" won't label incompatibilities with Ch<88, so the .CRX you end up saving to disk may well be an MV3-type extension, incompatible with your "legacy" Chrome browser ; I probe the CRX files with 7-zip, opening their manifest.json files with an editor and checking for the "manifest_version" value (to be 2, that is...). A third option that might die any day now is the following: Make a bookmark of below URI: https://chrome.google.com/webstore/old/ Once loaded, it'll auto-redirect to: https://chrome.google.com/webstore/category/extensions which is STILL the "old CWS"; as long as your browsing remains confined inside that very one tab, you can access extension-URIs in the old format, e.g. by clicking on suggestions or searching in the old-store's searchbar (and make sure the search result is opened in the same tab): The back and forward nav buttons are allowed, but be sure not to click the reload one (will get you to the new CWS) ; since this is the "old CWS", it won't offer (to your "legacy" browser) MV3-type extensions in the suggestions/search results ... Of course, as time moves on, the MV2-type extensions now found inside the "new CWS" will be eventually all migrated to MV3 or purged completely, thus these workarounds will become moot... Save your MV2-type indispensable Chrome extensions while you can... PS: I'm dead certain evil Google will make sure your Ch<88 will become less effective in browsing the web over time, but I feel it'll still be good for the next two years, at least - here's hoping (of course, browsers based on much newer Chrome versions have recently surfaced that can launch under XP/Vista, granted with several issues so far, but this analysis was targeting mainly 360EE/KMB users) ... Edited February 15 by VistaLover 4 Link to comment Share on other sites More sharing options...
Milkinis Posted February 15 Share Posted February 15 2 hours ago, VistaLover said: Save your MV2-type indispensable Chrome extensions while you can... most if not all of my extensions already have a MV3 type variant or I can easily spot a good alternative. although I can't tell if ublock MV3 will work over time as well as the MV2 type variant. Link to comment Share on other sites More sharing options...
Milkinis Posted February 15 Share Posted February 15 3 hours ago, VistaLover said: PS: I'm dead certain evil Google will make sure your Ch<88 will become less effective in browsing the web over time, but I feel it'll still be good for the next two years, at least next 2 years... this indicates that Supermium 121 browser is likely to reach the next decade 2030 https://msfn.org/board/topic/184515-arcticfoxienotheretoplaygames-360chrome-v1351030-rebuild-8/?do=findComment&comment=1242523 Link to comment Share on other sites More sharing options...
VistaLover Posted March 1 Share Posted March 1 (edited) On 2/15/2024 at 3:01 AM, VistaLover said: Google staff seem to have a perverse sense of "humour" , because after the auto-redirection has been completed, in non-supported Chrome versions, a new in-page banner is being displayed, stating: Quote To add this item to Chrome, please update your browser or visit the legacy store. Visit legacy store However, clicking on the "Visit legacy store" area (JS-controlled button) will only start a vicious circle , resulting in that same "new CWS" page ... Well, it's March 1st in my timezone already , and the "in-page info banner" no longer offers the alternative of "visiting the legacy store" : Edited March 1 by VistaLover 2 Link to comment Share on other sites More sharing options...
rereser Posted March 1 Share Posted March 1 https://msfn.org/board/topic/185918-arcticfoxienotheretoplaygames-360chrome-v1351030-redux/?do=findComment&comment=1255804 Link to comment Share on other sites More sharing options...
VistaLover Posted March 1 Share Posted March 1 @rereser : I only posted my newer screenshot (of "new" CWS) above as an indication that Google's wording has changed in the interim since my previous screenshot of Feb 15th, 2024, when they offered a (non-working ) alternative choice: "... visit the legacy store" ... As for your posted mitigation in the shape of a userscript, I've already talked about it (and its shortcomings ) in my post of Feb 15th: On 2/15/2024 at 3:01 AM, VistaLover said: This third party userscript, when installed (requires a userscript manager, e.g. Violentmonkey, Tampermonkey, etc.), will make the "Add to Chrome" button active again, however its functionality will now be limited, in that it will only enable a .crx file download to disk, not proper installation (as was the case with the "old CWS"); after saving to disk, the user has to drag-n-drop the saved file onto the "chrome://extensions/" internal tab, for the installation to proceed... The problem with that userscript is that the "name" of the downloaded extension always comes up as "undefined" (the "version" comes up correctly), so some renaming is in order after the download (perhaps one savvy person here could fix the script in that regard? ) ... Kind regards ... 2 Link to comment Share on other sites More sharing options...
mina7601 Posted March 1 Share Posted March 1 (edited) I also noticed that the banner disappears if spoofed as Chrome 109, and that's the minimum version to not have that banner. (last version for Windows 7/8/8.1) Edited March 1 by mina7601 1 Link to comment Share on other sites More sharing options...
rereser Posted March 1 Share Posted March 1 @VistaLover, somehow missed your post from 2/15/2024. if i did i would not have posted. ment no disrespect. 2 Link to comment Share on other sites More sharing options...
VistaLover Posted March 2 Share Posted March 2 9 hours ago, mina7601 said: I also noticed that the banner disappears if spoofed as Chrome 109, and that's the minimum version to not have that banner. ... I launched my Kafan MiniBrowser (KMB) copy (Chromium 87 based) on my Vista SP2 x86 OS with below command-line argument: --user-agent="Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36" Then I navigated to: https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm?hl=en Guess what? Yes, the previous banner: Quote To add this item to Chrome, please update your browser Learn more no longer displayed, but ONLY to be replaced by a new banner, stating: Quote Item currently unavailable. Please check the troubleshooting guide View guide WT... ? 2 Link to comment Share on other sites More sharing options...
realisty Posted March 17 Share Posted March 17 (edited) On 3/1/2024 at 9:59 PM, VistaLover said: ... I launched my Kafan MiniBrowser (KMB) copy (Chromium 87 based) on my Vista SP2 x86 OS with below command-line argument: --user-agent="Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36" Then I navigated to: https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm?hl=en Guess what? Yes, the previous banner: no longer displayed, but ONLY to be replaced by a new banner, stating: WT... ? tried https://github.com/tarampampam/random-user-agent/releases/tag/v3.19.0 and same result , i believe somehow they're detecting our browser use Manifest v2 possible cause see: https://github.com/tarampampam/random-user-agent/issues/526 btw Thanks for such great guide and keeping us up to date. Edited March 17 by realisty Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now