You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 15, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 15, 2017. It is now read-only.
Split 'Other' category into 'Stylesheets' and 'Other' #87
Stylesheets, considering their integral importance to web functionality, are best left grouped in a separate section than the ever-ambiguous 'Other' tab. 'Other' suggests that more than just stylesheets are included under that option.
Yes I agree about CSS, too important, and hiding in other is not helpful to the user (I could report fonts in this column too). The problem I have at this point is how to fit another column: the hostname column can't be narrowed more than it is, I actually spent a lot of time trying to make it larger, because it's not uncommon to have hostnames truncated.
Now the only thing preventing me to narrow a bit more the cells in the middle of the matrix are the header cells. If I could find a way to reduce the width of terms like 'cookie', 'script', etc., than I could narrow further the common cells. I have a prototype here where I use 'data' (for 'cookie' as 'ckie' is weird), 'img', 'plgn', 'scrpt', 'frm' and 'othr', but this is starting to look even more arcane I feel for the average user.
If there were standard pictograms for these concepts that most people could make sense just glancing at them I would try this.
So far it's the text in the header cell which blocks me. And I didn't even address translation in other language yet... Ugh. Yes pictograms would solve both problems, but I am no designer, so I am not sure where to look for this now.
I fiddled a bit around, and I found that if I can convey what a column is for within 20w x 16h pixels, that will be an improvement, allowing to introduce the css column, and to get rid of translation issues looming ahead for the header row.
This would be a nice change. Right now I just globally block 'other' because I dislike adding in requests that I can't easily validate, but many websites need it to display their CSS properly.
Working on this now for the next release. Hours spent trying to figure how to add a column while also adding more width for the hostnames. I think the new look is ok. Every pixel has been thoroughly vetted. The marker for permanent state had to be redesigned to reduce the number of horizontal pixels it was occupying.
Activity
gorhill commentedon Dec 13, 2013
Yes I agree about CSS, too important, and hiding in other is not helpful to the user (I could report fonts in this column too). The problem I have at this point is how to fit another column: the hostname column can't be narrowed more than it is, I actually spent a lot of time trying to make it larger, because it's not uncommon to have hostnames truncated.
Now the only thing preventing me to narrow a bit more the cells in the middle of the matrix are the header cells. If I could find a way to reduce the width of terms like 'cookie', 'script', etc., than I could narrow further the common cells. I have a prototype here where I use 'data' (for 'cookie' as 'ckie' is weird), 'img', 'plgn', 'scrpt', 'frm' and 'othr', but this is starting to look even more arcane I feel for the average user.
If there were standard pictograms for these concepts that most people could make sense just glancing at them I would try this.
So far it's the text in the header cell which blocks me. And I didn't even address translation in other language yet... Ugh. Yes pictograms would solve both problems, but I am no designer, so I am not sure where to look for this now.
gorhill commentedon Dec 13, 2013
I fiddled a bit around, and I found that if I can convey what a column is for within 20w x 16h pixels, that will be an improvement, allowing to introduce the css column, and to get rid of translation issues looming ahead for the header row.
insanitybit commentedon Dec 15, 2013
This would be a nice change. Right now I just globally block 'other' because I dislike adding in requests that I can't easily validate, but many websites need it to display their CSS properly.
gorhill commentedon Dec 16, 2013
Working on this now for the next release. Hours spent trying to figure how to add a column while also adding more width for the hostnames. I think the new look is ok. Every pixel has been thoroughly vetted. The marker for permanent state had to be redesigned to reduce the number of horizontal pixels it was occupying.