# Today

• Clear sailing ahead.

# Tomorrow

• Clear sailing ahead.

# Tuesday

• Clear sailing ahead.

# User Details

User Since
Apr 9 2015, 4:16 PM (153 w, 3 d)
Availability
Available
IRC Nick
Sky2042
LDAP User
Unknown
MediaWiki User
Izno

# Fri, Mar 2

Phabricator is for changes either to the MediaWiki software or configuration changes for the Wikimedia community.

# Fri, Feb 23

Izno added a comment to T124168: Show Navbox templates in mobile skins.

I'm going to float an idea here to see about technical feasibility of a sketched idea (or maybe to spark a similar idea--maybe with Lua tables instead). (TheDJ's comments above are pretty cool idea too I think.)

# Tue, Feb 20

In general,

xxx<tag>  inside  </tag>yyyy

should be treated as

xxx <tag>inside</tag> yyyy

# Feb 16 2018

Izno moved T72424: Set \$wgUseMediaWikiUIEverywhere = true from Goal to Other completed tasks on the Tracking board.
Izno moved T73181: [Tracking] MobileFrontend should use mw-ui-icon from Goal to Other completed tasks on the Tracking board.
Izno moved T74713: Get OOUI PHP to be good to go from Goal to Other completed tasks on the Tracking board.
Izno moved T12542: CLI setup script (tracking) from Goal to Other completed tasks on the Tracking board.
Izno moved T21288: Gadget usage statistics from Goal to Other completed tasks on the Tracking board.
Izno moved T37707: Complete unification of all accounts to SUL from Epic to Other completed tasks on the Tracking board.

# Feb 9 2018

And that foreign article needs to link to both English articles. Wikidata's faulty insistence on 1-to-1 realtionships causes problems for both editors and readers.

Thought of a technical solution, might as well throw it out there:

# Feb 6 2018

Either way, I think we should decline this and suggest filer take up the question at [[Mediawiki:Mobile.css]].

Izno added a comment to T183704: class="wikitable plainrowheaders" does not work in mobile.

no, minerva.css

# Feb 2 2018

I thought it might be going to the site default rather than auto-correcting.

Izno added a comment to T185840: AWB shouldn't strip <em>.

Please link to MOS or policy pages to show that this is recommended/preferred behaviour, as I would not want to make a change just because it is your own preference or idea.

# Jan 31 2018

Izno added a comment to T152821: Linter: check for <a> tags (checkwiki #4).

More generally, we should probably lint for any tag which is not on the whitelist. <img> is another.

# Jan 30 2018

Izno closed T177146: Compatibility with Internet Explorer (even IE 11) as Invalid.

I'm just going to decline this since it's not at all obvious what is actionable with this task (and IE11 is indeed functioning).

# Jan 25 2018

Yes, I think it's related to the mixed use of {{dts}} and non-dts dates, as I successfully caused the 2010s table to sort after removal.

Try as a start making sure every date cell either has {{dts}} or does not
have {{dts}}.

# Jan 22 2018

I'm using whatever is the default.

Are you using WTE2017?

# Jan 20 2018

Izno updated the task description for T36912: Add string distance function to AbuseFilter.

# Jan 19 2018

Izno added a comment to T173943: Display count of remaining content space errors.

Change 405327 had a related patch set uploaded (by Subramanya Sastry; owner: Subramanya Sastry):
[mediawiki/extensions/Linter@master] WIP: Display count of linter errors in the main namespace

https://gerrit.wikimedia.org/r/405327

Izno updated the task description for T185331: Sister project search results pushed to bottom.
Izno added a comment to T185279: Linter isn't highlighting text in 2017 WTE anymore.

This might be a Timeless thing too/instead; I haven't check vector.

Izno added a comment to T184706: Badly introduced inline references do not throw a warning.

Yeah, this is more a thing for CHECKWIKI or for Linter, not for Cite. (I have no issue keeping it on the cite board.)

it's typically a mistake

IMO you should remove the small tags, or move them inside the block items as desired. (The latter can be botted by an enterprising editor.)

Izno updated the task description for T185283: Timeless and OOUI on Special:Search aren't friendly.
Izno updated subscribers of T140358: HTML self closed tag misparsed on markup font design.

This is a problem with the citation templates, not the parser, but the cleanest fix would be both a fix in the template and in MediaWiki. I left a comment at section Italic lint error of Help talk:CS1. cc @ssastry

# Jan 8 2018

What happens if I try to move a page on en.wp during the downtime? Will Wikidata update later?

# Jan 2 2018

Top alignment makes sense when you have text of uneven but longer sizes, and you want everything to start at the top of the box. Difficulty with finding the first word when supposedly side-by-side paragraphs aren't lined up is a pretty significant usability problem, especially for people with dyslexia and related difficulties, which can make it hard to keep your place on a page.

Izno added a comment to T103276: Provide a way to justify the contents of a table cell.

Yes, I'd rather VE didn't support and encourage the status-quo of using style attributes.

I opposed a similar request at en.wp Common.css for a generic "top align all the things!" class. Why are people setting top alignment? We should have semantic class names so that, across the board we know why we are getting some set of functionality. ("That's just how they do" isn't all that great an answer.)

Izno added a comment to T183704: class="wikitable plainrowheaders" does not work in mobile.

@Izno Mediawiki:Mobile.css will apply to any skin run in the mobile domain e.g. http://en.m.wikipedia.org/wiki/MediaWiki:Mobile.css?useskin=vector
use MediaWiki:Minerva.css for the Minerva skin which will also apply in desktop http://en.wikipedia.org/wiki/MediaWiki:Mobile.css?useskin=minerva

# Dec 31 2017

Izno moved T182929: Cite.php on line 786 undefined index from Unsorted backlog to Defect backlog on the Cite board.

CC'ing @MaxSem and @Legoktm mentioned in that commit. (Though I'd personally decline this task.)

# Dec 28 2017

Izno added a comment to T183733: Add a magic word to expose wiki ID.

I'm sure there's a reason for this request, but what is that reason?

IABot makes use of these identifiers to identify which wiki to access. Making use of the magic words will allow me to make the tools easier to access via my global userpage since it can take the user straight to their wiki. I've already tried making use of referrers, but that doesn't always work so there's my reason. I figured this particular magic word shouldn't be too difficult to add and shouldn't be expensive to use.

I've merged the task because the rest of it is invalid. The reason the validator complains about the languages is because they are not valid language tags: -pro is not a valid language subtag and simple is not a valid language tag.

Izno added a comment to T183733: Add a magic word to expose wiki ID.

I'm sure there's a reason for this request, but what is that reason?

Izno updated subscribers of T183704: class="wikitable plainrowheaders" does not work in mobile.

This is not a code-in task.

Izno added a comment to T183720: Avoid or minimise impact of "unready" Grade A state .

This problem manifests on changes lists with the beta filters option (possibly specific to ORES/Wikidata changes/enhanced RC/WL).

Izno added a comment to T176445: Systematically test load speeds of Watchlist and Recent Changes.

50 changes is not very realistic for RC, especially if you are using the enhanced RC/WL Javascript collapsing.

Just for documentation's sake, this ended AutoWikiBrowser on XP (ref request for help at en.wp). Users will either need to upgrade their Windows operating system or attempt to run it on Linux or Mac to use AWB on Wikimedia wikis.

# Dec 26 2017

The main issue described in this task is a duplicate of T6521: Colon (:) & semicolon (;) shouldn't output as HTML definition list when used for indentation, boldfacing. Is the other item an actual issue or should this be closed duplicate?

# Dec 20 2017

I wonder if it makes sense/is possible to add a JavaScript method which allows a skin agnostic location for portlet manipulation and then let the JavaScript loaded with the skin figure out where to place the links. Otherwise this is going to be an issue every time a new skin comes along with not-quite-the-same-IDs/classes.