https://bugs.kde.org/show_bug.cgi?id=477234
--- Comment #3 from Juraj <jurajora...@mailo.com> --- Hello, > Does that mean it makes no sense to report new bugs in Falkon > for all current and maybe future Falkon versions which are still based on QT5 It means that Falkon is being ported to Qt6. > Should I wait with reporting new bug issues until the Falkon source > code will be based on QT6 and can locally get cloned using git? The "master" branch in git is already Qt6 only and most of the stuff works just fine. > Or does it depend on specific software elements, like (specific) browser > extensions, > if it makes sense to currently or still test them or not? Well, the extensions in the store[1] will probably not work, unless they are ported as well. Most of the other stuff should work, there are mostly only the things which are harder to find. It is very helpful to get a beta version a run and report bugs, even if they will be reported 10 times. Honestly I overlooked the extensions while porting, it compiles so we can ship it. > Are there specific browser extensions embedded into the Falkon QT5 based > source code which will not be available anymore in the future QT6 based > Falkon source code? All extensions shipped with Falkon should be ported to Qt6. There is a regression with StatusBarIcons in the Network availability icon, it does not work yet since this needs to be rewritten and some features added to Falkon itself. But since Falkon is part of KDE Gear we hit the feature freeze for 24.02 version and will strive to fix this and more for 24.04 release. Thank you, Juraj PS: Hope it makes sense. PS:2 All bugreports are welcome, even if there is no reply I read all of them. [1]: https://store.falkon.org/ -- You are receiving this mail because: You are watching all bug changes.
