dideler
commented
6 years ago Thanks for the report @1natsu172 🙇
I'm worried about
New code readability requirements Starting today, Chrome Web Store will no longer allow extensions with obfuscated code. This includes code within the extension package as well as any external code or resource fetched from the web. This policy applies immediately to all new extension submissions. Existing extensions with obfuscated code can continue to submit updates over the next 90 days, but will be removed from the Chrome Web Store in early January if not compliant.
Ordinary minification, on the other hand, typically speeds up code execution as it reduces code size, and is much more straightforward to review. Thus, minification will still be allowed, including the following techniques:
- Removal of whitespace, newlines, code comments, and block delimiters
- Shortening of variable and function names
- Collapsing the number of JavaScript files
[https://developers.google.com/speed/docs/insights/MinifyResources]
Hopefully it's not an issue for us since our code is minified and not obfuscated.
I've posted a question about the 2FA on their forum: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/wLQ3Wg1ir0E
1natsu172
Chrome extension security enhancement was announced.
https://blog.chromium.org/2018/10/trustworthy-chrome-extensions-by-default.html
I think that it is probably okay with respect to permissions, external resources and JavaScript obfuscation. Just a 2-step verification may be troubling?
It may be necessary to wait for a second announce on the handling of 2-step verification of the group publisher account. We need to do when things need to happen.