https://bugs.kde.org/show_bug.cgi?id=474945
--- Comment #8 from pmqui...@proton.me --- Unfortunately, the issue is getting zero traction even for triage on the chromium side. I'd speculate that this may be due to the fact that this only affects KDE plasma, and so chromium developers using GNOME would need to switch to repro. I understand that this is a chromium issue, but this only affects KDE Plasma users. As a result, it's a significant user experience impact for any plasma users who are using any chromium based browser, be it chrome, chromium, brave, vivaldi, etc. I imagine that's a significant chunk of plasma users. Given that there's no traction on the chromium side, I'm bumping this issue to ask about whether it falls within KDE policies to at least do the initial triage for this issue. This issue impacts a tiny fraction of all chromium users, but a significant portion of KDE users are impacted. So even though the responsibility for triage falls on chromium, as a practical matter that simply is not happening, so it may behoove KDE to do the initial triage here. -- You are receiving this mail because: You are watching all bug changes.
