Um, many do, actually, albeit without any specific theming applied. But that’s irrelevant anyway.
(Note: I myself don’t use any of the Manjaro theming, except for the default Manjaro GRUB theme and the default Manjaro SDDM theme. But that too is irrelevant.)
Yakuake asks for it’s key on startup. On Manjaro it’s skipped to not to annoy users as it’s started by default.
So, just keep it at F12 then. If the user wants to change that later, then nothing’s preventing them from doing so. 
I propose we make a public vote (like the one included in every release announcement) to help decide if we should include Yakuake in the default installation.
It is very useful but I’m not convinced it’s a good thing to have two different terminal emulators installed by default.
I think @LordTermor said he would bring yakuake back.
Technically it’s one. Yakuake is just a skin for Konsole.
Not only that, but there already are other terminal emulators installed, which I believe would come supplied with X.Org.
On my system here, I’ve got xterm and uxterm installed, and I sure didn’t install those myself.
Is there a Breeze/Breath GTK Theme for Plasma?
I removed skipping a first setup from config.
Breeze-gtk is in the repo, the breath theme is already installed
In new images (post-21.1) breeze-gtk is installed by default.
Steam screenshots. Firefox dev tools.
Okay, if we’re going to be pedantic…
Not everyone using Manjaro is a web developer.
Not everyone using Manjaro is a gamer.
A terminal emulator is an indispensable component of every graphical environment running on top of a UNIX system, and every user will sooner or later have to make use of it, whether they want to or not.
So, is it then preferable to change a certain default shortcut for a system component that virtually every Plasma user will be using in favor of something very specific that only a subset of our user base will be using?
Just keep F12 as default for yakuake in ISO.
Let people change the default shortcut themselves if they don’t like it after Manjaro KDE installation.
I feel the pain, hitting F12 during CSgo is a reflex I’ve had to suppress.
Thank you, Bogdan! 
In which web browsers do you have problems with F12 does not open yakuake?
firefox
ungoogled chromium
opera
are not affected: I bringed their window active one by one and tested in those 3 browsers: I see my global shortcut F12 to call konsole works well and does not open DevTools of web browser. F12 is obsolete shortcut to open devtools in IE6 may be in IE11, which is a years obsolete. May be F12 was in FireFox some day ago.
Why to do not use classical Ctrl+Alt+I to open DevTools and to introduce issue where it should not be?
Modern frontend developers does not use F12 to open Devtools as is initialy works not in every browser and there is universal key combination to open it in most current browsers (I do not know how about Safari).
I believe that F12 should be will good for yakuake. Please keep it for the app.
Breath GTK theme is no more.
I changed my Yakuake bind to Meta+F12. Takes care of both Steam and Firefox conflicts, and is still pretty easy to perform.
I’m using Meta+Enter personally. But it depends on where Meta is located.
