top | item 23287038

(no title)

geza | 5 years ago

I tried porting the extension over to Firefox when Firefox switched to WebExtensions, and at the time there were tons of incompatibilities, mostly with Firefox's Shadow DOM implementation (HabitLab is a huge and complicated codebase, porting it is non-trivial - I had an issue tracking it at https://github.com/habitlab/habitlab/issues/137 ). I'm sure it's a valid option for smaller extensions however. At the moment I'm trying to get it accepted on the Edge store, as Edge is much more compatible with Chrome extensions than Firefox.

discuss

order

jacamera|5 years ago

Have you tried again with Firefox recently? I'm the developer of an extension that makes extensive use of the Shadow DOM for UI components in content scripts. I recently ported our Chrome-only extension over to Firefox and had a few minor issues but none with the UI. I'm even using React for Shadow DOM UI components and it's been working well in both browsers.

hanklazard|5 years ago

I wonder if others are thinking the same re: Edge and whether this will eventually lead to chrome losing users to Edge as useful extensions find a home there.