@KSarabia-WMF to write the patch. https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/1145274 for reference.

Refined requirements based on above.

Thanks for the report!
I can replicate with a newly created user who enables the beta feature cc @Dillon - related to T394736.

Also impacts Charts - https://commons.m.wikimedia.org/wiki/Data:Olio_di_cocco_produzione_mondiale.Bar.chart
So I think if we're changing one, we should change both for consistency.

Thank you!

Since the contents of the Chart are using echarts library I wouldn't recommend or endorse using CSS to hide anything here. I think if you need to disable anything it would be better to request it explicitly and for us to configure a boolean on the chart definition to do this.

In T299772#10852940, @DLynch wrote:

mw-mf is a more intended for use in CSS, it's true -- and it is being used there in a number of places. (Though I do kinda think that caring about document.body.classList.contains('mw-mf') is a bit overzealous in user scripts -- it mostly matters for the WikimediaEvents case because it's really likely to trigger during the critical initial render flow, and for all users.)

The point I was trying to make is that there is a use case here and that skins have been setup to make this an extensible area (in the same way subtitle is now extensible via mw.util.addSubtitle) and that things other than site notices populate this area.

(Given age and inactivity)

Seems like nobody is looking at this and Minerva is passing againso marking back as resolved.

I assume this has been addressed.

Is this done?

Makes sense, thanks. Seems like they could get addressed by the same fix though?

ePub is no longer supported.

PDF generation appears to be done by a wmcloud instance now (https://ws-export.wmcloud.org/?format=pdf&lang=de&page=Index%3ATBHB_1943-07-19) so this doesn't seem relevant.

Since there is no book PDF generation any more.

TODO: Confirm this is still an issue.

Since there is no book PDF generation any more.

Since there is no book PDF generation any more.

Since there is no book PDF generation any more.

Since there is no book PDF generation any more.

I don't think PDF generation is likely to be restored in the current extension (at least while it is in Wikimedia production).

I can't replicate the exact issue but following the test steps I do see a JavaScript production error.

I would not recommend this is done as part of the existing Collection extension.

Assume applicable to Electron PDF now that we don't support PDF generation of collections. Apologies if I'm misunderstanding.

Closing an inactive epic with no subtasks.

TODO: check if we're still seeing this exception.

Given the state of the book feature we shouldn't be focusing effort on driving new users there.

This has been broken since 2011 and the code / feature should be removed.

There is no longer a book render service.

Dupe of T379460 perhaps @Ammarpad ?

I don't think this applies any more given the simplification that has happened in the extension (we no longer have a render service). Please let me know if I am missing something.

I don't think this applies any more given the simplification that has happened in the extension. Please let me know if I am missing something.

This seems acceptable in 2025. We have been using the siteNotice wrapper for things other than central notice banners e.g. WikidataPageBanner

Not likely to happen given the inactivity in the extension.

Not likely to be addressed but patch welcome.