Remove CSS-only features from feature count
See original GitHub issueDescription
The + 25
part is not useful for users, since they can’t disable them via the interface at all. It doesn’t even make sense for those who actually read the code, because it is never updated.
I propose that we just drop the addition (like 9179481
(#3297)). We may need to find another way of informing users CSS-only features (e.g. change the “useful to undo unwanted styles” line to “useful to revert CSS-only features”).
Screenshot
No response
Example URL
chrome://extensions/?options=hlepfoohegkhhmjieoechaddaejaokhf
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How Do You Remove Unused CSS From a Site?
I'll delete that CSS! And you do, only to find out it wasn't unused at all and you caused big styling problems throughout...
Read more >Using CSS counters - CSS: Cascading Style Sheets | MDN
Counters can only be set, reset, or incremented in elements that ... The counters() function is used when the count for nested levels...
Read more >featureCounts: Count Reads by Genomic Features in Rsubread
Assign mapped sequencing reads to specified genomic features.
Read more >featureCounts returning a matrix of counts full of 0...
Hello, I'm using the RNASeqGeneEdgeRQL workflow to process some RNASeq data. I've tried to create the required matrix of counts through the featureCounts ......
Read more >Graphical View Legend - NCBI - NIH
The NCBI Genome Workbench uses similar graphical renderings. Generic Feature Rendering; Gene Model Features; Clone Placement Features; SNP ...
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 think only
refined-github.css
andgithub-bugs.css
contain a lot of orthogonal changes. We can consider them as a whole feature (e.g. “refine-appearance” and “fix-appearance-bugs”).I’d rather have an exact count too, but there’s a lot of little improvements in the main CSS file, how do you count those? Is every selector a feature? Or maybe one for every descriptive comment?