What's wrong with HTTPS Everywhere?

Question

Browsers

Hello.
I decided to dig into HTTPS Everywhere , installed the Chrome extension of the same name, and was surprised to find that they have a huge database inside with a list of domains on which you need to replace http with https.
In this regard, the question is: why is it so? It seemed to me that the "concept" of HTTPS Everywhere was to simply drive everyone to https, regardless of what exactly the user entered as a url.
But suddenly there are whitelists.
Why is it so? Is the implementation flawed, or did I misunderstand something in the idea?

Answer 1

These are the site owners who are flawed and unable to set up HTTPS. And the addon developers do not want users to receive an error in the browser, so they have to keep these same lists.