SMcCandlish (Stanton McCandlish)
User

Projects

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Wednesday

  • Clear sailing ahead.

User Details

User Since
Sep 8 2015, 11:54 AM (148 w, 5 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
SMcCandlish [ Global Accounts ]

Recent Activity

Tue, Jul 10

SMcCandlish updated the task description for T199175: wikipedialibrary.wmflabs.org/about needs an update.
Tue, Jul 10, 6:19 AM · Library-Card-Platform
SMcCandlish added a comment to T199175: wikipedialibrary.wmflabs.org/about needs an update.

At a discussion over on Meta, someone (Xover) has suggested that the details of this example should be replaced: "Labor History is also a poor example to use for this (cf. the recent VPP discussion) as it's actually published by T&F and so the |via= parameter is of questionable value there. It would be better to use an example from JSTOR or Project MUSE ... Since these to a much larger degree are pure archive services (Project MUSE is run by Johns Hopkins, and some journals are published by Johns Hopkins University Press, but they also have a lot of journals published by others. JSTOR doesn't publish any journals themselves.)" Such an example would be this:

Tue, Jul 10, 6:18 AM · Library-Card-Platform
SMcCandlish created T199175: wikipedialibrary.wmflabs.org/about needs an update.
Tue, Jul 10, 2:43 AM · Library-Card-Platform

Mon, Jul 9

SMcCandlish added a comment to T196812: Make PolyGerrit the default ui.

Do pre-existing users need to do anything to turn this on?

Mon, Jul 9, 11:26 PM · User-notice, Release-Engineering-Team, Patch-For-Review, Gerrit

Mon, Jun 25

SMcCandlish created T198095: CSS not being parsed properly for spacing or for complex decimal values.
Mon, Jun 25, 1:04 PM · SyntaxHighlight

Jun 15 2018

SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

Re: "I can't find a smccandlish or mech user in gerrit. Is there another name I should be looking for?"

Jun 15 2018, 2:56 AM · Gerrit, LDAP, Phabricator

Jun 11 2018

SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

If it comes down to it, I'm okay with nuking SMcCandlish, smccandlish, and mech on all three systems, so I can create a new, "clean" SMcCandlish on them (provides there's no mech on either of the other two that isn't me; I'm pretty sure the only WMF site I ever used that on, by accident, was Phab). However, I do use SUL's single account across most WMF servers, as SMcCandlish, and I don't know if that complicates things.

Jun 11 2018, 8:12 PM · Gerrit, LDAP, Phabricator
SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

Tried that, and it's not working. I'm logged into wikitech as SMcCandlish and login attempts at Gerrit as smccandlish (or SMcCandlish, either way) do not work with the same password (or any other I can think of).

Jun 11 2018, 4:02 AM · Gerrit, LDAP, Phabricator

Jun 4 2018

SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

Update: I can login to Phabricator by one but not both of the available methods. I can login to Wikitech, but I cannot login to Gerrit, despite the fact that https://wikitech.wikimedia.org/wiki/Gerrit says that our Wikitech login ID/PW automatically become those for Gerrit. These issues (for me, and I think for a few others) seem to date back to the timespan when the Toolserver was being retired in favor of Phabricator, and the SUL system was being deployed. In my case, I already has pre-existing accounts on various WMF sites, but not all that many, when I created my SUL account. Not sure if that relates. As far as I know, I used "SMcCandlish" on all of them (and definitely did at Wikitech and Gerrit), except I created also a "mech" account at Phabricator, out of habit of using that old-time monicker of mine on some other coding-related sites. I now also have and am using SMcCandlish at Phabricator.

Jun 4 2018, 11:26 PM · Gerrit, LDAP, Phabricator
SMcCandlish updated the task description for T187299: User-perceived page load performance study.
Jun 4 2018, 11:07 PM · User-notice, MW-1.32-release-notes (WMF-deploy-2018-05-01 (1.32.0-wmf.2)), Readers-Web-Backlog (Tracking), QuickSurveys, Unplanned-Sprint-Work, Performance-Team
SMcCandlish added a member for Tech-Ambassadors: SMcCandlish.
Jun 4 2018, 10:18 PM

Apr 12 2018

SMcCandlish added a comment to T49544: <references/> list item must not wrap the text in <span>.

Yep.

Apr 12 2018, 12:03 AM · Wikisource, Patch-For-Review, Technical-Debt, Easy, Cite

Jan 18 2018

SMcCandlish created T185222: lists.wikimedia.org reporting "You must GET the form before submitting it" for all list subscription attempts.
Jan 18 2018, 3:45 PM · Wikimedia-Mailing-lists

Dec 25 2017

SMcCandlish added a comment to T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing.

Agreed with TheDJ on all counts, except that it's actually worse. What's happening is that particular and well-organized camps of editors are declaring that they refuse in mainspace to use more accessible markup. They are using talk page habituation to the bad markup as a "reason" to abuse description list code for purely visual layout gimmicks in articles we send to all our readers, and to effectively force all editors to do so (by changing our content guidelines to impose the bad style and to remove any mention of more accessible approaches). This is really, really not okay.

Dec 25 2017, 11:48 PM · Parsoid, Accessibility, MediaWiki-Parser

Dec 22 2017

SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

Yes, mech is me as well. I don't use that ID on any WMF sites any longer.

Dec 22 2017, 11:52 PM · Gerrit, LDAP, Phabricator

Dec 19 2017

SMcCandlish added a comment to T102280: Hovercard could show an extract from the id downward when #IDname links are used.

This is not an "edge case", it's how millions of links are done, and the hovercards can be at least frustrating and often very confusing as a result. The OP's case is a good one, and I encounter the same problem all the time.

Dec 19 2017, 11:13 AM · Readers-Web-Backlog (Design), Design, Page-Previews
SMcCandlish renamed T102280: Hovercard could show an extract from the id downward when #IDname links are used from Hovercard could show extracts of text extract fragments of articles when #section-links are used to Hovercard could show an extract from the id downward when #IDname links are used.
Dec 19 2017, 10:41 AM · Readers-Web-Backlog (Design), Design, Page-Previews

Dec 18 2017

SMcCandlish added a comment to T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing.

@MattFitzpatrick:

  1. The HTML specs say all kinds of things are permissible, but MW doesn't support all of them. That's okay. Heck, there are entire elements MW just ignores.
  2. Your "one-item ul" case won't matter: the in-wiki markup will remain *, and the output will look identical. (If we're concerned someone might be doing something special with style, we can give converted-to-div "list" elements a class they can use to match their list styling; edge case probably no one cares about.)
  3. When someone comes along and actually uses your placeholder "*" to create a real list with 2+ items, then after saving the page, MW will parse it as a list, not as a styled div. Meanwhile, if there is only one * we get the double benefit of a) screen readers no longer being told there's a "list" but finding only one item, and b) same users being told there's a list but there's nothing there at all, just an empty <li>.
  4. <dl role="presentation"> is still going to be invalid without a least one each of <dt> and <dd>, so by all means we should do something like <div class="whatever-dl-pseudo-indent-class">.
Dec 18 2017, 7:09 PM · Parsoid, Accessibility, MediaWiki-Parser

Dec 17 2017

SMcCandlish added a comment to T7718: Block element written inline splits multiline paragraphs.

Would love to see action on this. This block-element issue seems broader than the test cases provided years ago at what is now http://test.wikipedia.org/wiki/Bug_T7718

Dec 17 2017, 4:04 AM · MediaWiki-Parser
SMcCandlish raised the priority of T7718: Block element written inline splits multiline paragraphs from Low to Normal.
Dec 17 2017, 3:58 AM · MediaWiki-Parser

Dec 15 2017

SMcCandlish added a comment to T177923: How to measure "Wiki projects requesting beta features and other early deployments".

On to some more political and PR matters:

Dec 15 2017, 9:29 PM · Community-Relations
SMcCandlish added a comment to T177923: How to measure "Wiki projects requesting beta features and other early deployments".

Aklapper: I think it has to mean making beta features available in mw-prefsection-beta first. Few wikis are comfortable having features rolled out without extensive testing at the wiki in question. This has caused problems before. Three examples I can think of are: date auto-formatting (which also caused auto-linking – this was a huge debate at en.Wikipedia, eventually leading to an ArbCom case); and deployment of Flow as feature-complete and read-to-use, which some wikiprojects at the same site then implemented for their talk pages, which led to similar controversy; and similar issues with Visual Editor. Making VE opt-in at the user level has been key to getting some communities to accept anything about it, and to work with the devs in ironing out problems with it instead of just objecting to it being used at all (new users at a site like en.WP generally don't know it's available, so it is mostly clueful editors who are testing it and finding out what its limitations and flaws are).

Dec 15 2017, 9:27 PM · Community-Relations

Dec 14 2017

SMcCandlish added a comment to T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing.

My much earlier comment mistakenly suggested using a stylzed <span> when I meant <div>; indented "things" often contain block-level markup in them.

Dec 14 2017, 6:45 AM · Parsoid, Accessibility, MediaWiki-Parser

Dec 10 2017

SMcCandlish added a comment to T49544: <references/> list item must not wrap the text in <span>.

This does need to be fixed; people *all the time* use block elements in reference citations, most commonly paragraph breaks and short lists, though I've also encountered reasonable uses of small tables, block quotations, divs that do block indentation of material that is not a direct quotation, and so on. This is not a mistake or bad user behavior, it is editors doing what they need to do in references and non-reference footnotes (which also pass through the <ref> system, with templates (at en.Wikipedia) like {{efn}}, etc.).

Dec 10 2017, 4:21 AM · Wikisource, Patch-For-Review, Technical-Debt, Easy, Cite

Dec 4 2017

SMcCandlish added a comment to T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing.

Just FYI: WMF's failure to fix this simple and obvious bug after over a decade is likely (given where this RfC is going) to result in en.Wikipedia literally PROHIBITING the use of more accessible markup instead of abuse of the <dd> element for visual indentation. This is pretty much an accessibility debacle of stunning proportions, resulting from a combination of editorial ignorance of accessibility and of HTML specs, laziness, and WMF failure to prioritize development. I'm stunned and depressed that it's come to this. I have no idea how an organization with tens of millions of dollars and a dedicated development team with almost all focus on a single software project cannot get it together to fix basic, obvious, and comparatively easy-to-solve problems in its functionality when given over ten years to do it. This should be fixed within this month.

Dec 4 2017, 3:47 AM · Parsoid, Accessibility, MediaWiki-Parser

Oct 1 2017

SMcCandlish created T177182: Spammy notices should go away.
Oct 1 2017, 10:06 PM · Community-consensus-needed, InternetArchiveBot

Sep 23 2017

SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

Can you provide any pointers on how to go about that? I've been trying to resolve this for ages. It's not even multiple user IDs in the "SMcCandlish" or "mmodell" sense, but rather two e-mail addresses which can also be used (in theory) to login with – if I understand correctly. I think it took the "mech" part from one of my e-mail addresses, as I don't recall trying to establish that as an actual user ID on here.

Sep 23 2017, 5:06 PM · Gerrit, LDAP, Phabricator

Sep 14 2017

SMcCandlish added a comment to T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing.

This isn't really true:

Sep 14 2017, 6:53 AM · Parsoid, Accessibility, MediaWiki-Parser
SMcCandlish added a comment to T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing.

I'm not sure why this has gone on for so long without resolution. It seems pretty simple to me:

Sep 14 2017, 6:36 AM · Parsoid, Accessibility, MediaWiki-Parser
SMcCandlish added a comment to T138672: Having difficulty logging into Phabricator via LDAP when multiple accounts returned for username (gerrit: Duplicate users: smccandlish).

This is still affecting me, too (for a couple of years now). The workaround would probably be to delete the "mech" username associated with this ID, and just keep the SMcCandlish one.

Sep 14 2017, 6:14 AM · Gerrit, LDAP, Phabricator

Aug 19 2016

SMcCandlish added a member for Page-Previews: SMcCandlish.
Aug 19 2016, 4:46 PM
SMcCandlish added a comment to T65792: #section-links should preview the correct subsection.

I haven't figured out enough about this system yet (I've barely been able to get into it until recently due to LDAP issues with my account) to know where to start. I assume there's a git or svn repo somewhere. Anyway, not everyone who reports problems here is a programmer. The "this is going to remain on the back burner unless you code up a solution yourself" approach may make sense in, e.g., the GCC compiler development bug tracker over at GNU, but isn't very responsive when it comes to the issue tracker for a system that is mostly used by writers and readers of plain prose. Depending on what language this is written in, I might actually be competent to help, but the average Wikipedian (or user of other wikis) is probably not a coder.

Aug 19 2016, 4:42 PM · Readers-Web-Backlog, Page-Previews, TextExtracts

Aug 5 2016

SMcCandlish added a comment to T65792: #section-links should preview the correct subsection.

Why is this set to "Low" priority? It's been my experience, with a large number of projects, that marking a report/request low-priority means it will most likely never be dealt with. Having the hovercard show the content that the link actually points to, and stop misleading readers, would appear to be a high-priority item.

Aug 5 2016, 1:02 PM · Readers-Web-Backlog, Page-Previews, TextExtracts

Sep 8 2015

SMcCandlish added a comment to T107199: Let users specify TextExtract.

This seems to directly relate: T65792 (start displaying from point of anchor given, not just top of page, and allow this to work when on same page as anchor).

Sep 8 2015, 12:24 PM · Readers-Web-Backlog, TextExtracts
SMcCandlish updated subscribers of T107199: Let users specify TextExtract.
Sep 8 2015, 12:22 PM · Readers-Web-Backlog, TextExtracts
SMcCandlish added a comment to T65792: #section-links should preview the correct subsection.

It would be hot if the hovercard, or a template-triggerable variant of it, could start showing content starting at the specific anchor used in the link. If this were combined with the ability to trigger it for links on the same page, not just to different pages, this would be insanely great for glossaries (see https://en.wikipedia.org/wiki/MOS:GLOSSARIES and Wiktionary has them, too). For an example, see https://en.wikipedia.org/wiki/Glossary_of_cue_sports_terms]]. The zillion intra-glossary links in that could just pop up the definition in question (as could similar glossary links at articles like https://en.wikipedia.org/wiki/Eight-ball that link to this glossary), instead of the current practices, which are just a tooltip saying what entry it goes to (generated by the https://en.wikipedia.org/wiki/Template:Glossary_link tag) and, in the present hovercard, the top of the glossary's article page, if you are on a different page than the glossary itself. Many articles have embedded glossaries, too; they're not all in separate articles.

Sep 8 2015, 12:19 PM · Readers-Web-Backlog, Page-Previews, TextExtracts