- Open Source dev since 2001
- Wikipedian since 2005
- Wikipedia admin since 2008
- Commons admin 2010-2015
- MediaWiki dev (+2) since 2009
Uses Safari most of the time (because someone has to)
Uses Safari most of the time (because someone has to)
Small note that this hint was specifically for keyboard-only users, less for screenreader users
Not sure what goes on exactly, possibly has something to do with the #anchor synchoronization. But when I cursor from tab to tab on https://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
The focus immediately follows me, and selects to tabpanel making it impossible to actually descend into the tabpanel, because going forward or backward will select the next tabpanel again. (only the first and last allow me to get out).
Please note that the new tabs dont actually work in a screenreader. At least not when using VoiceOver
Also sounds like a good time to trim the access list a bit of any people that are 100% no longer involved in the projects.
So from an Accessibility point of view, the best html for this url is:
<ul> <li> Required parameter $paramName" for the required ones? </li> </ul> <ul> <li> <span aria-description="long explanation">Param name</span> <button>add/remove parameter paramname</button> </li> <ul>
I noticed this on the RFC talk page, but let me also put it here: Why limit to maintenance tasks ?
Why not a general architecture to run (command line) tools, of which the maintenance tool is just a more specific set/scope (maybe it's own registry ?)
This is because frontend/modules/ext.flaggedRevs.advanced.js makes assumptions about the msg keys that should be used here.
Speaking of, I noticed it now insert it's markers in competition with the visual diff beta, creating a layout that is less than ideal.
definitely still there for me, even in the HTML response (so no JS issue)
has no one tested that things like this shouldn’t happen? Can we instruct people to thoroughly test major changes like these so that this wouldn’t happen again?
Most of this part of MediaWiki has no unit tests. How it is "meant" to work is held in the minds of a few thousand users from their experiences. When re-writing it from scratch, sometimes some ultra-edge-cases get missed, like this one (all the REVISION* magic words are dark magic which are abused significantly). There was a great deal of testing, but sadly this was missed. The good news is that this area is now extensively covered in tests.
I don't have enough time to read through all this, but note that jumping the focus elsewhere ALSO can be accessibility issue. Think of it like this: You have roadmap directions, you read one of the streets, and suddenly the entry after the street you just read changes to something else. That's confusing and will make you doubt about where you are.
@AlexisJazz I doubt it does. As far as i know Apple only ever supported MPEG2 in MPEG-TS and as DVD. P.S. there is also T166024: Once it's not patent-encumbered, enable MPEG-2 support for Commons uploads and TMH/etc. playback
I'm sorry if I crossed a line or two, but I feel like two months of sitting on something this major is too long. If there's a better way to express frustration and prompt more immediate action in situations like this, be sure to let me know.
I think we can pretty much call this dead. It seems npm is catching up on most fronts, and this being a Facebook project seems to create higher levels of discomfort with certain people.
Agree that it would be really nice if we had dashboard for all extensions, as we sort of have with deprecated JS, giving you insight in this kind of stuf.
I'm a bit surprised that a database disappeared, and that no one thinks that should be explained/investigated ....
What's going on here ?
@Graham87 just to double check. You don't like having this popup information to begin with, because it is too much info and/or too many any interactions ? And you would not tab through the page to open them.
But it's not less accessible then it is was before right ? If you actively decided to ignore them, at all cost, you wouldn't run into them ?
Related: T192489: Page previews settings (“cog wheel“) are not keyboard accessible and T192627: Feature branch: Page Previews excerpts should be referenced by `aria-describedby` so we can begin user testing
Particular article fixed by enforcing a clear of the left floating objects
This is just yet another version of the HTML/CSS weirdness that bullets are actually part of the background instead of the content, and are thus NOT pushed out of the way when (left) floating content, like the image in the screenshot is pushing the content aside.
Please file a bug report with Firefox
The problem as I see it is the "overflow:hidden;" inline style on the template parent element which disables scrolling.
Interestingly enough, globals usage has actually been on the rise since october 2017... scary, to see how infectious code is...
whoops, copied a little bit too much there. Those weren't meant to attach to this ticket.
declining as unverifiable
Keeping this in favour of T200741: Editing site JS results in unexpected behaviour, as it's the more technical accurate ticket.
euh, not sure what i did there, not a dupe ;)
was an easy one, fixed.
Basically I only redirected randomarticle.php to core functionality to keep existing links working. Other than that, I consider all of erwin's tools to be pretty much deprecated/dead.
I can add you as a maintainer to the project, you can create your own project, or you can simply open a ticket to expand the functionality of Core to provide this.
Seems the transcodes were not moved with it at the same time, and these thus need to be regenerated. Until that time, there are not compatible formats to play for the player.
@Sadads which platform level ours ? I don't think we can solve this in MediaWiki. It's not so long since there finally is an HTML annotation to force downloads, but there is certainly nothing to force viewing. The only way is to rename all the files like @brion alluded to. But that would be more of a workaround, technically, they shouldn't look at urls to determine how to handle them. They only do this because there are some sloppy system administrators who don't properly configure the content type of files they serve.
Why do we cache 24 hours ? That seems like a lot for clients to cache. 1 hour would seem more than sufficient shouldn't it ? varnish could even use stale-while-revalidate to keep it's responsiveness.
Was tagged with the wrong project.
Just a note that this is fixed in librsvg 2.42.2, just like T193352: Update librsvg to support streamline-emoji
Hmm. This is for desktop, but likely there is a Mobile option too: https://support.google.com/chrome/answer/6213030?hl=en
Might be related ?
Any idea about phone brands and/or installed PDF viewer software on those devices ?
1,549,538 articles in en.wp feature usage of a (1 or more) Module:Message_box (the meta template for all Template:*mbox'es)
1,076,899 articles in en.wp feature usage of a Template:Ambox
@AfroThundr3007730 Usually these notices are not rly revision specific however. (protection expires, namespace/page notices are removed and/or added based on the behaviour of the audience/not the content etc etc).
@Amorymeltzer Unless the site is down, about to go down, or unusable for a very large group of users a ticket is not Unbreak Now!
Naively, I considered getting a physical braillex display, because how expensive can such a simple device (in the time of iPhone X'es) be? Well it seems that prices go easily 4000 euros and up !
I think we can close this ticket. The Gadgets (-extension) phabricator project usually does not deal with tickets of specific gadgets. The support forum for wikEd is well known: https://en.wikipedia.org/wiki/User_talk:Cacycle/wikEd
Is this about mobile apps, or the mobile frontend in browsers, or both? :)
This link disables some functionality on that same page that might possibly interfere. Do you experience the same problem there ?