Control: reassign -1 source:wxwidgets3.2 On Wed, Jun 07, 2023 at 09:49:19AM -0400, Scott Talbert wrote: > I think it would be okay to enable xtest support even though it doesn't work > under Wayland.
I think it'd be good to check with upstream if the "experimental" marker is out-dated, or still accurate, and if it's still accurate what the downsides of this are. I've opened a ticket: https://github.com/wxWidgets/wxWidgets/issues/23619 > However, this type of change doesn't seem appropriate for a > stable release (it's possible it might even cause an ABI change), so we'd > have to make it unstable after bookworm is released (this weekend?!). Thus, > the bug should be reassigned to wxwidgets3.2. Oh, I missed that this was reported in wxwidgets3.0 - thanks for spotting. I agree this should be reassigned - wxwidgets3.0 is gone from bookworm and newer and I really can't see the release team agreeing to enabling a new optional feature in a stable or oldstable update (and one of their criteria is severity important or higher). So we can only target addressing this for trixie at this point, so we can take the time to check with upstream. If it requires an ABI bump we'd need to do a transition so that's a key question. Cheers, Olly
