Mon, Mar 18
Sun, Mar 17
We already have a tag for this ( Accessibility ). I would actually recommend this task get closed with new tasks opened for each of the bullets in the original, as appropriate.
Sat, Mar 9
Mon, Mar 4
Okay, I've triaged as lowest. No objection if you want to decline also.
Does that load the json each time you invoke the module on a page though?
Sun, Mar 3
If we wanted still to whitelist an entire domain on a particular Wikipedia (as opposed to the blacklist currently at Meta), that should still be at the MediaWiki version of the page.
Fri, Mar 1
As for completely failing, VE (and the apps which I think load VE/WTE17 these days) doesn't try to work with pathological behavior.
I'm sitting here feeling a bit puzzled about why we should support this (particular) use case with this as the (particular) fix. Imo it's a bit pathological to use nowiki to actually get content like this.
Wed, Feb 27
Feb 17 2019
Feb 11 2019
Seems like a good one for after T122924: Merge Extension:Theme into core.
Feb 10 2019
Module:WikidataIB should already do this I think? @RexxS
Feb 9 2019
I don't think that really fits in with the theme of Timeless though.
It is not visible in the default view for anyone any more in any skin unless you have enabled a script or gadget.
Feb 3 2019
I realize this is a 4 year task... But Firefox works on my Android device (LG G5) with WTE17. It does still have the "unsupported" note in the edit notification pane.
Jan 28 2019
Jan 26 2019
Jan 25 2019
Yeah, I'm probably just a bit grouchy today.
Jan 24 2019
- Note these are restricted to #bodyContent (editor provided content) as these conflict
- with the Minerva skin. Remember .hlist is a class defined in core as well!
- See https://phabricator.wikimedia.org/T213239
Jan 22 2019
Jan 19 2019
Anomie's objections above seem to be rather... uh... interesting.
This is a "it just works" feature to most people.
I'd guess this is T4700.
Jan 18 2019
Jan 16 2019
Jan 8 2019
Jan 3 2019
Dec 25 2018
year and date are synonyms on en.wp.
The en.wp template is intelligent enough not to display it. The problem is that the hu.wp template is not up to date. See also discussion at T156548: Disallow adding Czech language tag (cs-CZ) into citation templates on cswiki and T115326: Many language wiki templates (pl, it, en, cs) don't accept xx-XX style language codes.
Dec 22 2018
Dec 16 2018
The English Wikipedia CS1/2 modules currently support by default what MediaWiki supports (mw.language.fetchLanguageNames). The module will trim to the first 2/3 letter code in language_parameter in the module proper. You can see this by experimenting with an English Wikipedia page that it does accept e.g. nl-NL with an output of "(in Dutch)". There are some overrides listed in lang_name_remap in the configuration file, but that's not directly relevant here.
Dec 11 2018
That's true. But if you mark up your <math> wikitext with <math display=block>, you as the author of a wikitext document are *way* obviously meaning for the math to display as a block. Are you familiar with that functionality? That's what this task is about. Arguing without that context or seemingly without that context seems to miss the point of the task.
Div meets the intent of block math better. It might even be reasonable to mark it up as a paragraph in HTML 5.
Dec 8 2018
It started happening with me right around Firefox 60 also, though I'm on 63.0.3 now and still affected. No issue before then. I mostly experience it with WTE17. It seems to impact the Linter extension also by not loading the linted wikitext, which does not load WTE17 but instead WikiEditor 2010.
Dec 7 2018
On an aside, I don't find the original report compelling for allowing this behavior. That's its own issue (T3584: Need method for multiparagraph list items, continuing numbered lists, and assigning specific numbers to list items especially the first item in the title) and should probably have its own fix. (Which, I may have falsely closed one or another in that duplicate chain....)
I'm going to copy the description from my T202083: First-class wikitext support for ordered list item value:
Dec 6 2018
W3schools points out that progress bars should use <progress>, not <meter>. A better use of <meter> would be for Template:Rating.
Dec 5 2018
I know @TheDJ has poked around here. I'm pretty sure I've seen a task for this elsewhere (not just for Timeless).
Dec 4 2018
- What is the purpose of the arrow? Is it discoverability alone?
- Is that necessary? I don't think so. I don't think the arrow here does any good to serve discoverability, and conflates the discussion ongoing in T125657 anyway.
- Is it only to demarcate "in <section of interest>: <summary>"?
- Is that necessary? I doubt so--clearly there are people who missed the usefulness of the arrow, which inspired the change that set off all this discussion.
- Is it both?
Dec 3 2018
Since the other task is making everything the same gray again, reopen this one.
I actually really like the serif font in these rather than the bold, though it does take some getting used to.