Hi Yui
I’m not suggesting WordPresss.org makes HTTPS compulsory, but the facility should be in the Core, not as a plugin – we all know plugin support comes and goes.
As of October, Chrome (the market leader) will be marking ALL pages with the ‘insecure connection’ if there is an entry field … this includes any ‘Search’ box, the from/to boxes for route planners etc. Other browsers follow where Chrome leads.
The WordPress.og and WordPress.Com sites are https … so why is it missing from the Core? I’ve looked at Dev chats recently, and I haven’t even seem it mentioned!
From the point of view of visitors to a website, https transport layer security is far more important that Gutenberg. And who do we build websites for?
Check the HTTPS topic tag, and there are lots of people struggling to get https working properly … about time the Core development teams woke up to the problem.
PS. My IT background (30+ years corporate and SME) has been on the customer support and account management side. While I understand lots about the technology, I’m not a programmer or coder (never mastered the skills) … I’m a user advocate … so that is my perspective.