I feel the situation was a lot different back in 2013. It's 2020. We are not talking about XHTML any more. We use HTML 5, a "living standard". At this point, is this an academic discussion about the semantics of HTML, or does this have real-life consequences? If so, in which browsers? Is there a specific example we can look at? (Ideally with a revision ID and screenshot.)
Mon, Jan 20
On WMF wikis this can also be done with Petscan, on an aside.
This can be worked around by accessing ?action=delete directly, I would believe.
Tue, Jan 14
I don't know. It just seems bizarre that something we wanted 4 years ago apparently is no longer wanted, and no circumstances related to the original work have changed. :) I would expect that as part of the Vector rework we'll get to a responsive mode again, but maybe that's not an explicit requirement of that work? (I am fairly certain that is an objective/requirement.)
Probably shouldn't do this...
Mon, Jan 13
I have removed the reference to "including themselves" per the other work to remove self-unblocks generally.
I believe this is T208965: Partially blocked admins should be able to access Special:Block. Please feel free to merge.
Sun, Jan 12
Sat, Jan 11
Thu, Jan 9
Wed, Jan 8
I honestly see the implementation of citation content (and other extensions) in Parsoid as technical debt to be cleaned up/removed eventually by the 1-parser-march. @ssastry should probably comment on the general plan for those extension reimplementations, if that has been considered previously (and if not, maybe it should be discussed somewhere more general).
The linked task says that @Cyberpower678 has access now.
Tue, Jan 7
Mon, Jan 6
Sun, Jan 5
Sat, Jan 4
Thu, Jan 2
Tue, Dec 31
Dec 21 2019
Dec 20 2019
On WMF wikis, [[Special:Search/insource:extends]] would probably do to start.
Dec 19 2019
Dec 18 2019
Dec 13 2019
I left this comment on the Promises task; not sure if it might be better suited for here.
IE11 is still some 3% of total views (7.6% of desktop) and is presently the only MS browser available on Win7 (mind you, an OS basically EOL in a month) and Win8. (Chromium Edge supports both but will be released more-or-less with the end of support for Win7; how it will end up on users's computers for Win7 when they won't be receiving updates, I do not know (voluntary download? for people using IE11...).)
We see behavior similar to this on-wiki today on occasion, where one person's edit obliterates someone who made a comment just before (and occasionally it is a longer time period--I think that is usually due to users who start an edit long before and then come back to finish it after someone else as made a comment in the same space, which for some reason the edit conflicter won't catch). I can't point to any diffs offhand.
Dec 11 2019
I think silent failure, or using something other than class=error, might be preferable here if it's the case, and I already suggested it will be, the community will want support for such. I'd rather field questions of "why doesn't it work?" than "there's a big red error for something that should work". One might reasonably make a category for it though, without the red error.
Dec 10 2019
Okay, that's what I thought.
Dec 8 2019
Dec 5 2019
See also T104926: Remove the old wikitext styling code from Cite and children tasks, and maybe also T156350: Add language-specific CSS modules for Parsoid's Cite output and children. I suspect @Jdforrester-WMF and possibly @ssastry will have some commentary about numbering.
Dec 4 2019
Is this comment based on the beta feature for hover tooltips, the now-common gadget for the same, or some other hover?