Feature request: separate outline settings for text information only
See original GitHub issueI’m using uniqueDesignation
to add text beside a symbol, and in order to make it legible against varied backgrounds I need it to render as black with a white outline. I saw #50 and have been using outlineWidth
successfully to achieve this effect. Unfortunately, this also applies the same outline to the icon itself, and in my case this actually has the effect of reducing legibility of certain symbology decorations against certain backgrounds. I’d like to see a way to independently control the outline so that “text” is outlined while “symbols” are not.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Outlining feature requests - Forum
Re the outlining pane, I'd like to be able to.... Have separate formatting options just for it. Allow me to select background color,...
Read more >Create an "Response:Outline view" for CDATA - SmartBear ...
Currently, the OUTLINE view in the Request and Response only apply to well formed data. Defined by the WSDL or WADL. In cases...
Read more >font-feature-settings - CSS: Cascading Style Sheets | MDN
The font-feature-settings CSS property controls advanced typographic features in OpenType fonts.
Read more >4.14 Font outline unaffected by opacity - Unreal Engine Forums
The font and the outline have two separate color settings that can be set independently. If you would like to fade out the...
Read more >Feature request | Altium Designer | Knowledge Base
Something is not working the way I expect or want it to work. I would like to see an enhancement.
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
I have verified that there is an error with tead when I updated Node from v8.9.4 to v10.16.3. I have contacted the maintainer of tead to see if he is planning to fix this, otherwise I will have to look into other solutions.
Totally forgot I didn’t actually open a PR. Once this lands, what’s the timeline look like for a release to NPM?