Remove `cssClass` attribute
See original GitHub issueAs said in: https://github.com/zxing-js/ngx-scanner/issues/55#issuecomment-378918988 …And confirmed in: https://github.com/zxing-js/ngx-scanner/issues/55#issuecomment-379035505
The attribute will be removed from zxing-scanner
component.
We have to add docs to explain how to style the inner elements without the class and with ::ng-deep
virtual shadow piercing.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Reset/remove CSS styles for element only - Stack Overflow
Once an element has received a certain CSS style via a rule, it can not be just “taken back” – the only way...
Read more >How to remove CSS class from code behind? - MSDN
Hi,. In my page load I am adding a CSS to a href as follows.But I could not remove this CSS class in...
Read more >Apply and remove CSS class or style in asp.net code behind
In this article I am going to explain how to apply and remove CSS class or style in asp.net code behind. Description:.
Read more >How to add or remove multiple Css Class names from ...
Below I am adding and removing CSS class for a Label control. Same way it can be done for Button using the CssClass...
Read more >How To Remove a Class Name - W3Schools
Learn how to remove a class name from an element with JavaScript. Remove Class. Click the button to remove a class from me!...
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
@csutorasr thanks for the example, looks very clean in deed. I’d suggest to go with this solution, I think we’re making our life harder by introducing more Inputs. If somebody doesn’t understand how to properly use that syntax he can still (for now) use the hacky
/deep/
workaround but I don’t like the idea of more complexity with Inputs just b/c some people might not understand itYes it must be removed. I posted some parts at the wrong issue (#55). I add a stackblitz to the other issue.