1 Feb
2022
1 Feb
'22
7:16 p.m.
Nikolay Sivov nsivov@codeweavers.com wrote:
It looks like assigning a reviewer for a patch doesn't work very well. Can the situation be improved somehow? Is there any responsibility of a reviewer for ignoring the assigment?
Since this is exactly the same as the original patches, same concerns expressed initially apply for it as well.
I didn't see any real concern. Could you please try to be more specific?
I'm planning to work on this, unfortunately can't give exact time frame when it will be done.
I already suggested a solution for a bunch of real world WPF applications that rely on this behaviour: the test shows exactly what's the problem, and the patch provides the fix. What's wrong with this approach? What would you suggest to do instead?
--
Dmitry.