On Sat, 2012-12-29 at 02:36 -0600, Michael Catanzaro wrote:
I have one question: what do you do on websites that have forms with white backgrounds? I was trying to type on Github but gave up and switched back to Adwaita, since the white text I was typing was the same color as the form's background. :S
For browsers, specifically Firefox, I go a different way, and I've filed a bug with Mozilla a ways back on this issue. A workaround was suggested, but its an ugly workaround. Here's the bug report which should give you a decent set of steps for how it is done. Unfortunately, it seems to have fallen through the cracks and isn't being tended to.
https://bugzilla.mozilla.org/show_bug.cgi?id=746205
I could go back to 12.1, which is still supported by openSUSE, but at the same time, that one's going to be out of support once the 18 month cycle is ended.
Debian 7 will ship GNOME 3.4, and will give it security and bugfix support until 2016. If you don't mind using older software, that might be a good option for you.
That solution bothers me on two points. 1) The very concept of "A11y" means I shouldn't have to switch to older versions of other distros. If my choice is to use openSUSE with GNOME, it should work. Having to learn a whole different architecture than one I'm used to for years now just doesn't seem fair. 2) Again, referring to the concept of A11y, having to be relegated to older software instead of being able to stay with current versions o software seems just plain wrong. I should be able to stay current with the masses on the same curve.
I should be able to enjoy the benefits of latest GNOME innovation just like everyone else. Not being able to enjoy innovation simply because of one thing missing/broken just is wrong.
I could file bugs against the brokenness of 3.4 Inverse, but seems pointless if it has already been decided to drop Inverse.
Yeah, but since it is shipped in 12.2, and in a default install no less, it ought to work. It'd be helpful if you would make a bug (you can assign it to me - *no promises*) and attach a couple of screenshots of particular issues in the 3.4 theme; the Evolution issue I had already noted, but I'm sure to miss other stuff that's irking you since I don't use the theme on a regular basis.
I agree that a bug against Factory/3.6 would be inappropriate, since it's dropped by design.
I still don't understand how this would help much, and perhaps you can enlighten me. If subsequent GNOME versions drop Inverse altogether, why would anyone fix Inverse? It seems unfair of me to expect anyone to fix older versions instead of fixing current versions. 3.8 isn't that far around the corner and further distances the work folks have to do between old and current.
There's also tons of missing icons in both high-contrast themes; that'd be a significant chore somebody (else) would have to tackle for a quality user experience.
Meg Ford did the high contrast icons, and I do commend her for her work. You can always reach out to her to discuss your observations in more detail.
Oh I don't have any issue with the icons that do exist - they look nice
- I just notice that a lot of default "Gnome" icons are used because the
high contrast [inverse] iconset doesn't provide ones of its own. It looks jarringly inconsistent to me to see the default icons alongside the high contrast ones. But I guess icons are probably a ton of work.
Meg actually worked on designing High Contrast icons, rather than High Contrast Inverse icons. So, yeah, I would say that High Contrast Inverse icons don't exist either if the theme itself is dropped.
I do feel strongly however, that more investigation should be taken into exactly why upstream decided it was too much work to maintain Inverse. Despite my feeling that dropping it was a tragic decision, I do feel that there are good folks in the A11y team and they must have had a sound reason why not to proceed further with it. I'm just frustrated because this decision doesn't seem published anywhere. I've been on the GNOME A11y mailing list for many years and never saw any discussion of this decision, so when I upgraded to 12.2, I was quite blindsided by this.
Bryen