I just noticed that 8301136545 works, but weirdly, the ISBN which you get back in the citation (9788301136543) does not work! Is it just that the isbn 13 isn't in their search database (despite that obviously they know about it because they're returning it) do you think?

Maybe it would be more useful to spit back interpretation of what was entered. You know like now when enable ES6 it says that on the special page ("This gadget is only supported on ES6-compliant browsers") and other thing like that. So like that, but show even a dump of options on a preview of changes or something. I guess an editor would solve that too (like for TemplateData).

Something you can use for things like popups:

// popups
// only on devices that can hover (not on touch-only)
if (!window.matchMedia("(hover: none)").matches) {
	importStylesheet('MediaWiki:Gadget-navpop.css');
	mw.loader.using( "mediawiki.api,mediawiki.user,mediawiki.util,user.options,mediawiki.jqueryMsg".split(',') , function() {
		importScript('MediaWiki:Gadget-popups.js');
	});
}

The thing with en.wiki is probably that they get most of the stuff done by WMF. For example, many enhancements were made in the new Vector specifically after the mutiny on en.wiki. This is not a reproach; it just partly explains why they have fewer default gadgets. This also might explain why Wikisource usually has more gadgets than Wikipedia. WS has weaker support in general, and more features need to be added by the community.

Does that mean gadgets will still be available for all skins by default? So this would be a default gadget for all skins and targets?

wikiflex [ResourceLoader | hidden | default] | wikiflex.css

In T328610#8974807, @Jdlrobson wrote:

I do think on the long term we should replace targets in gadgets for a more sophisticated system. I like the idea from @Tgr for using skip functions - that seems more in line with what we actually want here. These skip functions could potentially be predefined so you might have a gadget that requires support for touch devices (ReferenceTooltips might benefit from that for example) that could mark itself up like so:

gadget.name[ResourceLoader|default|skipIf=TOUCH_DEVICE]

So to be clear this will cause a bug:

hideSidebar [ResourceLoader | skins=vector,monobook | targets=desktop ] | hideSidebar.js
MobileMaps[ResourceLoader|targets=mobile]|mobilemaps.js

This will be fine:

hide-rollback [ResourceLoader | rights=rollback | targets=desktop,mobile ] | hide-rollback.css | hide-rollback.js

On that note, there is a new color-mix function in CSS:
https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/color-mix

So this is called multiple times uw.ui.Upload.prototype.load = function (uploads).

There are too many files-added events.

Reproduction with images.

More detailed steps to reproduce:

The scripts are not re-downloaded every time you view a page, and there is no need to add any bcache, maxage or smaxage parameters to MediaWiki urls, these do not improve performance anymore. Performance is our default, as much as possible.

Note that on Village pump someone mentioned that the i18n menu doesn't work in Opera GX so that is kind of weird. I don't have that one but I tested with IE on Windows 10 (via Edge).

There is a green light from Zotero devs and the Polish National Library is now available:
https://github.com/zotero/translators/pull/3036

As I understand below would work, but AFAIK was not merged:

@Esanders That is helpful for other stuff... but none of that works for discussion tools.

@KFrancis I sent you an email. Please let me know if it didn't arrive or something else would be needed.

I've confirmed the steps above break refs.

This is still a regular thing. I think this might be happening for all named refs when the first ref doesn't have cite-body.

Sent an e-mail signed with my PGP, fingerprint: 86C84A9B865FDD51FCFB12D2EE3F8013A0DD3792.

analytics-privatedata-users is the wrong group and SRE-Access-Requests is the wrong workflow here. What you want for (especially client) log access is Logstash access which can be received via the nda LDAP group which is required via LDAP-Access-Requests.

In T336297#8859823, @Mvolz wrote:

In T336297#8846443, @Nux wrote:

Did you consider using LoC or some other national library?

Most if not all big libraries should support OAI-PMH. OAI can be used as a dump (kind of) to get all book descriptions and keep them on some Wikimedia server.

Most big libraries have some API which you could use directly to search for ISBN. Many probably use Z39.50 which is not very friendly, but doable for ISBN searches. Polish national library (BN) also has a custom API that support JSON, XML and MARC (but it is a custom API, so probably better for a local tool or gadget then a global search service).

Thanks for your suggestion! For the time being we have have enabled Zotero's ISBN endpoint internally which primarily uses Library of Congress (T336727)

With Zotero it would be possible to support other national libraries in addition by contributing a translator for them here: https://github.com/zotero/translators

In T336952#8863202, @Nux wrote:

[...]
I also narrowed down the problem.

• This is a minified Lua that is problematic: https://pl.wikipedia.org/wiki/Modu%C5%82:Kontrola_autorytatywna/temp
• This is a test page: https://pl.wikipedia.org/wiki/Wikipedysta:Nux/test_WD-KA_fail_-_mini

Please note that you will not be able to edit or view the test page until you disable the Lua module (e.g. change the name of the main function).

You may have seen my tests. I've re-enabled the KA template (the Lua call) for a while and it's a very popular template. I've disable the Lua call for now, but please note that it doesn't solve the problem.

Not sure if related but I see WD is on 1.41.0-wmf.9 (bacc43a)
https://www.wikidata.org/wiki/Special:Version

This "fixed" the article:
https://pl.wikipedia.org/w/index.php?title=Szablon:Kontrola_autorytatywna&diff=cur&oldid=prev

Authority control brakes the articles as soon as Wikidata element is conected to the article.

View doesn't work (after purge also doesn't work for anons).
Diffs don't work.
Edit doesn't work (even code).

In T336298#8849499, @EpicPupper wrote:

In T336298#8846535, @DeirgeDel wrote:

Stupid question. Is the Open Library API https://openlibrary.org/dev/docs/api/books a usable alternative? In particular ISBN via the .json format?

I presume that Open Library is not as comprehensive (it's the same as any other downstream collection like Google Books, it doesn't contain all possible ISBNs).

In T336595#8848878, @MBH wrote:

@Nux can https://www.mediawiki.org/wiki/Template:Graph:PageViews be replaced with the Timeline on something other? It is very high use case in ruwiki, pageviews graphs on talk pages.

There are two potential replacements for wikis. I just replaced graphs in some demographic articles on plwiki. Maybe this will help some other wiki.

And maybe some tools to sanitize user input form parameters (e.g. disallow characters that would break strings). Maybe some Lua utils?

Question/propsal: Due to T336595 sounding much like July (or worse)... Would it be possible to add some possibility to migrate existing charts in the meantime? For example, generate JSON of a given chart and show it in the HTML comment in the place where the chart was supposed to be displayed. So you could copy that spec, see what the graph looks like (offsite), and make an SVG, PNG, or some other substitution.

For no-JS icons inside buttons, we implemented a Less mixin that applies the icon SVG as a mask-image. This allows us to dynamically change the color of the icon when the user interacts with the button by changing the background-color, keeping it in sync with the text color. For browsers that do not support mask-image (e.g. Firefox < 53), we simply apply a black or white background-image depending on which has better contrast.

Did you consider using LoC or some other national library?

@Jules78120 Stylus CSS seem to be more stable if you want:
https://userstyles.world/style/5790/wikipedia-toc-tweaks

Sorry, was my project the last one on old grid? 🙈 I got an e-mail, but I was sure I've done this ages ago. The problem was a job in my crontab (not the whole project as the email suggested, hence my confusion)... Sorry about the delay.

Will this be supported? I don't see any protocols mentioned here. Is this supported in some API instead?

"url": "tabular:///{{{table}}}",
"url": "wikidatasparql:///?query={{urlencode:{{{table}}}|PATH}}",

Those are used in [[mw:Template:Graph:Stacked]]

url() can lead to lead to all sorts of nastiness unless controlled tightly...

@stjn you can see full CSS here, that will probably make more sense:
https://github.com/Eccenux/wiki-team-brackets/blob/master/html-redesign/lines.css

This would just work with CSS variables. In template code you can do this:

<div class="flexi-cols" style="--flexi-cols--min-width: {{{min-width|150px}}}; --flexi-cols--gap: {{{gap|1em}}};">
</div>

And in CSS for the template:

.flexi-cols {
	--flexi-cols--min-width: 250px;
	--flexi-cols--gap: 1em;
	
	display: grid;
	grid-template-columns: repeat( auto-fill, minmax(var(--flexi-cols--min-width), 1fr) );
	gap: var(--flexi-cols--gap);
}

CSS variables are already supported in HTML so this kind of already works... You just need to load CSS with a mw.loader or @import to make this work.

Another use case is making code more readable and maintainable:
https://pl.wikipedia.org/w/index.php?title=Szablon:Nux/test_teambracket/8tpl-lines.css&oldid=70248259

As there are plans for making a darkskin this will be important for templates. It will not be feasible for the WMF staff to create a skin supporting each and every template.

I think when you have a button that is only an icon and nothing else is displayed instead in IE then this is not an acceptable degradation (for me personally). The problem is in Vector sometimes you only have icons. But I think if you could display labels that are hidden and ditch icons for IE that would satisfy "content is presented in a readable manner, and content and account actions can be performed". Not sure about codex, but when you remove all classes from links in top menu it just works. So maybe in some case just make an empty css for IE? (e.g. surround everything with @supports)

Just as a note: you can write CSS for IE and then use @support(display:grid) to provide better layout for modern browsers. You just cannot use @supports not (display:grid) because of limited @supports support 😉. So IE rules first and other browsers later with @support.

Both should work fine in User:Example/hello-vue.js which you can import from common.js with e.g. importScript("User:Example/hello-vue.js").

Note that all browsers on iOS use WebKit engine (Chrome, Opera and even Firefox). So I doubt Puffin Browser can do anything about what they support. This is due to Apple policy which bans browser engines on their store. I guess most devs know that, but every browser on iOS is a skin over Safari (mostly).

As a follow up to pl.wikipedia switch:

Currently it works like that (both in Chrome and FF):

I'll let you know if those steps worked better once T332809 is done :-). I plan to use those steps in a message after the change.

JavaScript: Migrate any content from MediaWiki:Vector.js into MediaWiki:Common.js (NOT duplicating it, because that can cause errors, unless you know what you are doing)
JavaScript: Assess whether content in MediaWiki:Vector.js can be moved to Common.js or if it should be copied to Vector-2022.css and then move or copy it as appropriate.

About 15 UTC would be fine for me (just about my dinner time)...
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230330T17&p1=262&ah=5

OK, then we are ready: T332809 :)

When will the switch be possible?

WIP UI: https://patchdemo.wmflabs.org/wikis/6689bcdde2/wiki/Douglas_Adams?veaction=edit&section=26

Hmm... I did this exercise: change the position of the tools to the left side... And unfortunately there is a problem, not even with this grid, but with this structure. Maybe I'm missing something, but I've come up with something like below and I don't see how to fix it. I don't see a good, stable way to make a space between the table of contents and the tools. I can't do a row-gap because it will completely ruin the look of the title bar and tools. Longer ToC would also brake things.

I like the new grid :)

Everything seems to be working now, thanks 🙂

Similar bug still occurring. Example fix:
https://pl.wikipedia.org/w/index.php?title=Wikipedysta%3ANux%2FTracy_Barrell&diff=69907638&oldid=69907611&diffmode=source

A similar example I assume:
https://pl.wikipedia.org/w/index.php?title=Ko%C5%9Bci%C3%B3%C5%82_%C5%9Bw._Katarzyny_w_Timi%C8%99oarze&oldid=68618051
Current view with JS enhancement:

It turned out be much easier to do and more stable with the Broadcast Channel after all. Available as gadget for now at least:
https://meta.wikimedia.org/wiki/User:Nux/notificationsSync.js

Hardly a fair fight on Android with all those open-in-app modes and other stuff...

For what it's worth, it works in my test cases too (on WP, WS and WD). The element #mw-panel-toc is not in page DOM at all. Thanks 🙂

If anyone wants to tackle this, I have a newer version of the library for filtering here:
https://pl.wikipedia.org/wiki/Wikipedysta:Nux/ViewFilter.js

Maybe I wasn't clear. Firstly I know what those queries are for 😉. I want the templates to change based on the width they can actually occupy. E.g. in less obvious things like dynamic preview (which you could then use to preview template on small screen):

@Samwilson Sorry, I assumed all letters are using it. The HTML is from this page:
https://pl.wikisource.org/wiki/Strona:Janusz_Korczak_-_Dziecko_salonu.djvu/11

Note that the same link is also for connecting to an existing WD item when there is no WD connected yet.

link-button	dialog

Sorry, but it is still there.

Done. I see recompressing on YT makes it even weirder. You have to imagine it flickers faster. Much faster. The flickering is always when I scroll up. Not touching the screen is not changing anything (still flickers).

Here is a video with touch visibility enabled:
https://youtube.com/shorts/CzaVHHAsFpE?feature=share3

Fix in Firefox that can be applied in MediaWiki:Vector-2022.css even:

	#mw-panel-toc:-moz-only-whitespace {
	
	  display: none;
	
	}

Note that the element is also in the same place on Firefox (v110). It's just that selection behaves differently on Firefox and on Chrome. In Firefox you cannot select/click from left side of the title (as you click on a transparent element).

Possible fix:

Yes, I was assuming that page tools for anons would follow. Not sure anymore which things should be visible by default though. Page tools are more for consuming content by default on plwiki and "Zgłoś błąd" ("Report a bug") in your demo-link is on the left side...
https://pl.wikipedia.org/wiki/Sun?vectorpagetools=1&useskin=vector-2022