Full stack web dev.
Studying FP web development approaches, while helping Mission Bit create paths to programming for underserved public school kids.
Previously @ Gradescope.
That's good. The differences aren't big; IIRC some manifest options have different names, and the top-level API's namespace differs (chrome in Chrome & Opera, browser in Firefox & Edge).
My one relevant project only makes light use of the API and so it's likely that the namespace is the only difference I'll see. And it can be done transparently -- Firefox supports chrome as the namespace, or one can use browser in Chrome with a polyfill).
The state of the "standard" is weird -- from what I can tell, Moz and MS put some effort a while back into making Chrome's APIs a W3C recommendation, but it doesn't seem like Google cared much, and I suspect the planned manifest v3 changes are partly why.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's good. The differences aren't big; IIRC some manifest options have different names, and the top-level API's namespace differs (
chromein Chrome & Opera,browserin Firefox & Edge).My one relevant project only makes light use of the API and so it's likely that the namespace is the only difference I'll see. And it can be done transparently -- Firefox supports
chromeas the namespace, or one can usebrowserin Chrome with a polyfill).The state of the "standard" is weird -- from what I can tell, Moz and MS put some effort a while back into making Chrome's APIs a W3C recommendation, but it doesn't seem like Google cared much, and I suspect the planned manifest v3 changes are partly why.