These just correspond to abstract Tab objects in the webextension API, I don't see why they would need special treatment. > that we've been trying to get out of for a long time.
> Opening up the API to allow styling different tabs puts us in a bad position We could as well make `style` a property of the `Tab` objects, and use the existing `tabs.update()` function to update that `style` property. The method could be paired with a getStyle method.
I'm suggesting a (tab, style) method that could allow setting some specific style properties to a tab, the naming of the properties would be consistent with the naming used by the theme API. 'colored_tabs': 'if (url.startsWith('https')) 'īut that really does make sense as a manifest field, and it's quite limiting as well. If you'd like the API to be static rather than dynamic (which doesn't really make sense in my opinion), I guess a manifest field could work: The point of this API is to be dynamic rather than static. > styles statically through the manifest. > I'm not sure how we could support this. (In reply to Jared Wein (please needinfo? me) from comment #4)
