Since I'm touching this library for gpano, I might take a look. @Krinkle can you get me a list of some of the filenames throwing these log lines ?

Special:TimedMedia statistics could work i guess..

For the old player this is T96504: Video subtitles delay and expected.

Another note to self: once implemented, this requires an update to the cached metadata using maintenance/refreshMetadata --force

Note to self, Apple uses EXIF CustomRendered == 6 (panorama)

i think this is a really cool idea btw.

I now have:

• changes to our xmp-reader, which read the relevant metadata (still needs test)
• changes to the thumbnail renderer, to check the metadata for panoramas and to add a data-projection-type attribute if appropriate (T151451)
• a userscript to replace images annotated with data-projection-type, with an iframed https://tools.wmflabs.org/panoviewer/ (if i disable crossorigin checks in my browser)

Doesn't seem like our problem to me... browser bugs be browser bugs...

old Kaltura player is not lazy loaded if you use audio-only or inline videos over $wgMinimumVideoPlayerSize

Shouldnt we trim to a sane amount of digits behind the radix ???

I used to have a sharebox.js userscript yes, and it showed a disclaimer on its documentation page..
https://web.archive.org/web/20190410075542/https://en.wikipedia.org/wiki/User:TheDJ/Sharebox

made some of those changes for you, but notice the raw curl usage, which instead should be https://doc.wikimedia.org/mediawiki-core/master/php/classMWHttpRequest.html

can you add a screenshot ? not everyone has an android, let alone the same version of an Android phone. Screenshots probably easily communicate the problem.

Low usage is a terrible metric to remove features. Valuable usage is what matters. For instance, from a 'global' perspective most Sysop gadgets are never used.. but removing them would break many workflows for admins which in turn affects everyone.

[Error] Origin https://commons.wikimedia.org is not allowed by Access-Control-Allow-Origin.
[Error] XMLHttpRequest cannot load https://fastcci2.wmflabs.org/?c1=1685819&d1=15&s=200&a=fqv due to access control checks.
[Error] Failed to load resource: Origin https://commons.wikimedia.org is not allowed by Access-Control-Allow-Origin. (fastcci2.wmflabs.org, line 0)

Is this fixed now ?

Adding my caution to @Izno's ;)
Many of these classes have wide usage OUTSIDE of the templates they are historically associated with. Please make sure you don't break things accidentally.

Found that experiment back: https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/TimedMediaHandler/+/525145/

so initially we chose this route, to make sure we had full HTML5 fallback.. The technology of lazy loading is somewhat incompatible with html5 fallback content as the controls are always presented.. you can add lots of logic on top to hide the native player and everything, but what if someone already started native html5 playback before your 'lazy load' logic start overlaying it ?

{{Audio}} is a broken design and needs to be fixed, but that is not easily possible as long as the old player is still deployed for people, it will have to wait.

[[Media:]] is nothing more than a file download link and never will be anything but that. It has nothing to do with inline playing. [[File:]] transclusions exist to create players (or technically: has the responsibility to transform a file into HTML for a page.

Some images in articles are not labeled.

This should now be fixed if your browser supports localeCompare for the locale you are using in the content

This should now be fixed (if your browser supports locale compare for the language of your wiki)

No proton is the renderer, it doesn't determine what gets rendered. That is mostly a Collection extension problem + infra.

small note.. seems that hhvm is out of date with php7 here and doesn't support webp with its getimagesize.. possibly this should therefor wait for our complete php7 switch ? or wrap in HHVM conditional...

This is because we reuse ids.. and render the new player in detached mode, before removing the old player.. But video.js keeps global dom state, which is only removed when you use the .dispose() function on the player.. And since we don't, the 'new player' reuses context from the 'old' player...

T228250: PHP Notice: Undefined property: stdClass::$module in OATHAuth/src/OATHUserRepository.php on line 193 could be a potential blocker ?

but.. have those db changes run on WMF production already then, because otherwise this might turn into a production issue. I only see a note of them having been deployed to beta.wmflabs

Note that getimagesize and getimagesizefromstring are part of standardlib not GD, even though they are documented on the GD page (were they originally part of GD?)

because i already did so ;)

Pretty sure this is: T129546: Support preserving external links in pasted HTML content

Note that this thing isn't really meant to be used in the first place ;)
It's more a test page for the tiles renderer, and people tend to embed the maps directly in their own copies of openlayers and leaflet

Note that this thing isn't really meant to be used in the first place ;)
It's more a test page for the tiles renderer, and people tend to embed the maps directly

right, i was still in the process of swithing this thing to leaflet

Fixed, this was lost at some point probably due to switching from .OSM to .XYZ layers, which caused it to loose the automatic attribution.

The original is upside down, with a 180degree rotation file annotation. Apparently at some point the transcodes for that recognized this and fixed it.

While perhaps not perfect, this should get us by for now. Further issues can be filed separately.

In T213893#5321448, @Kghbln wrote:

the version check for php won't help you in giving useful feedback as you will receive a syntax error.

Ah, so this broke the version check?

User is using MariaDb. Another user just reported:

I've updated the description a little bit, to more accurately reflect the current status.

I note that this introduced php 7 syntax into the update.php script.
This means that if you use php56 and try to run update.php and accidentally you use php56 as a command line default etc. the version check for php won't help you in giving useful feedback as you will receive a syntax error.

Maybe an update to the class documentation to make it easier to distinguish between proper use and inproper uses ?

Seems like something that could easily be experimented with, using some javascript. A minerva specific gadget ?

i've long since said we should just provide both and allow users to switch between them, like we now do for normal diff and VE diff.

@Jnanaranjan_sahu This ticket is about sorting the results retrieved from their search terms, in order of certain date fields instead of 'relevance'. It is not about making the dates themselves search terms.