New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better fallback on extension command contributions that use icons #89574
Comments
Instead is it possible to support codicons in context menu? @sbatten ? |
@misolori codicons are just part of our font, yes? meaning we'd have to fallback to some emoji in the native menus which would probably look out of place. |
Correct that native menus would not be able to support it (we could hide it) but in the custom menu we could show it since it's part of our font. But I worry that it might cause inconsistencies across menus. |
We will also have inconsistency if we do not show complete label. I think this issue is same for all context menu actions that can be contributable. Leaving it to @sbatten |
I think it should be stripped to be consistent. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
@misolori Since you created the issue, can you try your test extension to verify? |
Testing #89361
If you have a command that uses Codicons via
$(icon)
like:The context menu shows the text:
IMO, we should strip out the codicon reference in the context menu since it's not supported there. Otherwise authors have to duplicate commands.
The text was updated successfully, but these errors were encountered: