https://bugzilla.wikimedia.org/show_bug.cgi?id=45757
--- Comment #2 from ShoeMaker <[email protected]> --- (In reply to comment #1) > (In reply to comment #0) > > # Allow superscript and subscript (checked by default) > There are plenty of legitimate uses for these, so I don't see the point of > adding yet another user option. > > > # Allow text shadowing (unchecked by default) > > # Allow text scrolling (unchecked by default) > > # Allow text blinking (unchecked by default) > Possibly, though once the specific CSS properties are identified, they could > certainly be overridden using user CSS. Again, no change to core MediaWiki is > required for this. It would not be difficult to implement a !locked in the skin style sheets that works in a way similar to how !important use to work in CSS1. > > # Allow unicode characters (unchecked by default) > This has nothing to do with CSS, and at least the seemingly obvious solution > of stripping all characters above U+007F would be unusable on most non-English > wikis. Also, some English words (e.g. résumé), as well as IPA pronunciations, > contain (or can contain) such characters. My concern with these characters are the ones that don't render and leave horrible little squares with a number inside of them. If a list could be made of what unicode characters do load with what browsers on what operating systems, then the "problem" characters could be easily removed. > > # Allow text/background contrast greater than 7:1 (unchecked by default) > > This one could also offer a drop-down selection to change the ratio > This is ridiculous. Black text on a white background is 21:1 contrast, > according to http://juicystudio.com/services/luminositycontrastratio.php . > And it's not something that's easy to analyze on the server. I apologize, I was not clear. What I meant was LESS than 7:1. I want more readability and uses of #FCFCFC characters on a #FFFFFF background are highly annoying and disruptive. > > # Allow animation in *.gif images > Theoretically, it should be simple and quick to remove everything but the > first frame on the fly. However, the current image serving architecture likely > would require storing a separate thumbnail of each animated GIF on the server, > which would consume additional disk space. I've seen this done on other sites with no extra disk space being used or exceptional processing load time added (it actually made the page load faster), and I would be happy to research and post what I find as to how they did it. > > Drop-down range for minimum and maximum font size in regular text > > I would start it at 9pt minimum and 16pt maximum. > > Allow the minimum size to go as small as 6pt. > > Allow the maximum size to go as large as 36pt? > This is really the only part that might make sense, although in my > understanding, anyone using such an option would not benefit from the parser > cache (as in waiting 30 seconds for the Barack Obama article to load). The key words here are "in regular text". By this I meant all headings excluded. I don't see this as difficult or an issue. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
