-
Notifications
You must be signed in to change notification settings - Fork 71
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
Investigate optional feature support advertisement #6
Comments
If I interpret the title right I think the support for the format specifiers
should be optional. The expandable elements are difficult to realise in a terminal, e.g. for platforms like Node.js. Basically the same applies to the CSS styling which is just partly possible (colors would be possible) |
@terinjokes ping |
did i understand intention of the title properly? |
Yes, I believe so. I think the idea was that the JS would be able to see that expandable elements aren't possible and pick a different way to log, but maybe that's just too complicated. |
I feel like a lot of the text in https://console.spec.whatwg.org/#printer (specifically user experience innovation and common object formats) allows for optional feature support, which is referenced in the https://console.spec.whatwg.org/#formatting-specifiers table. I think I'll add a note in #98 so that we know to mention in some capacity, that the application of styles are up to the implementation and then close this out. |
No description provided.
The text was updated successfully, but these errors were encountered: