Earlier quoted context omitted.
The rendering engine: Chromium had to be kept "libre", because khtml/Webkit was LGPL. The browser: Chrome. could be kept closed because the LGPL allow the integration of libre libraries in closed products as long as the library itself remains "libre". In this case the library is the renering engine: Chromium. As a counter example MacOS was built on top of decades of work on the BSD operating system and Apple is under…
Your logic seems faulty. Let me see if I have this right: >For some of us that is unacceptabme . 1. So, Apple, creator of macOS, "the most valuable company on the planet", followed the rules of the BSD licence,and that is unacceptable? But, Google, a company that is also highly valuable, and the creator of Chrome, also followed the rules of the LGPL licence, but that is acceptable?
Yes, forced to follow. Its a sign in retrospect that KDE should have used an even stronger license. I don't know if AGPL existed then, but if I start a browser today, I'd license it as AGPL. If you want to use the project, you have to release your changes to your users. If you don't want to do that, good luck, spend millions on developing an equivalent application in house. Thats the beauty of GPL like licenses.
With BSD companies are under no obligation to release their changes, and like any self interested party, most don't.