Feb 12 2020
I would support Linter errors being provided via Hidden categories, based on error and namespace..
Was this issue ever resolved? (I'm looking through my old tickets to see if any still open can be closed.)
Addendum as of 2019: TemplateStyles allowed for the approach suggested by Technical13 to be implemented.
Feb 11 2020
Closing as undiagnosable. No evidence available to work from.
Feb 5 2020
The current authority reference template uses named sections, but LDR looks to be partially like what I had in mind.
See also T49544,
<p> ... </p>
Feb 3 2020
In response to csott-
Jan 27 2020
Not breaking existing handling, which would affect many many wikis (not just English Wikisource) is something I can understand the technical reasoning for.
If in respect of Wikipedia the non-provision is intended then I can see the reasoning.. In which case alternative functionality should be provided as not will wikis are Wikipedia.
Jan 26 2020
Adding a trace (London, UK)
Dec 11 2019
Ideally, the status of individual revisions, and a status "change" indication should be different tags or properties.
Sep 10 2019
Isn't the number placement, a function of the localized page numbering script (as in not part of the extension)?
Sep 7 2019
In response to Inzo, if this is a bug, it's essentially a 'false-positive' detection glitch.
Aug 16 2019
https://en.wikisource.org/wiki/User:ShakespeareFan00/foo/testcases My set of test cases for some experimental template code I wrote.
Jul 17 2019
In simple cases, expanded the whole thing to wikitext would be the intended approach..
See also T162375, which was a request for an explict way to indicate null values..
Re-opening as it relates to T196440
Jul 13 2019
Marking this as an 'Annoyance' type task in the heading, given that the issue noted can be carefully worked around, as indicated. It would be nice not to have to use the work-around in the future though, with a more robust parser being able to know it inside the <span> still and act accordingly.
Aklapper, Is this and T226395 the same issue?
See also T57674
Another example of where wrapping references in a span is not a good thing-
Jul 11 2019
In respect of the discussion at English Wikisource this is also slightly related to: T226395
Jul 10 2019
Keep the existing functionality and have <footnote> <footnote follow=> </footnote> instead to handle the block level cases?
Jul 8 2019
(Opps! must have hit save by mistake, added an initial discussion)
Jul 3 2019
Yes. it would , in respect of this the zero length content would be the first param to the "tag" parser function
Jun 24 2019
It relates to the ProofreadPage code base because it's that extension that implments the PAGES tag used in the example given.
Jun 23 2019
Jun 21 2019
I will also cross reference https://phabricator.wikimedia.org/T200632 here. Having parameterizeable style sheets in conjunction with per Index works would be immensely powerful, as you could write various generic style sheets, and then tweak them with parameters for individual works instead of having to completely re-write largely identical stylesheets. (Not a priority though).
Some questions / talking points :-
May 6 2019
And for reference the Special:UserLogout changes are related to T25227
Closing as invalid, it's a script error or a script that was written for an earlier version of Special:UserLogout.
Mar 18 2019
Feb 23 2019
The observered behaviour is a limitation of the browser, not in Mediawiki. Support for proper dropinitials will have to wait until CSS4.
Feb 18 2019
Apparently resovled, as I am no longer seeing this issue..
Feb 17 2019
For reference the code for aligned table is at :
The relevant page was eventually repaired by someone else
Feb 11 2019
Not unexpected but - https://en.wikisource.org/wiki/User:ShakespeareFan00/Ruffhead displays the intended drop-capital, albiet vertically displayed, which suggests something additional is being applied to the styles used in Page namespace.
Feb 8 2019
Jan 28 2019
Closing as Documentation concern.
It wasn't in the help specifically on English Wikisource, so I updated the advice:
The original example in this was temporarily repaired using the suggested work-around, see https://en.wikisource.org/wiki/The_Return_of_Sherlock_Holmes,_1905_edition/Chapter_3 for an example of where the reported issue now arises.
Re-opening because I still consider this a bug. Whilst the work-around suggested, is indeed a reasonable "temporary" solution, it doesn't fully resolve the issue. It is not unreasonable for the transclusion functionality /page numbering script to recognize an entirely blank page and suppress or amend display of numbering which would overlap, without having to explicitly make use of excludes.