Jump to content

NotHereToPlayGames

Member
  • Posts

    7,484
  • Joined

  • Last visited

  • Days Won

    98
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. Please show me your "About 360Chrome" popup. If it does NOT look like the below, then your version is not the version being discussed in this thread. edit: copied image to Dropbox host instead of using profile attachment
  2. You're NOT actually using jisu9_chrome.srx as your skin. What steps did you take to NOT have an XP skin with XP min/max/restore icons?
  3. Thanks. I wanted to verify that as the out-of-box jisu9_chrome.srx and it is.
  4. Can you right-click on your jisu9_chrome.srx file, select Properties, and tell me what dates you have for Created, Modified, and Accessed?
  5. ie, we know that Official UNGOOGLED does NOT contain the Translate to English context menu item. But does that context menu item RETURN if TranslateEnabled is set to ONE? My hunch is NO, which puts 360 behaving EXACTLY the way that Official Ungoogled has done things long before 360 showed up.
  6. I wonder if Official UNGOOGLED also respects TranslateEnabled? I shall test later unless you beat me to it
  7. Official Regular Chrome v86 does contain the "Translate to English" feature. edit: screencap removed from profile attachments
  8. Regarding "Translate to English" - Official Ungoogled Chromium v86 also disables this feature. edit: screencap removed from profile attachments
  9. Awesome! I'll post a how-to in one of the <reserved> spaceholders on how folks can convert the "base download" into a "non-ungoogled" and how to restore "Translate to English".
  10. I think this will require two browser restarts to fully take effect. The 155.json and the googleapis entries in chrome.dll "should" have been the only things required to restore "Translate to English".
  11. Correct. I did try that in the past. If you think of text within a div container within a div menu, I think these context menus are similar. We should be able to remove the div container without effecting the overall div menu. For lack of a better way to explain.
  12. My plans are for a fully ungoogled (including removing "Translate to English" as it requires googleapis not otherwise needed for "web surfing"). But then provide instructions/links to "restore" something like "Translate to English" or non-XP skin or non-ungoogled.
  13. @mixit We can disregard the file 13570 differences that resulted in our resources.pak (ungoogled) files being different sizes. My local file had some cosmetic changes to the extensions page (personal preference) and to the settings/content page (to correct anomolies on laptops with 768px max vertical resolution) and all of these changes were within file 13570. Apologies for any confusion. edit: discussion concluded, removed images from profile attachments
  14. for reference (I seek to REMOVE these from the context menu completely - these "features" are intentionally broken in my default ungoogled releases). edit: copied images to Dropbox host instead of using profile attachments
  15. for reference (special thanks to @rereser). edit: copied images to Dropbox host instead of linking directly to rereser's profile attachments
  16. Link to new thread -- https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/ (have not provided download links at the time of this posting, will be doing so shortly). Please consider this my last post in this thread. I kindly request that our new thread be dedicated to v13.5 build 2022. References to anything outside of v13.5 build 2022 should be considered as "off-topic". (ie, members wanting a v11 thread, for example, should kindly start their own thread.) Citing any web page that "does not work" and also does not work in Official Chrome v86 should also be considered as "off-topic". Please do not view this as "micro-managing", but rather as a CLEAN NEW START - I invite any-and-all to join me in our new thread.
  17. for reference - https://chromium.googlesource.com/chromium/src/+/refs/tags/86.0.4240.198/chrome/browser/renderer_context_menu/render_view_context_menu.cc (special thanks to @mixit).
  18. Instructions to restore "Translate to English" context menu feature. Note that this works for both the "ungoogled" and the "regular" versions. Obtain HxD Hex Editor from here - https://mh-nexus.de/en/downloads.php?product=HxD20 Copy 360Chrome's chrome.dll from the base "ungoogled" version to a temporary folder and open in HxD. Perform a REPLACE (Ctrl+R) and enter ttps://translate........... (there are 11 dots) in the "Search for:" field and enter ttps://translate.googleapis in the "Replace with:" field. Note the h in https is intentionally skipped so that the instructions do not get mangled by forum reply box or by web browser viewing. Make sure that "All" is selected for "Search direction" and that "Text encoding" is set to "(Editor encoding)". Also make sure that "Case sensitive" is not selected. Click the "Replace all" button. TWO occurrences should be replaced. Save chrome.dll and replace in 360Chrome's folder while 360Chrome is not running.
×
×
  • Create New...