Windows- & MacOS-specific CRX install failure
11 views
Skip to first unread message
Warren Halderman
8:43 PM (2 hours ago) 8:43 PM
to Chromium Extensions
I was wondering why my extension update wasn't being propagated for weeks after release. Turns out there was a filename casing issue that only affected Windows and MacOS users.
You may already know, but most Linux-based file systems and (to my surprise) ZIP archives are case-sensitive and consider "url.js" and "URL.js" to be different files, but Windows and MacOS consider them to be the same, leading to invisible bugs when developing and testing on Linux-based operating systems...
When validating newly uploaded packages, would it be possible to also verify that there are no "duplicate" filenames in any directory of the archive? I realize it would only help a minuscule portion of developers, but it would be incredibly helpful.
You may already know, but most Linux-based file systems and (to my surprise) ZIP archives are case-sensitive and consider "url.js" and "URL.js" to be different files, but Windows and MacOS consider them to be the same, leading to invisible bugs when developing and testing on Linux-based operating systems...
When validating newly uploaded packages, would it be possible to also verify that there are no "duplicate" filenames in any directory of the archive? I realize it would only help a minuscule portion of developers, but it would be incredibly helpful.
Reply all
Reply to author
Forward
0 new messages