https://bugzilla.wikimedia.org/show_bug.cgi?id=24529
--- Comment #3 from Aryeh Gregor <simetrical+wikib...@gmail.com> 2010-07-25
20:17:24 UTC ---
(In reply to comment #2)
> The tt element and other simple cases can be fixed in the wikicode with AWB
> and
> other scripting tools and bots, after being fixed in engine to not actually
> reach the user agent as a tt element, but a span with monospaced font. On
> installations other than Wikipedia, they'll need to write their own (or adapt
> WP's) tools, or fix it manually.
If people step up who are willing and able to fix all the breakage, I don't
mind disabling support in the software. But not before all existing uses are
removed, and people commit to fixing any stragglers.
> I'm not sure that allowing the tt element in the wikicode is a huge deal. We
> also allow br elements without a closing / in them
Which is allowed in HTML5.
> we allow the p element without a closing /p tag
Which is allowed in HTML5.
> I think that tt should be removed from the editor-facing
> documentation, so that new instances of it are not added to the wikicode,
> willynilly, forever. The help pages on editing should direct users to a
> {{monospace}} template or something (which would use the span and
> font-family).
I agree, but of course, this isn't the right place to ask. It's a wiki, change
it. :) (Or get consensus, whatever.)
> For HTML5-verboten attributes... Yeah, that'll be big fun. I don't have any
> particular ideas with regard to table stuff especially.
That's much harder, yeah. Of course, it wouldn't be a big deal if people would
just not use presentational tables, but good luck with that one . . .
--
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
