https://bugs.kde.org/show_bug.cgi?id=434709
--- Comment #2 from kavol <ka...@seznam.cz> --- (In reply to Juraj from comment #1) > Hello, > I tried this with Chromium and I got the same results. > Can you confirm that? > > In that case this issue could be closed and marked as upstream since it > originates in Chromium itself. pardon my ignorance, but what has Falkon to do with Chromium? I thought it uses QtWebEngine, so if the problem originates with code provided by Qt, it should be reported to Qt if Qt copies the code from elsewhere, then Qt should forward it to the origin if you're saying there is a shortcut, well, okay, then go ahead and report the problem where do you deem appropriate, but then we're losing track when will the fix hit downstream, if ever anyways, I'm just simple Falkon user, I see a problem when using Falkon, so from my POV, your attitude "not in our code, so just close this" really does not help to get rid of the problem - sorry if I got you wrong, I do not mean this negatively, I'm just trying to express myself that I just want to use the product and do not spend time studying its internals when you already know; well, to be honest, I believe I've already did my part by identifying the exact issue and reporting it, so that other users can benefit from the fix (if it gets fixed, but without even knowing the problem it can hardly go magically away itself) instead of swearing what a crappy product Falkon is, not displaying something ... -- You are receiving this mail because: You are watching all bug changes.
