-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extension not saves auto/handle tumbler and not saves inspector-settings #78
Comments
Thank you. I will look further into this. |
Just tried to duplicate the issue on Windows and haven't been able to. I will try on my MacBook as well... Regarding the 2nd issue "chrome inspector not saves console options", that is likely an issue with that version of DevTools specifically and not NiM. Might want to try changing DevTools versions. These blog posts may help https://blog.june07.com/nim-custom-devtools-url/, https://blog.june07.com/devtoolscompat/. |
Thank you for your patience. I was just able to duplicate the issue on my macbook! A temporary workaround would be to go to your NiM settings and save them after changing from auto to manual or vice versa. Please give the workaround a try and let me know if that helps... |
Seems to be a race condition between the switchHandler and the model update. Still investigating a fix. |
I do not know how to save the settings manually // |
oh so sorry, thanks, it's works |
Glad the fix worked for you. Just a heads up. Considering the recent times as well as the very long delays with the Chrome Webstore (although the NiM project has been fortunate not to have had any issues), I am going to delay any updates to the Chrome Webstore until further notice. |
Thanks for your patience on this one. Fix has been pushed here https://github.com/june07/NiM/releases/tag/v2.4.2. Will be pushed to both Google/Microsoft stores shortly. |
NiM extension is beautiful, but after a year of rest, I launched it again on a new project and discovered two problems.
MacOs 10.14.6 Mojave, Chrome 80.0.3987.132
The text was updated successfully, but these errors were encountered: