On 24/12/2016 13:33, Xidorn Quan wrote:
On Sat, Dec 24, 2016, at 11:59 PM, Gijs Kruitbosch wrote:
On 24/12/2016 01:24, Ehsan Akhgari wrote:
On 2016-12-23 8:13 PM, Xidorn Quan wrote:
I don't think that would be a problem, because the number of people who
use navigation caret is rather limited, and thus I don't think websites
would likely hide the caret for normal text intentionally to annoy
people who use that.
Also people can always specify ":root { caret-color: auto !important; }"
in their user stylesheet to effectively disable this property if they do
find any website doing annoying things with it.
The reason why I mentioned this is that this feature is related to
accessibility, and I'm worried that respecting random styles for this
may hinder the visibility of the caret on the screen, but I suppose as
things stand the caret may not be fully visible everywhere on the
page... I'm fine with leaving things as is personally.
Can we make sure that this property like color: and background-color:
before it is affected by the existing prefs (for which we have browser
UI, unlike "add this random CSS to userContent.css") to turn off website
colors and override them with system- or user-configured foreground and
background colors? That would likely help with at least some of the a11y
concern.
It would be controlled by the same pref as other color properties that
we have browser UI for.
Are you proposing that we should add another pref for that? I don't
think it's worth.
No, just that we should make sure it is governed by the existing
pref(s). We can reuse the generic foreground colour for the caret also.
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
