I'd be concerned that some contributors might try to add data about Firefox for iOS to properties that aren't WebExtensions-related, which doesn't really have a point because of iOS browsers all just using WebKit as their engine.

Well, which browsers are visible for which category is controlled by browser‑compat‑toolkit (and kumascript), so even if someone were to try to add Firefox for iOS to non-WebExtension features, it wouldn’t show up in MDN anyway.

Regarding my previous comment, I wonder if we shouldn’t have the linter check for certain browsers in certain feature categories? E.g. Firefox for iOS info being added for a feature in html/ would cause the linter to fail. I think that’d make it easier to add these “edge-case” browses safely.

At first, I thought that wouldn’t be a problem, but after seeing #2484, I’ll add that to the linter in a separate PR.

Update: I have now opened PR #2487 to add that.

There is still no implementation of themes in Firefox for iOS. I think it is too early to even add Firefox iOS to this repo (even if it is just for webextensions). Implementation might never happen at all and I think it is too much overhead for us now to maintain this here. What do you think @wbamberg?

I think it is too early to even add Firefox iOS to this repo (even if it is just for webextensions). Implementation might never happen at all and I think it is too much overhead for us now to maintain this here. What do you think @wbamberg?

I agree.

I'm closing here then. We can re-consider this if it should become a reality.