On 1 October 2014 08:17, Ryan Schmidt skizzerz@gmail.com wrote:
The idea of <sig> seems fine to me as a way to semantically designate signatures, however I'd like to caution against using a <span> in the expanded text, as while it may not be an issue with WMF wikis, some third-party wikis format signatures like you would in a forum (in that there is a signature "block" underneath the post, alas I cannot find that wiki again so no example), and these signatures can contain block-level elements. Rendering to a <span> may break that style of discussion, perhaps we can instead render to a <div> and set display: inline for it in the default css. Then a wiki could override this to move it wherever or display it as a block if they so choose.
Another alternative is keep the span, but add a hook to allow extensions to fully modify the output (including changing the span to something else), that way we can keep the sig semantically valid for the 99.99% of them that are actually used inline.
Or, more simply, span.sig { display: block; } in your site CSS, rather than putting the burden on, as you put it, the "99.99%"… :-)
J.