User Details
- User Since
- Oct 27 2014, 6:03 PM (490 w, 14 h)
- Availability
- Available
- IRC Nick
- edsanders
- LDAP User
- Esanders
- MediaWiki User
- ESanders (WMF) [ Global Accounts ]
Yesterday
The above patch uses the same variable as used in the other popup/dropdown menus (@font-size-dropdown). Presumably this will get migrated to the small/standard/large CSS variables when that switch happens.
Sat, Mar 16
given our plans for changing the font size,
Fri, Mar 15
Thu, Mar 14
See this commit message for why @Catrope left in "undelete" (and therefore "delete"): https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Flow/+/415514
After:
Also the font size should be 14px (for now): https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/1011166
To make tests more resilient in general we should:
- Avoid looking for specific i18n messages
- Add some CSS classes judiciously to make our selectors less fragile, e.g. by helping us avoid nth child selectors
There's a rule in CodeMirror (written by myself 5 years ago) that gives the toolbar a z-index of 7, so this is only broken when CodeMirror is not installed.
Wed, Mar 13
This doesn't appear to happen consistently for me locally:
We don't have these transaction types anymore.
The same applies to ToggleButton (codex) vs ToggleButtonWidget (OOUI)
Tue, Mar 12
We want to avoid enabling VE on namespaces which contain discussions, such as the page you linked to (VE does not handle the indentation used in discussions very well). Are most pages in the Wikipedia: namespace on your wiki non-discussion content?
Sun, Mar 10
The easier fix here is to avoid level 2 headings unless you are starting a new discussion , e.g. by using level 3 instead
Thu, Mar 7
I also note that Citoid expands the shortened URL to youtube.com, which is allowed - but we do our validation on the inputted URL.
The error message you get in the save dialog is a lot more verbose, and includes information about not using URL shorteners:
Wed, Mar 6
Will we prioritize making permalinks more discoverable at this time?
The code checks if the prefix is ctype_alpha in PHP. The check for generating the links doesn't include the ctype_alpha check.
Tue, Mar 5
It'd be pretty easy to hook into the same code that's highlighting permalinked comments and log to that schema from there, if we want to track usage, too.
This was a Codex regression, as the icon went from having padding to having margin.
Note that this doesn't measure if the permalink is used. We could perhaps track on-wiki usage by looking for #c- or #h- in wikitext diffs, but not off-wiki use:
https://en.wikipedia.org/w/index.php?search=insource%3A%2F%5C%23c%5C-%2F&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns1=1&ns2=1&ns3=1&ns4=1&ns5=1&ns6=1&ns7=1&ns8=1&ns9=1&ns10=1&ns11=1&ns12=1&ns13=1&ns14=1&ns15=1&ns100=1&ns101=1&ns118=1&ns119=1&ns710=1&ns711=1&ns828=1&ns829=1
Given the age of those issues we shouldn't expect them to be fixed any time soon.
Anything that generates block level HTML should be disallowed in a signature, if not automatically by our signature validator, then by policy.
Mon, Mar 4
The initial API has been implemented, it returns "blocked" or "allowed" for a given URL based on MediaWiki:Spam-blacklist and MediaWiki:BlockedExternalDomains.json.
See also T262093.
I think T262093 would help with the infobox issue.
Sat, Mar 2
Fri, Mar 1
I'm not sure this needs a tech news announcement, but if you want:
Usability improvements to the "Add a citation" workflow: Moved the "Insert" button to the popup header.
Thu, Feb 29
The highlighter is for formatting SQL syntax only, not an interactive SQL command prompt. Such a request could be made upstream.
Wed, Feb 28
Note that there are existing selenium-webdriver test in VE-MW (in tests/selenium and build/screenshots.js), and some existing infrastructure (the wdio-mediawiki package). If there are good reasons to use another platform (the patch above uses cypress), then the case for that should be documented and a plan made to make sure all VE browser tests use the same technology, where possible, to reduce maintenance burden.
Tue, Feb 27
oldpassword seems unused since https://gerrit.wikimedia.org/r/c/mediawiki/core/+/280945
Mon, Feb 26
On the subject of inverting colours, it is worth noting that while we try to uninvert colours of photographs with mw-no-invert, due to the way CSS hue transforms are calculated this always results in some distortion of the colours[1][2]. While this is subtle and acceptable for photographs, it is not really acceptable for instances where the colour is the information, e.g. on https://en.wikipedia.org/wiki/Pantone#Color_of_the_Year:
Sun, Feb 25
If it isn't toolbar hacks causing it, we could just reset the page scroll to 0 while full screen dialogs are open.
Interestingly, this only happens when the page beneath the dialog is *not* scrolled to the top, so I suspect some of our scrolling hacks for the page toolbar are kicking in in dialog mode, which might be a simple fix...
Fri, Feb 23
We could probably be more vandalism resistant by limiting the number of new topics we detect per edit. Although there may be legitimate case where this happens, e.g. a handful of discussions being moved to a more relevant page.
It just depends which edge case you want to design for...
Thu, Feb 22
+1 unless @nayoub disagrees
This issue only appears to affect Chrome. Firefox works fine.
Real world example of full screen dialogs is the kartographer extension:
https://en.wikipedia.org/wiki/Golden_Gate_Bridge#/map/0
Mon, Feb 19
As noted above, topic permalinks, which begin #h- are already implemented and work, they just aren't exposed in the UI anywhere:
Reason: to start [i], the user experience for generating a permanent link to a comment and topic will be one and the same...
Feb 13 2024
In T325768, the appearance was specified for temp user links in history pages, which adds 2px/8px padding, and this was implemented in the .mw-tempuserlink class as the default.