In T344680#9115373, @egardner wrote:

As far as the equivalent for the code sample you posted, as I mentioned there is still more we need to do before the process is streamlined enough to recommend generally, but you can use Codex components now by doing something like the following:

mw.loader.using('@wikimedia/codex').then(function( require ){
    var Vue = require( 'vue' );
    var Codex = require( '@wikimedia/codex' );
    
    Vue.createApp( {
        data: function () {
            return {
                count: 0;
            }
        },
        template: "<cdx-button @click='onClick'>click me</cdx-button><p>You've clicked {{ count }} times.</p>",
        methods: {
            onClick: function () {
                count++;
            }
        }
    } )
    .component( 'cdx-button', Codex.CdxButton )  // register the component
    .mount( '#my-app' );  // assumes that you have an element with an ID of "my-app" somewhere on the page
});

Tagged the wrong task, sorry.

In T52881#9352286, @gerritbot wrote:

Change 976691 had a related patch set uploaded (by Sophivorus; author: Sophivorus):

[mediawiki/extensions/ParserFunctions@REL1_39] Backport fix of implicit conversion to int

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

I think the issue is that a few lines before (line 817) there's the following line:

Sure, makes sense, thanks for your time and answer!

Thanks! I also updated this and now the stats on the page seem up-to-date.

How about a config option for third-party wikis that don't have extremely long articles and may therefore benefit from defer over async?

Yes! This solved the issue that I reported here and had me baffled, thanks! The code you shared didn't quite work for me (perhaps because I'm using REL1_39) but after understanding what's happening and doing a few tweaks, I made it work. Thanks again!!!

I think the problem might have been that the repo didn't have the permissions set up. I just fixed that, see https://gerrit.wikimedia.org/r/admin/repos/mediawiki/gadgets/MiniEdit,access

Apparently it's not so simple, gallery thumbnails and plain images are processed before image thumbnails, so in order to lazy-load everything but the first image thumbnail, the code would be:

$wgThumbCount = 0;
$wgHooks['ThumbnailBeforeProduceHTML'][] = function ( ThumbnailImage $thumbnail, array &$attribs, array &$linkAttribs ) {
	global $wgThumbCount;
	$class = $attribs['class'] ?? '';
	if ( strpos( $class, 'thumbimage' ) !== false ) {
		$wgThumbCount++;
		if ( $wgThumbCount === 1 ) {
			return;
		}
	}
	$attribs['loading'] = 'lazy';
};

Again, this idea can be easily customized.

For what's worth, here's a bit of code anyone can add to their LocalSettings.php to lazy-load just the FIRST image of every page:

$wgThumbCount = 0;
$wgHooks['ThumbnailBeforeProduceHTML'][] = function ( ThumbnailImage $thumbnail, array &$attribs, array &$linkAttribs ) {
	global $wgThumbCount;
	if ( $wgThumbCount > 0 ) {
		$attribs['loading'] = 'lazy';
	}
	$wgThumbCount++;
};

It can be trivially modified to lazy-load the first TWO images, or whatever. Hope it helps someone!

Hi, good news! I was able to add valid hashtags to links by simply adding a space before the # (so as to satisfy the Twitter's specification of a hashtag) like so:

Hi, thanks for identifying the cause and the temporary fix! Just to keep you updated, now it seems the tool has stopped recording changes since August 18, cheers!

@Samwalton9 Hi! Ping because it seems you fixed it last time T321635? Cheers!

I second this request. Three of my tools (Proveit, Synchronizer and WikiEdit) would benefit from it.