win32ss / supermium

Chromium fork for Windows XP/2003 and up
https://win32subsystem.live/supermium/
BSD 3-Clause "New" or "Revised" License
2.24k stars 74 forks source link

Chrome Packaged App Depreciated Message #393

Open joeyoropesa-dev opened 6 months ago

joeyoropesa-dev commented 6 months ago

Describe the bug The chrome packaged app cannot be opened due to this message when the user tries to open the app. The user can install it but it cannot use it.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Chrome Extensions page'
  2. Click on 'Load unpacked'
  3. Scroll down to 'An chrome packaged app'
  4. Installed successfuly
  5. Open 'chrome://apps'
  6. Click on that chrome packaged app
  7. See error

Expected behavior Opened chrome packaged app

Screenshots If applicable, add screenshots to help explain your problem. Screenshot 2024-03-18 150920 Screenshot 2024-03-18 150948

Desktop (please complete the following information):

Additional context Add any other context about the problem here. Since this Supermium browser should support legacy features and one of them is Chrome Packaged App in the manifest v2 APIs this should be supported and fixed.

jonm58 commented 6 months ago

maybe is chrome_pwa_launcher.exe can't find progwrp.dll

Alex313031 commented 6 months ago

@admin-elvistrujanovic @jonm58 No, this is due to the fact that M112 and above no longer support Chrome Apps, and M120 and above no longer support NaCl (Native Client), which is needed for most Chrome Packaged Apps to work properly. And I don't mean just "don't support", I mean the code for this stuff was purged from the source code.

Also, chrome_pwa_launcher is now only used for progressive web apps, or extensions that need "background mode" support, i.e. to run on Windows startup, or to hang around after the main browser is closed.

joeyoropesa-dev commented 6 months ago

@admin-elvistrujanovic @jonm58 No, this is due to the fact that M112 and above no longer support Chrome Apps, and M120 and above no longer support NaCl (Native Client), which is needed for most Chrome Packaged Apps to work properly. And I don't mean just "don't support", I mean the code for this stuff was purged from the source code.

Also, chrome_pwa_launcher is now only used for progressive web apps, or extensions that need "background mode" support, i.e. to run on Windows startup, or to hang around after the main browser is closed.

Could just that code that was responsible for supporting and running chrome packaged apps and NaCI be ported from M112 to M120+ so that support can be implemented into Supermium

Alex313031 commented 6 months ago

@admin-elvistrujanovic Well, it turns out that the code for both Chrome Apps and NaCl wasn't entirely removed. They just removed the parts of it relevant to Linux, Windows, and MacOS. ChromiumOS/ChromeOS still supports both, so the code to run these is still present, just all of the bindings and UI stuff to run it on platforms other than ChromeOS has been removed. So maybe @win32ss could restore it. It would be a nice addition. I have my own chrome app that I made called Cog > https://chromewebstore.google.com/detail/cog-system-info-viewer/bkapefioegaebnkbjpfbbemmmcholeii which I now can't install on anything but ChromiumOS. Tis frustrating.

joeyoropesa-dev commented 6 months ago

@admin-elvistrujanovic Well, it turns out that the code for both Chrome Apps and NaCl wasn't entirely removed. They just removed the parts of it relevant to Linux, Windows, and MacOS. ChromiumOS/ChromeOS still supports both, so the code to run these is still present, just all of the bindings and UI stuff to run it on platforms other than ChromeOS has been removed. So maybe @win32ss could restore it. It would be a nice addition. I have my own chrome app that I made called Cog > https://chromewebstore.google.com/detail/cog-system-info-viewer/bkapefioegaebnkbjpfbbemmmcholeii which I now can't install on anything but ChromiumOS. Tis frustrating.

What will happen if we take Chrome/Chromium browser (and all it's libraries/dependencies) from an ChromeOS/ChromiumOS x86_64/amd64 rootfs image and tries to execute it on an linux x86_64 - will the app start and will chrome apps and NaCI will work after that - if it can work after that, there could be some possibility of porting that code to other desktop platforms like linux, windows and MacOS

What you think?