Jump to content

rereser

Member
  • Posts

    272
  • Joined

  • Days Won

    1
  • Donations

    0.00 USD 

Everything posted by rereser

  1. nice catch and an easy fix, thanks. made an error the first time editing http to hxxp. a search / replace / text-string / all - for http://cseupdate with hxxp://cseupdate did the trick. chrome store remains useful for now if only to see what version of an extension is not compatible anymore. then download an older version from crx4chrome.
  2. by extension , embedded is gone and so is the context menu ... https://www.crx4chrome.com/crx/142425/ posted earlier on page 18 , with some changes to the default settings. and with some file deletes to slim it down to 1mb.
  3. "What Is Happening to Chrome's Built-In Google Translate Feature? In a community post on the Chrome Support page, Google announced its plan to disable Chrome's built-in translation service on version Chrome 95 or older. If you try to use Google Translate on an outdated version of the browser, you'll receive an error message stating that the page cannot be translated." https://www.makeuseof.com/older-chrome-losing-google-translate/
  4. 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.
  5. 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 !
  6. 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.
  7. https://philipwalton.github.io/polyfill/ maybe this can be used , don't have the knowledge.
  8. 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.
  9. latest build works also , that was not my point. would like to know what changed in the 20230318 build that fixed the layout for that page. build 20230311 does not work with the lner.co.uk page. edit , found the issue - support for :not() css was added in build nm28 20230318
  10. https://msfn.org/board/topic/184051-my-browser-builds-part-4/page/64/#comment-1241382 NM28XP build : https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230318-d849524bd-uxp-85f6a4929-xpmod.7z something in this build made https://www.lner.co.uk/ to display correctly. could someone point out what change did that please?
  11. thanks for the feedback. have no other way to test the findLastIndex polyfill except for the mozilla page. also have zero javascript knowledge , i just find , test and post. the previous findLastIndex polyfill i found somewhere else but the test returned a wrong value that i did not notice. still curious about what 'use strict'; does and if it is needed at the top of each script. hope you find the cause of the USPS login break.
  12. source : https://github.com/behnammodi/polyfill/blob/master/array.polyfill.js at the top there is 'use strict'; i left that out on copy because it was not present in the structuredClone polyfill. "use strict"; is also present in the palefill xpi polyfill.js. could that be the cause of the USPS login break ? can't test , have no account , but the login page displays fine.
  13. understand and thank you for the link. had a look at the readme.md , makes more sense now. added that polyfill and disabled the four others. will see what this does in the future. it does not slow down the browser so that is good.
  14. the last new four are in chrome 110. the link you posted is a replacement for those four ? a lot more lines ...
  15. test : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/at chrome 92 : https://caniuse.com/mdn-javascript_builtins_string_at // ==UserScript== // @name Inject String.at Polyfill // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!String.prototype.at) { Object.defineProperty(String.prototype, "at", { value: function (n) { // ToInteger() abstract op n = Math.trunc(n) || 0; // Allow negative indexing from the end if (n < 0) n += this.length; // OOB access is guaranteed to return undefined if (n < 0 || n >= this.length) return undefined; // Otherwise, this is just normal property access return this[n]; }, writable: true, enumerable: false, configurable: true }); }
  16. https://msfn.org/board/topic/184624-arcticfoxienotheretoplaygames-360chrome-v1352036-rebuild-1/?do=findComment&comment=1245462 https://msfn.org/board/topic/184624-arcticfoxienotheretoplaygames-360chrome-v1352036-rebuild-1/?do=findComment&comment=1245468 https://msfn.org/board/topic/184624-arcticfoxienotheretoplaygames-360chrome-v1352036-rebuild-1/?do=findComment&comment=1245522 my posts for "Array.prototype.findLastIndex" , "Array.prototype.at" and "Array.prototype.findLast" polyfills have been edited. got it wrong the first time ... source : https://github.com/behnammodi/polyfill/blob/master/array.polyfill.js only the first three that i posted are needed to pass the tests on https://developer.mozilla.org/ all other arrays already work in 13.5.2036. no tests available yet for the latest four very new ones.
  17. ECMAScript proposal “Change Array by copy”: four new non-destructive Array methods https://2ality.com/2022/04/change-array-by-copy.html four new polyfills are on the page. all implemented in chrome 110+ not sure we need them as i have no way to test.
  18. JS polyfill for findLast test : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/findLast implemented in chrome 97 : https://caniuse.com/mdn-javascript_builtins_array_findlast // ==UserScript== // @name Inject findLast Polyfill // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!Array.prototype.findLast) { Object.defineProperty(Array.prototype, "findLast", { value: function (predicate, thisArg) { let idx = this.length - 1; while (idx >= 0) { const value = this[idx]; if (predicate.call(thisArg, value, idx, this)) { return value; } idx--; } return undefined; } , writable: true, enumerable: false, configurable: true }); }
  19. JS polyfill for Array.at test : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/at implemented in chrome 92 : https://caniuse.com/mdn-javascript_builtins_array_at // ==UserScript== // @name Inject Array.at Polyfill // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!Array.prototype.at) { Object.defineProperty(Array.prototype, "at", { value: function (n) { // ToInteger() abstract op n = Math.trunc(n) || 0; // Allow negative indexing from the end if (n < 0) n += this.length; // OOB access is guaranteed to return undefined if (n < 0 || n >= this.length) return undefined; // Otherwise, this is just normal property access return this[n]; }, writable: true, enumerable: false, configurable: true }); }
  20. JS polyfill for findLastIndex test : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/findLastIndex implemented in chrome 97 : https://caniuse.com/mdn-javascript_builtins_array_findlastindex // ==UserScript== // @name Inject findLastIndex Polyfill // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!Array.prototype.findLastIndex) { Object.defineProperty(Array.prototype, "findLastIndex", { value: function (predicate, thisArg) { let idx = this.length - 1; while (idx >= 0) { const value = this[idx]; if (predicate.call(thisArg, value, idx, this)) { return idx; } idx--; } return -1; } , writable: true, enumerable: false, configurable: true }); }
  21. https://msfn.org/board/topic/184051-my-browser-builds-part-4/?do=findComment&comment=1243849 https://phiab.com/ : blank page ... enable : chrome://flags/#enable-experimental-web-platform-features
  22. thanks again. ! see that the chrome.dll is rebased compared to 13.5.2022 , works fine. so does the win 10 skin that was posted earlier. my "white text to black mod" in the top blue bar also works.
×
×
  • Create New...