Jan.Kamenicek

Linter errors.

See https://en.wikisource.org/wiki/Special:LintErrors/misc-tidy-replacement-issues

Your user page appears to have a swapped DIV and SPAN. This is often when a template like {{float right}} contains a template generating DIV based syntax. You may wish to consider using {{right}} or {{right block}} etc instead?
ShakespeareFan00 (talk) 09:49, 17 October 2024 (UTC)

Hm, unfortunately, each of the boxes behaves a bit differently which makes it difficult to align them one under the other. The only way that worked for me was putting them in a table. I have just tried to redesign it using the right block template, but it did not work. However, I have never seen this page displayed incorrectly on any device and in any browser, so the lint error probably is not a big problem. If you want, you can try to suggest a better design at User:Jan.Kamenicek/Sandbox, but it is probably not necessary. --Jan Kameníček (talk) 10:07, 17 October 2024 (UTC)

The specfic issue that's showing up on the linter, is that you've put {{collapse top}} ..{{collapse bottom}} inside {{float left}} . {{float left}} only takes a SPAN parameter, soemthing that's also caught me out more than a few times:) Not a priority though. ShakespeareFan00 (talk) 11:20, 17 October 2024 (UTC)

I did a quick sandbox on Expand Templates. {{left block}} seems to be the DIV version of {{float left.}}, but you already updated the page. Thanks :) ShakespeareFan00 (talk) 13:37, 17 October 2024 (UTC)

Yes, I have replaced the float left templates for block left, so I hope it is OK now. --Jan Kameníček (talk) 13:41, 17 October 2024 (UTC)

Vector 2022

Hi @Jan.Kamenicek, since it's been more than a week with no reply from SGrabarczuk about their plans to switch to Vector 2022, I was thinking it may be worth writing to the WMF board directly, as I doubt they are aware of this issue. From what SGrabarczuk said, the technical team seem to be arguing that "due to legal reasons, we will have to enable" temporary accounts, which is supported only by Vector 2022, so I doubt we will be able to prevent this entirely. However, if we make the case to the board, I think they might consider getting the technical team to prioritise fixing the main issues, and perhaps extend the deadline until these fixes have been made, in contrast to their claim that they would "talk and may make some changes, most likely after the deployment". What do you think? (I would be happy to help draft something if you'd like?) --Yodin^T 12:12, 15 November 2024 (UTC)

Hello. Meanwhile, somebody has answered there, though their answer was in fact just empty words without really addressing our concerns. I am not sure whether writing to the board would help anything because they are imo on the same wavelength, but it can be tried. However, I am not sure whether I could be diplomatic enough, so if you could draft it, I would appreciate it. Or maybe you can write it directly on your account if you want too. How do you think it is best to contact them? By email? -- Jan Kameníček (talk) 14:56, 16 November 2024 (UTC)