No no! Simple!
* Note that the default mediawiki output is:
<li id="$1"><span
class="mw-cite-backlink">[[#$2|↑]]</span> $3</li>
* Find out where "mw-cite-backlink" is currently defined. (?)
* Suggest changes to that CSS, that will work to make the arrow a
consistently wide number of clickable pixels. (What we want)
* Profit!
On 13-11-15 10:01 AM, Jared Zimmerman wrote:
you mean something like this?
http://blustemy-design.com/blog/drawing-pure-css-arrows-with-less-mixins/
*
*
*
*
*Jared Zimmerman *\\Director of User Experience \\Wikimedia Foundation
M : +1 415 609 4043 | : @JaredZimmerman <https://twitter.com/JaredZimmerman>
On Fri, Nov 15, 2013 at 11:24 PM, Quiddity <pandiculation(a)gmail.com
<mailto:pandiculation@gmail.com>> wrote:
On 13-11-15 05:04 AM, Jared Zimmerman wrote:
The screenreader case seems like even more reason to have it be a
image/button with descriptive alt text rather than relying on what a
particular piece of screen reader software said an extended
character
should represent, since we're using it for something different.
This aspect is already solved, as I pointed out yesterday in
http://lists.wikimedia.org/__pipermail/design/2013-__November/001159.html
<http://lists.wikimedia.org/pipermail/design/2013-November/001159.html>
screenreaders now say "Jump up" no matter what the character is.
There's no problem with the unicode arrow, except that it isn't
reliably/consistently styled cross-browser/platform. I was really
hoping you'd suggest a simple CSS fix.
_________________________________________________
Design mailing list
Design(a)lists.wikimedia.org <mailto:Design@lists.wikimedia.org>
https://lists.wikimedia.org/__mailman/listinfo/design
<https://lists.wikimedia.org/mailman/listinfo/design>
_______________________________________________
Design mailing list
Design(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design