The task split looks pretty sensible, and we can go through in more detail when we do the task breakdown. The big concern I have is about the end-to-end testing - we would need a way to enable the Musical Notation datatype for Wikibase when the Score extension is loaded, and we would need there to be a live Shellbox for CI that has lilypond installed. I expect that both of these things will be hard to achieve with Quibble. We might have to make do with unit testing - still an improvement on the zero tests currently included in the Score extension.

yep - that's my expectation. I'll move the patch to the other task as soon as we work out which one it should be. Thanks!

@Alice.moutinho In the first screenshot, the "Help | Discuss" is not pinned for a single issue, but is pinned in the third screenshot (Overflow). Is that inconsistency expected or is that a mistake?

From task time on 4/12 - we would write the icon name, SVG and some associated HTML for the pop-over to the wbui2025 store and allow Wikibase to decide how that should be rendered (or if, for example, icons should be overridden?). Associated HTML here might be a reference to a Vue component that should be rendered inside the popover.

I have broken this implementation down into the tickets T411602, T411604, T411606, T411608 and T411609. Some parallelisation of the implementation is possible, though there are path dependencies between some tickets.

This has been resolved with the patches from T411237

Since you said 'ideally' for making them disappear, and since that's easier, I think we can just go with that :)

I think @Lucas_Werkmeister_WMDE's suggestion was to immediately dismiss any messages when the form reopens - mine was to move the messages up so that the buttons are not covered. Which of those do you prefer? And if the buttons should be moved up, how far? (Currently the green message floats arbitrarily 100px above the bottom of the form. Anchoring it above the grey line like we do with the red message would be slightly more complicated but also doable.)

@Alice.moutinho The situation happens if you successfully edit and then quickly open the edit dialog again. The green message covers the button for 3 seconds and the question is what to do there.