Sorry this dropped off my radar. I've given the various bugs connected to this one another read and it seems to me that: * There are reasons we would not want to enable `context-fill` generally. svg params seems to be the alternative, though it is still an unofficial draft * Enabling context-fill for extensions would be a workaround for the meanwhile. One futher restriction would be to only enable it for privileged extensions I think we should extend `devtools.panels.create` to take more than just a string for the icon. It could be an array modeled similar to `theme_icons` from browser_action. This doesn't require us to enable context-fill which does not seem to have a future in web content, would allow us to wait for svg params, and solves the use case of having different themes, even if more limited than what context-fill could provide.
Bug 1553996 Comment 14 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry this dropped off my radar. I've given the various bugs connected to this one another read and it seems to me that: * There are reasons we would not want to enable `context-fill` generally. svg params seems to be the alternative, though it is still an unofficial draft * Enabling context-fill for extensions would be a workaround for the meanwhile. One futher restriction would be to only enable it for privileged extensions I think we should extend `devtools.panels.create` to take more than just a string for the icon. It could be an array modeled similar to `theme_icons` from browser_action. This doesn't require us to enable context-fill which does not seem to have a future in web content, would allow us to wait for svg params, and solves the use case of having different themes, even if more limited than what context-fill could provide. Does this solve the use case for you?