KDE’s current approach is to either integrate GTK applications as well as possible via Oxygen-GTK or to write a KDE front-end on an existing back-end (as with LightDM, NetworkManager, PackageKit, etc.)
In fact the main reason why there is no broad push for a KDE web browser (Konqueror and Rekonq are basically one-man shows these days) is that most KDE devs simply use Firefox or Chrome.
I'm not saying it is a flaw, just an experience. And good to hear it is being looked into, if only for the fact that people
That's because the current keyboard shortcut implementation is lacking and IIRC cannot easily be fixed without breaking binary compatibility. I believe it’s on the agenda to be fixed in KF5. The current implementation can’t handle two alternatives for global shortcuts. Therefore a default that works also with keyboards without multimedia keys is chosen.
Again: Distributors can change such defaults to target a specialized user group (e.g. one that has a higher likelihood of owning such keyboards).