-
Notifications
You must be signed in to change notification settings - Fork 375
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
Broken chrome builtin unpackaging compatibility #497
Comments
Interesting, APPNOTE says you should use idea for adding function there is avoid constructing file names like but I think if chrome really uses backslashes we should add option like |
As i mentioned before, problem is specific for creating archive on windows, broken archives cause error in all desktop browsers (Opera, Edge, Firefox and others, not only Chrome) for windows and mac. I tried creating the same archive with same pkg version from mac and it do not cause any errors. So i conclude that the In other words browsers are incompatible with windows created archives, after changing to backslash 🤔 |
After some research promlem was opposite in replacing shashes on backslashes, |
I don't consider myself an expert on working with zip archives, but i detected that commit 9c37fa8 brokes compatibility with chrome extension unpackaging compatibility on windows (may be not only on windows).
Attempting to install archived extension you receive an error and temporary extracting folder looks like this:
The text was updated successfully, but these errors were encountered: