On Monday, 3 August 2026 23:26:46 Pacific Daylight Time Eskil Abrahamsen Blomfeldt via Development wrote: > However, I do think we should also consider ways of changing the default in > Qt 6 lifespan. We have to prioritize backwards compatibility, so we can't > change it unconditionally for everyone. My idea so far has been that we > could add application profiles which govern how defaults and behavior are > chosen. With the default "compatibility" profile, backwards compatibility > would be the priority like before. But for applications explicitly choosing > a "security" profile, we would be able to change defaults and behavior > between releases as long as we think it strengthens the security of the > application by avoiding common pitfalls. Security-sensitive applications > would pick this profile and accept the extra price of sometimes having to > update their code.
I agree on attempting to find a solution in Qt 6.x, but I don't think an application-wide setting is the solution. That would apply application-wide to third-party widgets, which may then look broken because they were using AutoText. We may want to look at #define defaults instead. > I might make a session for this in the Contributor Summit, actually. It > would be nice to hear if there are other ideas. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCG - Platform & Sys. Eng.
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
