Skip to content
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

Lockdown doesn't work first time. #6

Open
fspeirs opened this issue Dec 13, 2019 · 3 comments
Open

Lockdown doesn't work first time. #6

fspeirs opened this issue Dec 13, 2019 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@fspeirs
Copy link
Owner

fspeirs commented Dec 13, 2019

In dfcd453 there is an issue whereby lockdown doesn't work the first time it is tried on a new account. You have to lock, unlock and then lockdown again for it to work. Cause unknown.

@fspeirs fspeirs added the bug Something isn't working label Dec 13, 2019
@fspeirs fspeirs self-assigned this Dec 13, 2019
@fspeirs
Copy link
Owner Author

fspeirs commented Dec 13, 2019

First-time lockdown works correctly on a fresh Chrome user on macOS. Problem was observed on managed users on a managed Chromebook.

@fspeirs
Copy link
Owner Author

fspeirs commented Dec 13, 2019

Further investigation: the extension works correctly first time if you reload the page once after the extension has been installed.

The previous failure mode was:

Sign into a new managed Google account
Allow the extension to install on an already-loaded Google Doc page.
Try to run the extension - it will fail.

The code in popup.js will work but the message will not be sent to the tab. I wonder if it's because the code in background.js doesn't get executed until the page loads at least once with the extension installed.

@fspeirs
Copy link
Owner Author

fspeirs commented Dec 13, 2019

This problem can be reproduced on macOS with the following steps:

Create new Chrome profile
Load a Google Doc
Install the extension
Try and lock down the page

The result is that the extension does not work. If you unlock, then reload the page, the extension works correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant