Thanks for merging: Placing the contents of the duplicate bug below as a specifc use case for recursive tags in extensions.
Feature summary (what you would like to be able to do and where):

Or depending on context

"display :table; margin:0 auto;" -

margin:0 auto;

respectively.

That was unexpected. And this assumes the V2 API stays active: -
https://iiif.archive.org/iiif/documentation

I think, but as Inductive load is absent it would need someone to take over the toolforge side of the tool, something I can't do as I wouldn't qualify for dev access.

This is what the authors of spectral.js had to say:-
https://github.com/rvanwijnen/spectral.js/issues/20#issuecomment-2936400683

<center> can be implemented as a 'text-align:center" in CSS on an enclosing DIV, or a CSS class, which is the approach taken on a number of wikis.

Not reproducible , so closing as invalid.

Hmm. Intermittent, It didn't reproduce for me, when I re-examined. Checked the edits and found what appeared to be an unbroken list element. Therefore I am wondering if a 'list' item expansion size limit was hit.

Additionally , The edit page could give PROMINENT warnings about pages with deperecated HTML, "Do you really want to save this page?" ..etc..

Do you have a full list of properties that would need to 'discretised' ? If you have regexp for a potential linter style filter , even better :).

I'm not sure as to the viablity of that, given that there are perhaps many templates on Wikisource that presume the current behaviour.

It's not just the "-" use case, as there are plenty of other duplicates like "img" "plate" that are used in pagelists..

The most recent example of doLevels weirdness...

The idea is that rather than storing massive 1 GB scans on Commons, a mid quality 'readable' PDF/Djvu (of small file size- typically not more than 200MB ) could be for archival purposes, along with an IIIF path through which other projects (especially Wikisource) could obtain higher quality images for transcription purposes. Currently the script I use on English Wikisource (implented in https://en.wikisource.org/wiki/User:Inductiveload/jump_to_file if you wanted to review one approach used) , does something like the above but currently uses a file URL (or IA identfier over a direct IIIF resource path) and at present seems to use a tool-forge(?) hosted script to work out some of what to retrieve. Being able to have the same functionality as a drop in Gadget that could be more widely used would be advantageous for a number of projects. As would being able to give a suitable IIIF path directly so that an archive not currently supported by the current script could be added with minimal changes to the underlying gadget.

Seeing recoveries... No objection to merge on closed bugs.

Can confirm recovery occuring at English Wikisoruce on files mentioned previously, eslewhere.

Also affected : [[c:File:WikiIndaba2024 Working across Wikis.pdf]] and others..

Closing as the situation that lead to the request was solved locally on Wikisource.

See also - T216350 which I thought had been solved.

For reference the HTML generated output -
<div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><dl><dd><style data-mw-deduplicate="TemplateStyles:r14324469">.mw-parser-output .wst-tpl{width:100%;position:relative}.mw-parser-output .wst-tpl-entry-outer{max-width:80%;text-align:left;text-indent:0;padding-left:0}.mw-parser-output .wst-tpl-entry-inner{position:relative;display:inline;text-align:left;padding-right:0.5em;background:white;color:#202122;z-index:1}.mw-parser-output .wst-tpl-pagenum{display:inline;position:absolute;bottom:0px;right:0px;text-align:right;min-width:2em;background:white;color:#202122;z-index:1}</style><div class="wst-tpl"></div></dd></dl>
<div class="wst-tpl-entry-outer"><div class="wst-tpl-entry-inner" style="color:inherit;"><b><span style="font-size: 120%;">Division 1—Short title and commencement</span></b></div></div>
<div class="wst-tpl-pagenum" style="color:inherit;">1</div>

I'm seeing the linter flag up stuff with <section> and <onlyinclude> tags, so the patch whilst welcomed, might need to be further tweaked.

A related glitch..

This may also be happening with <onlyinlcude>..</onlyinclude> tags.
see https://en.wikisource.org/w/index.php?title=Template:Information_field&action=edit&lintid=3152787

Do you have a regexp to find paged with affected constructions? ~~~~

If I do that I get a fostered content warning, but that's apparently due to a different bug

Possiby Related- T369354? I had fixed what I thought was a 'fostered-content' error, only for it turn into a 'missing-tag' error. The tag that is missing, is inside a noinclude.

Work-around exists. and I note that I failed to put the exact revision of the issue in above.

See - https://blog.archive.org/2023/09/18/making-iiif-official-at-the-internet-archive/ it seems the tool supporting this needs a URL change to migrate it over to a new IA service for IIFF

This is also affecting English Wikisource.

Adding LST , as this could also relate to the transclusions done using {{#lst:}} syntax.

It wasn't just the include/exclude param but the from= to= changes as well.

Marking as 'stalled' because the DB schema doesn't currently have a means to quickly determine if a specific revision changed the 'transclusion' map

That was exactly the sort of thing I had in mind as a first step :)
(I would suggest updating it to use a different example image however, The one it's using currently has a complex copyright situation.)

I'm ocassionaly using a tweaked version of a script written by another contributor here- https://en.wikisource.org/wiki/User:ShakespeareFan00/pages.js

An unclosed DIV "within" a list item is to me malformed-syntax.

I found a way to resolve the situation without needing code changes. The original request should be considered as more of a feature request if it needs to be kept open at all. Further discussion seems to be in the RFC for balanced templates anyway.

https://github.com/psb1558/Junicode-font/releases/tag/v2.000

Marking this as stalled, until there is another "stable" release of Junicode.

The JuniusX name was dropped:-

Another 'filter' that I think might be useful is specific to a Wikisource use case:-

In T334606#8781169, @TheDJ wrote:

There is another ticket discussing mapping triple ` to syntaxhighlighting, which I think is a much better idea honestly. It matches expectations that people have of other wiki link languages such as markdown, it's short, not language specific and unlikely to conflict with existing wiki text. The inline variant with ` might be a bit more difficult to introduce, but worth an investigation.

However, adding wikisyntax is difficult, especially if that syntax has to map to an extension (I don't think we have anything like that right now).