Your answer makes be both sad and angry.
The lack or ignorance of understanding that Plone5 having a severe quality problems speaks for itself.
AGAIN this one example (out of many) where simple issues, obvious issues, easy-to-spot issues are taken to the end-user.
AGAIN these simple issues distract people from using Plone 5.
AGAIN you are only looking through the eyes of a Plone core developer - you don't have user in the focus.
AGAIN the developer must have figured out these issues by itself - very easy to test, very easy to detect. Very little quality control in this case by the developer, very little quality control in this case by the GSOC mentor.
AGAIN this is not about me finding and fixing a problem. It's all about user experience, it's all about user experience when you touch Plone for the first time in order to try things out.
AGAIN this is was only a representative example of the Plone user experience with Plone 5 0 and 5.1 at the moment.
And this is one reason why people move to others systems that just work for them - independent of Plone features, its security record or whatever. I tried several other systems over the last weeks from Odoo to Wordpress for some simple landing pages. At least for Wordpress I installed dozens of themes and I never found such obvious issues that I found in both cases within one minute in Plone with very little test magic (just resizing the browser windows).
I am not the only one with similar feelings and the perception that some of you core developers are sitting on the moon and care about nothing outside. The current development process from outside appears completely headless with a lack of vision and concepts. Instead of addressing the core problems we see experiments like Webpack integration, headless Plone etc...no issue with experiments and thinking into different directions but at Plone core development at the moment is without direction, without commitment, without resources.