BTW, if we still get trimming behavior issues in 2.2.2, we will change the trimming API:
Currently, trimming is considering: intersections, and user click position, but not in the same step.
We should change it into a unified API to do trimming in one step, with both set of information.
This is a way to handle complex trimming in the future, like closed curves, or self-intersecting cuves.