Tue, Dec 11
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.
Sat, Dec 8
It started happening with me right around Firefox 60 also. 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.
Fri, Dec 7
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:
Thu, Dec 6
W3schools points out that progress bars should use <progress>, not <meter>. A better use of <meter> would be for Template:Rating.
Wed, Dec 5
I know @TheDJ has poked around here. I'm pretty sure I've seen a task for this elsewhere (not just for Timeless).
Tue, Dec 4
- 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?
Mon, Dec 3
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.
Sat, Dec 1
Fri, Nov 30
Invalid with T165189: "→" link to page section on History page can be hard to click, should be larger somehow I think. 😃
Tue, Nov 27
Mon, Nov 19
Yeah, this is not likely to be changed. Use syntaxhighlight with lang=moin and inline if you want this behavior.
Wed, Nov 14
Nov 14 2018
Are there any wikis where it makes sense for NEWSECTIONLINK to work in mainspace that shouldn't instead be configured in the wiki configuration for global new section links?
Nov 13 2018
Nov 11 2018
Nov 8 2018
Sticking our heads in the sand and declaring that the current svg render is already perfect (when it manifestly is not) does not advance that cause.
Nov 7 2018
Nov 6 2018
Related task over at T8089: Section edit button shows up for transcluded protected page (also not the same).
Well, found a duplicate just above; T15079: no edit links for transcluded sections on protected pages is similar but not the same.
Not quite the same as T11394: Section "view source" on protected pages but figured I'd relate them in the comments.
Nov 5 2018
This is either a duplicate of T92432: Come up with a better way to auto-label references or of T52568: VisualEditor: Be able to name references manually in the reference dialog.
Nov 4 2018
This seems like a bad idea. Render modes would spread into the wild, which makes it harder to use math everywhere else and get expected results according to user preference.
Nov 3 2018
I've narrowed the scope for the request to annotations per the last comment by the ticket author.
Just want to link T155732: Provide a Preview panel that doesn't obscure the wikitext box and maybe the skin's sidebar (?) and T153306: Have Show preview and Review your changes more directly accessible in the New Wikitext Editor here as relevant.
Oct 30 2018
I see the insect as the 4th result in Google in a private tab on Firefox.