3 ms·

Thank you. We hear a lot of complaining about people not having problems, but wanting to predict there will be. It's refreshing to have the perspective of some

Thank you. We hear a lot of complaining about people not having problems, but wanting to predict there will be. It's refreshing to have the perspective of somebody who actually had the problem. Also, the stance of the ublock origin maintainer on this: https://news.ycombinator.com/item?id=14973424 https://news.ycombinator.com/item?id=14973424 He clearly states why FF is NOT becoming a chrome clone as everyone says.

Animats 9y ago
Here are the issues I ran into: - In Webextensions, retrieving something from local storage is an async operation. In Jetpack, it was a sync operation. This has the potential to create race conditions if you're updating a cache. It's OK in my application, because a double update is harmless. - Webextensions, by default, will run in incognito mode. That's because the "incognito" key in manifest.json doesn't support "not allowed" yet. ([1], table "Browser compatibility") That should have been both supported and the default, as it was in Jetpack, because it's a form of permission. Requires a one line workaround. - The use of "id" requires a better explanation. When upgrading, you have to use the same ID your previous non-Webextension used, even though that ID ends with "jetpack". The documentation doesn't indicate anything like that. But the AMO uploader detects this and gives a good error message. The new development and debugging environment on desktop is nice. The add-on worked the first time on Android, so I didn't have to use the more difficult environment for mobile debugging. [1] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/incognito https://developer.mozilla.org/en-US/Add-ons/WebExtensions/ma...
- sametmax 9y ago
  Insteresting.