fix(material/form-field): outline label position

[adumitrescu-plenty]

Fixes the outline label position when a prefix is present and the form field is not yet rendered.

Fixes #29064

[crisbeto]

By the way, are we sure that it resolves #29064? The example there isn't using shadow DOM at all.

[adumitrescu-plenty]

By the way, are we sure that it resolves #29064? The example there isn't using shadow DOM at all.

No but the actual check fix it by narrowing down the fact that is not yet rendered. Which is the root cause of the issue. I tried eliminating the possible places that it could be (shadow dom, document or itself) which left us with the case where the element is not yet rendered thus the functionality inside the form field that gets the width of the prefix will return 0 for the prefix container which is not yet rendered. Hopefully this makes sense.

[crisbeto]

This had to be rolled back, because it broke a test internally. I can't share much about it, aside from it being a form field inside of a sidenav that wasn't floating its label correctly anymore.

[adumitrescu-plenty]

This had to be rolled back, because it broke a test internally. I can't share much about it, aside from it being a form field inside of a sidenav that wasn't floating its label correctly anymore.

I'll try to see why and fix it

[adumitrescu-plenty]

@crisbeto any way I can help or test? Maybe we can try including the document check?

[crisbeto]

I can't run the test myself, I've only seen the failing screenshot. It has a sidenav with some form fields in it and one of them has the label on top of the prefix, similarly to how it failed for me when the check was broken inside the shadow DOM.

[adumitrescu-plenty]

@crisbeto I assume that is the case for any form field inside a side-nav. This is the case now as well. Check this https://stackblitz.com/edit/ad4b8f-dq4pmf?file=src%2Fexample%2Fsidenav-autosize-example.ts . I will try to see if I can fix this also

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}