[Feature]: add a `forceOpaque` option for themes
See original GitHub issueCurrently xterm will warn when the css colours provided in a theme either do not set the alpha channel or have an alpha channel that is not 0xFF
equivalent.
Namely, I see a lot of the following errors:
Color: #eeeeec is using transparency, but allowTransparency is false. Using fallback #eeeeec
It would be nice to be able to silence these errors. I could add the FF
to the end of the colours but I believed that it is generally assumed that if the alpha channel is not set then it is assumed opaque. Maybe this is not the case, but could such an option be added?
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Theme Features - WordPress Codex
Theme Features is a set of specific functionality that may be enabled by theme authors. Themes must register each individual Theme Feature that...
Read more >Styling treeWidget, mdiArea, subWindow, tableWidget #428
I've read the two pdf documents Theme-Making and Theme-Config, ... we can call it Force opaque alt.base.color where we can add the name...
Read more >How To Load Themes In FL Studio 21 !! - YouTube
Note: You have to be logged into your Image-Line account in order to access these links: Link to my Rukia Theme : ...
Read more >placeholder - CSS: Cascading Style Sheets - MDN Web Docs
The ::placeholder CSS pseudo-element represents the placeholder text in an or element.
Read more >Setting Preferences — GUI 9.9.0 documentation
These preferences affect on the application look-n-feel and common functionality. If the study has just been started and other modules have not been...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm, I tried reproducing again, but I can no longer get this to happen. Something is afoot, but I’m not sure what or where… I’ll refrain from filing until I have a consistent repro.
@Fang- it’s likely a bug on xterm.js’ side, can you create a new issue with details?