https://bugzilla.wikimedia.org/show_bug.cgi?id=26470

Krinkle <krinklem...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |krinklem...@gmail.com

--- Comment #8 from Krinkle <krinklem...@gmail.com> 2011-02-03 01:02:49 UTC ---
(In reply to comment #7)
> Instead of JavaScript, how about a pure css solution, changing the background
> to checkered on hover? That'd be cleaner, simpler and make the verification of
> background transparency even faster than clicking a toggle link/button.

Not bad at all, but when manually scanning a category or gallery page, having
to hover each to see if and how an image is transparent would not be very user
friendly.

I'd suggest making a preference dropdown:
* Apply checkered background on hover [CSS :hover { background } ]
* Don't apply checkered backgrounds []
* Apply checkered backgrounds by default [CSS { background} ]

Still no javascript required. and a small bit of css is added/removed (the same
way the css for stub articles is dynamically loaded in a special way).

Alternatively, if this would fragment cache (not sure if it does, I don't
expect it will) - we could opt for a pseudo-javascript implementation, in which
the preference is set and can be retrieved via javascript (
mw.user.options.get('checkedbackground') ), and then css can be added on-load
by a core module (ie. mediawiki.js or mediwiki.util.js)

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to