Really appreciate your detailed information. I'm not familiar with Firefox extension system, and I really learn a lot from your reply, thanks :))))

Maybe its time for me to study Firefox devtools and to find if there are something interesting to do :p

Firefox recently deprecated their entire legacy extension system, in favour of a new, more secure system based on Chrome's extension system, and also on the W3C's draft spec[0]

This means that many things should be identical between them: including but not limited to the packaging format, manifest format, security model, and the basic APIs for simple common browser features like tabs, page loads, network connections, etc. which gives you a very high compatibility surface area.

Naturally, APIs for any innovative features either browser have will be unique to that browser. e.g. Firefox has unique APIs for it's Container system, and it's Sidebar. I guess Chrome has some unique features too.

[0] https://browserext.github.io/browserext/

This is so impressive. These insights are really informative and helpful. I have much more concepts of these two browser after reading your reply. Really thanks for your sharing and amazing effort :)

I only focus on Chrome so far and haven't do much survey to the entension sysytem of Firefox. Integrate with Firefox could be a next challenge to move on

Another reply touched on the possible differences in extending devtools, I can't speak to that.

I've built several extensions now that worked seamlessly in both Firefox and Chrome. Firefox exposes a `chrome` object that very nearly matches the Chrome extension API and a `browser` object that goes beyond it (e.g. Promise-based async handling instead of callbacks, some additional functionality).

The only incompatibility between the two that I've specifically come across is that Firefox doesn't allow background pages to be specified as persistent. Otherwise if you're doing fairly standard stuff with content scripts, background scripts, browser actions and page actions everything should Just Work.

This extension leverage the prototype chain of HTML DOM API, so it is coupled with the front end environment.

Really nice explanation in detail, I do really learn a lot from your reply.

And I'm so glad to hear that your mate has done a great job relevant to this topic, I have search for a long time but didn't get any relative work. I will look over his repo and learn more from there.

Thanks again for your in-depth reply !

Really thanks for your information, its helpful! I wiil think more about it if there is any possibility to overcome this limitation

That's right. Especially for doing animations. There will be a lot of additional tracking work even though those operations have been tracked. Performace issue will be a challenge future work

Thanks for your appreciation :)))

Hope this tool could help you at some future time :)

I believe it will :)

I have uploaded new video preview photo with play button, it's much clear now. Thanks again :)

Much better! I'm sure it will increase the number of clicks.