Closed tmm1 closed 1 year ago
Is there any reason why it changes the behavior? Why does a not pinned tab fixes the bug?
afaict its some sort of chrome bug. the pinned tabs loads too early before the --load-extension
etc are processed?
the issue in #112 only happens if you quit chrome while the pinned tab is active. when you relaunch, the pinned tab shows that "blocked" error and nothing works.
if you close all the tabs before quitting chrome (i.e. no pinned tab left), then the next launch works as expected.
fixes #112