OK, I'll try to install 1.4GHz Tualatin with 512K cache (my treasure!) instead of my current 1Ghz Coppermine with 256K (I know you may not believe it), but I still don't understand your approach to consensus. Doesn't enwiki demonstrate a clear consensus to remove the update? You impose it nevertheless, and it makes me wonder.

It seems that no one thanked Volker for this "improvement". No one at all! See this ridiculous talk at enwiki where he had suggested masking it with CSS {display:none} when I asked him about the performance. You know, I still won't upgrade my hardware just because of your useless features, but now every time I chase a vandal at enwiki (one of my main activities) I have a time for recalling some things before the edit history opens. First, I recall the name of the developer who imposed such a wonderful gift on me. It's Volker. Then, who that Volker is? He's [censored], [censored] and [beep]. Did the edit history open yet? Not yet, wait some more. Then Volker is [beep] [beep] [beep]. And the edit history is still not avalable. It finally ends with someone else reverting the vandalism, but it's not me. Thank you Volker, I'll never forget you!

In T107069#5096891, @Iniquity wrote:

this block is not needed

In T165189#4790562, @stjn wrote:

I was saying about any active states, of course (so, focus/active/etc.).

In T165189#4787486, @stjn wrote:

Could this be done with saving previous colour by default (unless on hover)? I am fully supportive of this change on the grounds of accessibility, but right now basically everything in the watchlist is blue, which doesn’t help with hierarchical navigation.

Do new editors understand what the Preview button does? Would they use it more if there was an explanation next to it?

As I've already said at the tech forum of ruwiki, my personal average use of the "Preview" button is much more than that of the "Publish", maybe 10 or 20 times for large edits, and even the smallest edit won't go without one. The same stands for "Show changes". And I do encourage everyone not to hurry too much, given that the published edit will always remain at least in the revision history. So, to get started with, my suggestion is to avoid putting extra emphasis on "Publish" button in the new OOjs UI and keep color the same for all three buttons like it used to be.