Using display: none to enforce semantics is bad. It
will then show up
for many cell phone users, old screen readers, Lynx, etc.
I concur. Even modern feed aggregators will ignore CSS (even inline
style="" directives).
The comment was probably a better idea, although
unfortunately still
rather hacky.
Yeah it's hacky - I can't argue with that - but it's the only way I know of
to deal with all three of the following:
1) HTML comments found in wikitext are stripped (we get around this by using
an extension tag)
2) Whitespaces in extension output are converted to <br> and <p> tags (we
get around this by putting it in an HTML comment)
3) Malicious users could prematurely end the comment by putting "-->" in the
keyword text followed by <script> or any other HTML markup (we avoid this by
base64 encoding all input and only decoding it during the meta parsing
step).
If there's a better way to achieve this, I'm open to suggestions. I've been
using this technique on extensions I've been developing since I haven't yet
found a better way. But seriously, if there /is/ a cleaner way to do this
I'd love to know about it :)
On 2/27/07, Simetrical <Simetrical+wikilist(a)gmail.com> wrote:
On 2/27/07, Jim Wilson <wilson.jim.r(a)gmail.com> wrote:
3) Add a CSS rule to hide spans of class keyword
(to MediaWiki:
Common.css):
span.keyword { display: none; }
Using display: none to enforce semantics is bad. It will then show up
for many cell phone users, old screen readers, Lynx, etc. The comment
was probably a better idea, although unfortunately still rather hacky.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/wikitech-l