jtackaberry
commented
10 years ago Yeah there's no way to override a global default for individual sites right now. Rather than setting a global default, you could apply a per-site value for those sites that need it. This is perhaps less convenient for your use-case.
When I found out about nosquint I was happy there was a solution to low contrast sites. Low contrast is a fad I hope dies soon, or sites start using an alternate css control that can be toggled..
But I soon found out that nosquint works on an opt-out basis. EVERY site gets the treatment unless an exception is made. I want it the other way around. To work best, there should a button to toggle nosquint on/off for the current site, and another button to add it to an 'always on' list. Sites in the "always on" can be removed if they come to their senses. You can keep the opt-in of the current nosquint and let the user choose which they prefer opt in or opt out as the basis of operation.
Another problem is light text on dark backgrounds. Sites that use both "gray on white" and "light on dark" text are common. There should be the ability to recognize the text/background contrast and leave it alone if it meets set thresholds. As it is now, nosquint turns "white on dark" to "dark on dark", which is not readable.
Right now I leave nosquint off most of the time. On some sites if I need to see something better I just hit cntl-a for a temporary contract change. Nosquint is manually activated only for particularly bothersome sites I need to see. Then I deactivate it.
That is not a good way to operate an extension.
I won't contribute to nosquint as it is now, but add the features above and I will.
githum.com has bad contrast. I just hit cntl-a to review what I've been writing. Corrected a few typos.