> 1) Use of tipsy for language change notification [...] is an important feature. Also, let's stop calling 1 a tooltip, because it is not: it has a link and it is automatically shown. [...] it has been proposed or I propose: I) mw.notify (has positioning limitation, which possibly could be fixed) II) OOUI (I suppose it's even heavier than tipsy, correct me if wrong; seems out of question) III) Custom, as-light-as-possible solution
> Regarding the specific use for ULS, we want to:
> * Notify the user of a language change and provide a quick way to revert it (note that turning your UI to Greek by accident can be problematic if you don't know the language).
> * Make it in a lightweight way: not requiring specific confirmation to avoid getting into the user workflow when the obtained result is what the user meant (most of the cases)
> * Connect that piece of information to the language settings component to show the general way to adjust such settings.
> The solution proposed can be described as a "transient undo popover" more than a tooltip. We just used tipsy because it was what was at hand. I'm ok in using a different technology but I won't break the principles I described above.
> I Googled for "undo popover" (Pau's phrase) and came across discussions about Google's "undo send" functionality, which seems indeed to be a very close match for what you want: i.e., a way of telling the user "OK, I did what I think you wanted me to do, but if you find out it's not what you wanted there is a window of opportunity for you to quickly reverse it". mw.notify() does indeed seem like the best fit, in that case. I understand that having it in the default position does not fulfill your desire that the undo option direct the user to the ULS interface pane, but I think that's both fixable and a smaller problem overall than the misuse of tooltips.