Questions regarding FF implementations (file input behaviour, faviconUrl quality, host_permission reload)

[hicallmeal (al)]

Thanks taking the time to reply!
I was actually going by a comment you made in the first article I linked, which after testing I encountered myself as well.

@hans_squared

For the sake of simplicity, the test extension forces the user to enable the “<all_urls>” permissions manually, and reload the extension manually. A finished extension could do this with browser.permissions.request() and browser.runtime.reload()

So I just wanted to confirm if this was purely within the debugging env, or published as well. I will take it that only when debugging!

RE 2. Yep, I actually did some more research and made another comment about that. So all good on that front.

3. Thanks for the suggestion - it’s less that the API is unstable (from what I’ve seen it always yields icons when there is one available), but the quality is seemingly varying.
   Would love to hear the inner workings of it - I struggled to find the source on Searchfox, as it [tab.favIconUrl] appears to stem from internal browser APIs.

4. That’s really helpful, thank you! I think that’s what I will base it off of.