Domain inversion force known part of OR-ed when some are unknown
I got a case where I put a filter on a One2Many. The filter is a OR-ed domain on two fields like ['OR', ('a', '=', v), ('b', '=', u)].
The editable tree view displaying it has only 'b' field not 'a'. The domain inversion force the value of 'b' to u. I think it is a wrong behavior. In such case the domain inversion should just consider that the domain will be valid.