Kristiyan Kostadinov

The idea of that function has always been that the `Point` it returns is where you want the top/left corner of the dragged element to be. It's how it worked...

So the (not well documented) assumption is that if you're using `constrainPosition`, you're in complete control over the positioning. `lockAxis` and `boundary` may end messing with it since they're all...

You'd have to offset it based on the position at which the user picked up the element, which I now realize isn't possible to read. I've opened up #25341 to...

Will be fixed by https://github.com/angular/components/pull/23931.

I spent a bit of time investigating this and I think it comes down to the fact that we make a lot of assumptions that the `ClientRect` of the various...

I can't say when the fix will be prioritized since we already have a bunch of commitments on our roadmap.

Makes sense, I'll see what I can do.

@jelbourn I did some exploration into it. The problem with using an `ng-template` is that we count on the individual options to provide their text which we then use to...

We do have the `mat-select-trigger` component already which lets you override the trigger.

An alternative approach can be to hand over all rendering to Material. e.g. the user provides the data source and a function that determines what the output should look like:...