In T257490#6359873, @Trizek-WMF wrote:

Which proportion of users raised this up?

Enough to cause concern :) You can google translate this part of consensus. I just need data about our test to convince them.

Mainly arguments: "I would not work with Wikipedia myself if you showed me this poll. Users will think that we want to steal their data"

In T257490#6359676, @Trizek-WMF wrote:

Thank you for the update! ;)

In T258584#6359066, @Jdforrester-WMF wrote:

That large a hover trigger area probably isn't great from an accessibility standpoint (too much of the screen flashing in response to user action).

Hmm, It seems to me that it is good that the entire button is blinking, maybe I'm wrong.

In T258584#6359066, @Jdforrester-WMF wrote:

Can you explain why you think the current WikimediaUI-compliant design isn't?

1. Not our icons are used
2. Not our colors are used
3. The start button is basically out of OOUI style

@brion, @Jdforrester-WMF: And if like this (gif image)?

We can set a fixed width for the block, but here it is mainly about the fact that such buttons cannot be used :)

In T246035#6357180, @brion wrote:

In T246035#6357153, @Iniquity wrote:

Don't just call the OOUI window, maybe just replace the area of the audio placeholder?

That would defeat the purpose:

• no place for subtitles
• no place for additional controls which will be added later for control of embedding and subtitles
• no garbage collection of player instance when it's closed

• Create display:none block, and change it to display:block when subtitres choosen
• I think there is enough space, but for especially small sizes, remove all settings to the additional menu.
• I don't quite understand why this is needed :)

Don't just call the OOUI window, maybe just replace the area of the audio placeholder?

And what will happen after the deployment with T246035: Videojs player for audio opens a dialog to support subtitles, which is unexpected?

Blockers, I think:

• T258578: In the "New video player" beta feature, Subtitle and Quality lists are forced to LTR direction
• T258644: VideoJS audio player start button is misleading
• T258570: Increase interface's base font size for VideoJS player
• T258622: Poor display of media on Special:NewFiles
• T249204: New video player does not leave enough space in gallery
• T258638: Improving the accessibility of buttons that launch the player
• T138768: TMH video.js-mode 'info' button needs localizable alt and hover text
• T249249: Loading indicator renders in the top left corner instead of centre

Wow, stop, you have a bunch of bugs not fixed, what deployment to Group 1?

In T259240#6349611, @Volker_E wrote:

@VulpesVulpes825 Could you clarify the statement “can give users the impression that something is wrong about the site and browser”? Why would that induce the impression of “something wrong”?

In T248457#6330346, @QEDK wrote:

Each project however retains full control over their content. The Wikidata
integration was done prior to receiving community feedback and hence
there's no reason to not undo this given that work has been put in to make
it better for everyone - integration does not equate to it being better. As
Tgr said, this is not the place to relitigate, if you object to this, start
a discussion on English Wikipedia.

I would probably still agree with this if the integration would be simply disabled. But instead of that, the integration turns into support for a template, which is then transferred to other Wikipedia, where it is completely useless.

In T248457#6330315, @Tgr wrote:

@Iniquity this is not a good place to have this argument. If you want to convince the English Wikipedia community that Wikidata descriptions do not conflict with their policies, or that they should be used regardless of whether they conflict with their policies, you need to do that on English Wikipedia.

I came here not to convince the English Wikipedia community, I came here to express my disturbance to the Wikidata and MediaWiki developers that they support the deterioration of integration between projects.

In T248457#6329589, @RexxS wrote:

What happens, though, is that it adds content that may not abide by the local policies and that is a fundamental flaw.

I don’t understand how a five-word sentence might not be in line with local politics. And I also don't understand why this policy cannot be negotiated with Wikidata?

In T244486#6327653, @alexhollender wrote:

In T244486#6326085, @Iniquity wrote:

@alexhollender no, sorry if I explained it wrong :) I mean, will these logos be uploaded to commons?

Ah, of course! Great idea. I've just created T258643 to track that.

In T248457#6326902, @RexxS wrote:

If you don't want to abide by the policies on the English WIkipedia, you need to stop adding content to the English Wikipedia. It's not a difficult concept.

I am now doing QA testing of the player, and I was very surprised when my audio opened in popap. Of course, less than when I found out that these are not control buttons, but an ordinary picture...

Changed to latest with OOjs classes, check it here: https://commons.wikimedia.org/wiki/Template:Upload_Help_notice/sandbox. Feel free to update main file :)

I understand correctly that this refers to the comparison with the styles of the MediaWiki, and not the extension itself? I would expand it in this case.

@alexhollender no, sorry if I explained it wrong :) I mean, will these logos be uploaded to commons?

Needs solution for task T258573.

I think It can be closed because of T248061.

Possibly related to T227195.

I think this may interest Performance-Team, delete if not for you :)

@Trizek-WMF, Its good :)

Yes, I also started working with video from Commons, and noticed that it is very inconvenient to independently enable and select subtitles from a list of 50 languages.

I would like to see these logos on Commons, will it be possible? :)

In T254055#6324701, @Jdlrobson wrote:

I also wonder if the only blockers are community consultation whether there is anything @Iniquity could do to help us (e.g. see on village pump whether this would be controversial)

Yes, community consensus I think will be the biggest problem for this change. I have already spoken to some of the members and received mixed reviews: old editors work in a very peculiar way with the font, some increase it by browser's scale, some say that it is more convenient to read a small font. We can prepare a survey (with information about [https://pielot.org/pubs/Rello2016-Fontsize.pdf | readers expireince]) and distribute it via Tech Ambassadors & Translators, for example.

Must be re-analyzed with new version. Stalled for now.

In T256585#6314974, @Aklapper wrote:

@Iniquity: This is basically the same as T238341: Structured localization framework for Templates, Lua modules, and Gadgets, but describing the status quo instead?

Yes, it describes the status quo, but that task is still more about the technical component, and not about the documentation for the user.

If created this should probably be linked from https://www.mediawiki.org/wiki/Gadget_kitchen

Yes, this is good idea :)

In T256585#6263780, @Aklapper wrote:

Hi @Iniquity, thanks for taking the time to report this! Unfortunately this Wikimedia Phabricator task lacks some information.
If you have time and can still reproduce the situation: Please add a more complete description to this task and provide links to where you'd expect such documentation to exist. Also, did you mean "internationalize" maybe?

Thanks for the clarification :) I expanded the task.