Bush2021/chrome_plus 1.19.0

on GitHub

New

• 82545bb feat: add managed_updates to apply builds staged by an updater by @Bush2021

  I'm also introducing Pitstop, my new Windows app for configuring Chrome++ Next and managing portable Chrome. It provides a graphical settings editor, updates for Chrome and Chrome++ Next, version rollback, and portable-profile backups before major Chrome updates.

  Chrome++ 1.19.0 adds the integration Pitstop needs for background and in-app updates. Pitstop prepares the new build, and Chrome's "Relaunch to update" applies it. Pitstop enables managed_updates automatically, so no manual INI edit is needed.

Fix

• 0d80d13 fix: run launch commands once, without a console window by @Bush2021

  Opening a link from another app no longer reruns launch_on_startup or triggers launch_on_exit in the process that forwards the link to the running browser.

  Commands in launch_on_startup and launch_on_exit now run without a console window by default. If a command needs a console or interactive input, change it to start "" <command>. Programs with their own windows still display them normally.

• 84d01b5 fix: run exit commands before a relaunched browser's startup commands by @Bush2021

  On relaunch, Chrome now waits up to 3 seconds for launch_on_exit commands before the new browser runs launch_on_startup. This gives cleanup commands time to finish before helper programs restart. Startup commands proceed after the wait even if an exit command is still running.

• 7b80a11 fix: match launch switches by argument, not by substring by @Bush2021

  Links containing text such as content-type= or --portable no longer get mistaken for launch switches. Opening these links from another app now preserves the configured portable profile instead of potentially opening Chrome with the default profile.

Full Changelog: 1.18.3...1.19.0