I wonder whether Use packageFiles for Popups https://gerrit.wikimedia.org/r/1024608 would be a good first step to see whether packageFiles (in comparison to JavaScript bundlers such as webpack or rollup or vite) is a viable strategy. It seems that this patch is mostly ready?

Likely a regression of https://gerrit.wikimedia.org/r/c/operations/puppet/+/815759.

Screenshots of https://gerrit.wikimedia.org/r/1079645:

Might be obsolete if we remove this link completely, see T376972.

Related: T360589

Related issues: T77108, T77481, T68606

Related to T365193.

Any new insights? If createEntityView in wikibase.ui.entityViewInit.js shall not be called from commonswiki, maybe we should simply return from this function if mw.config.get('wgWikiID') === 'commonswiki' && mw.config.get( 'wgCanonicalNamespace' ) === 'File'

The template parsing is performed by the CommonsMetadata extension.

@TheDJ in https://gerrit.wikimedia.org/r/910766

MobileFrontend uses its own implementation different from MediaViewer, see T65504 for the plan to use the same code for both versions.

Testing today, I obtain the following caption: "Tämä on kuva suomalaisesta monumentista, jonka tunniste on 'Turun tuomiokirkko ja Turun historiallinen ydinalue' (Q29974183) - RKY: 4620"

The problem here is that the monument template outputs this HTML fragment:

The template parsing is performed by the CommonsMetadata extension.

The desktop MMV should allow cycling images e.g. it should be possible to get from the first image to the last image.

Great, thank you so much. I've migrated to codex.style-bidi.css for dinoscan: https://github.com/simon04/dinoscan/commit/595314ae000e331b00716d728c68882098fc15c0

with something smaller (what?)

@Cparle, the patch is working now... :)

This seems to be the relevant CSS code regarding scroll-padding-top: https://github.com/wikimedia/mediawiki-skins-Vector/blob/3cbb12b590bf7de3f8eac956904e9486fd50c706/resources/skins.vector.js/stickyHeader.less#L133

Related: T360589

Hi @Jdlrobson and @TheDJ, I've drafted a patch to get an idea how the Vue.js future of MultimediaViewer could look like. It's far from complete and lacks plenty of animations and interactions. Also, it should use the native Vue.js Codex components, eventually. What do you think? Is this (draft of) Vue.js migration worth pursuing?

The square icons look awesome. Thank you for your great work, @mwilliams and @TheDJ!

In T368225#9919409, @Sneha wrote:

Let us know what you think.

In T366197#9922602, @Jdlrobson wrote:

This looks like it's in production, is that correct? It's appearing in dark mode for me on https://en.wikipedia.beta.wmflabs.org/w/index.php?title=T352930&veaction=editsource&action=edit

Some preliminary notes regarding an implementation:

• includes/media/JpegHandler.php swapICCProfile already implements invoking exiftool
• exiftool supports removing all GPS tags via -gps:all= -- https://www.exiftool.org/geotag.html
• to be figured out: how to invoke JpegHandler from UploadBase (there's also TransformationalImageHandler.doTransform, but it seems to be related to thumbnail generation)

Should have been fixed T139808, but the patch confused seconds with milliseconds.

Fixed in T361049 via https://gerrit.wikimedia.org/r/c/mediawiki/extensions/UploadWizard/+/1020880.

Done in 2016 via https://gerrit.wikimedia.org/r/c/mediawiki/extensions/UploadWizard/+/325559

This confirmation dialog has been removed in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/UploadWizard/+/1037482 for T365710.

Confirmed. The strings have changed:

White-on-white icon issues in dark-mode in VE – page options dialog:

The caption/description fields are currently undergoing an overhaul, see https://commons.wikimedia.org/wiki/Commons:WMF_support_for_Commons/Upload_Wizard_Improvements for details.

The tests haven't been fixed, but just (temporarily) skipped via QUnit.skip – https://codesearch.wmcloud.org/search/?q=QUnit.skip&files=&excludeFiles=&repos=Extension%3AMultimediaViewer

Seems to be addressed via T361049.

See T327009 for a more generic approach. Instead of using &depicts=... it suggests &property=statements (such as &P180=Q10884).

MediaSearch uses a copy of getLocationAgnosticMwApi since 2021-04-09:

Issues 1+2 seem to be fixed (with the migration to Codex?). Issue 3 remains (the extension is using TextInput plus a Button instead of SearchInput).

Untagging SearchVue, covered by the subtask T357420.

Untagging MediaSearch, covered by the subtask T357421.

Err, confused SearchVue with MediaSearch. Sorry!

A draft how this could be implemented: Add language filter with all available languages. We could additionally display the Codex icon cdxIconLanguage...

@Jdlrobson How are you measuring?

Does the imageinfo API support specifying the SVG language?

Thanks, I've noticed this, too. Should be fixed via https://github.com/simon04/bldrwnsch/commit/fb08b36d57b3eae27af435b252b5cb095b52dae1