or something? [20:47:53] yep, that'll work fine [20:48:10] ok cool... are there any guidelines on this? I just don't want to mess up regular html rendering [20:48:15] I will test obviously [20:48:32] and I don't particularly _want_ to change font family but we have text in multiple scripts (alphabets) and one font won't work for all [20:49:18] I assume you're doing something other than just wrapping in a div to actually merit making it an extension [20:49:30] technically, div is not allowed in certain contexts [20:49:36] Skizzerz: how else can I do it? [20:49:41] not sure if realistically there's a better approach though [20:49:44] a regular mediawiki template [20:50:00] and most browsers probably ignore errors like that anyway [20:50:01]

is allowed in normal wikitext [20:50:19] Skizzerz: yes, but then I'd have to do like {{foo|text goes here}} and wouldn't that be kind of ugly if the text has multiple paragraphs etc? [20:50:34] HTML phrasing context, I mean [20:50:46] an alternative is {{foo begin}}text goes here{{foo end}} [20:51:00] but that has downsides as well [20:51:05] Skizzerz: oh really? huh, well I looked at docs yesterday and didn't find anything like that [20:51:13] and asked here but no one answered :P [20:51:35] it isn't at https://www.mediawiki.org/wiki/Help:Templates [20:51:56] (note: that's two separate templates. One named [[Template:Foo begin]] that just has the opening div, and one named [[Template:Foo end]] that just has the closing div) [20:52:05] ohh [20:52:08] got it [20:52:24] yeah, I suspect we'll want a little more certainty and logic to this [20:52:29] I dunno, I will think about it [20:53:01] if you go the template route, put the css in [[MediaWiki:Common.css]]. If you go the extension route, you'll probably be looking at injecting the css via ResourceLoader [20:53:20] yes, good point [20:53:33] I'll also note that don't support wiki markup inside of them, only {{#parserfunctions:}} support markup [20:54:05] (you can parse markup inside of a tag extension, but you're on your own to do so in your extension code; the software isn't going to do it for you) [20:54:33] ok, good to know [20:55:04] what else happens to the text input? I noticed that in example tag extensions there is htmlspecialchars($input) [20:55:16] by default? Nothing [20:55:24] so it doesn't apply html entities either, apparently? [20:55:34] the reason htmlspecialchars() is there in examples is because the output of tag extensions is treated as raw HTML and sent directly to the end user [20:55:35] I assume likewise for, say, two newlines, it won't insert

or whatever [20:55:58] correct; the software doesn't touch your extension's output. [20:56:22] also, the things that look like html attributes seem to be passed in as tag attributes but they are just for the code to use and interpret [20:56:31] since it is a custom tag after all [20:56:32] (htmlspecialchars is therefore needed to avoid security vulnerabilities such as XSS when emitting user-generated content) [20:57:00] both the attributes and content are 100% up to your extension to interpret however you want [20:57:19] for example, https://www.mediawiki.org/wiki/Extension:InputBox#Wiki_code [20:57:33] Skizzerz: what mediawiki function would I call to convert mediawiki markup to html in the normal way (as if there were no tag extension)? [20:58:02] you'd need to obtain a Parser object instance and call the parse method on it, passing in the text you want parsed [20:58:11] like if I wanted a noop tag extension, so ..... and act as if there were no foo tag [20:58:14] ok [20:58:19] I am just going to use that as a starting point [20:58:30] I'll also consider the template route, I am not sure yet what will make most sense [20:58:31] example is at https://www.mediawiki.org/wiki/Manual:Tag_extensions#Since_version_1.16 [20:58:34] thanks [20:59:05] yes, I found the api, I actually have a working one -- well, working meaning it runs, not that I know how to tweak most of this yet [20:59:46] looks like basically you just return a text string and that's the html output [21:00:01] most of my fears here are too much magic behind the scenes and it looks like it's the opposite :) [21:32:58] I am testing using the resource loader now. I added a hook to BeforePageDisplay where I call $outputPage->addModules('foo') [21:33:32] the module name shows up in the