The good news: changing the default breaks surprisingly few tests.
The bad news: it’s not because the whole thing is particularly well tested
So, I now added a bunch of tests for the whole thing that also highlight the
two cases that are UX-bugs via QEXPECT_FAIL:
https://codereview.qt-project.o
Of course. The +1 only applies to Qt 6, and not any versions of Qt 5 :)
Cheers,
Lars
> On 1 Jun 2021, at 14:58, David Skoland wrote:
>
> To be clear: +1 to changing default behavior in 6.2.
>
>> On 1 Jun 2021, at 14:57, David Skoland wrote:
>>
>> Not thrilled about subtle default behavior ch
To be clear: +1 to changing default behavior in 6.2.
> On 1 Jun 2021, at 14:57, David Skoland wrote:
>
> Not thrilled about subtle default behavior changes like this, there’s no
> knowing how it may break certain apps. I suppose most people will be
> upgrading from 5 to 6.2 and will to some de
Not thrilled about subtle default behavior changes like this, there’s no
knowing how it may break certain apps. I suppose most people will be upgrading
from 5 to 6.2 and will to some degree expect having to make some adjustments
and the proposed behavior is definitely desirable, so I’m giving th
On 28 May 2021, at 16:37, Konstantin Shegunov
mailto:kshegu...@gmail.com>> wrote:
On Fri, May 28, 2021 at 2:13 PM Volker Hilsheimer
mailto:volker.hilshei...@qt.io>> wrote:
Hey Widget fans,
Hola,
I need your opinions on https://bugreports.qt.io/browse/QTBUG-59888
The UX resulting from our (str
