Describe the bug; what happened?
I have a login page in a asp.net core razor page with a fast-text-field for the username and one for the password. Both have the name and ID set so that they should be mapped to the according Bind Property of the model. When I fill in both values and hit send in FireFox I do get both values in my page model on the server. In Chrome and Edge (Chromium based) both values stay null. When I replace the fast-text-field with a normal input or an bootstrap input it works as expected.
Also maybe related (if it's not let me know and i file a bug for that separatly: Autofilled credentials aren't shown in the text-field aswell. But when I navigate to a page where there are saved credentials in firefox and just click login to submit, I do get the correct autofilled values although in the UI both fields are empty. In Edge and Chrome I get null (as in this case expected since no value is to see as well).
What are the steps to reproduce the issue?
Example:
What behavior did you expect?
Entered value are correctly sent to server.
If applicable, provide screenshots:
In what environment did you see the issue?
Is there any additional context?
Thanks for the detailed description @NPadrutt! This looks related to https://github.com/microsoft/fast/issues/3550 - working on a fix now.
@nicholasrice Can we close this as done now?
I had a look at the new version and the main issue, that data isn't sent to the server is fixed. Thanks for that!
The second one I mentioned with credentials not being autofilled (or offered to safe in the browser for that sake) however still exists. Should I create a new separate issue for that?
@NPadrutt Yes, if you don't mind, please create a separate issue for the credentials bug. We'll need to do some investigation on that to see if it's something we can fix.
I'm going to close this issue out in favor of the new issue related to creds.
Done #3614
@EisenbergEffect maybe a stupid question but this was fixed with the 1.7 version of fast-components. I noticed that the error still persists in the latest fast-component-msft package (1.6). Is that because of the transition to fluent and should be fixed with 0.1 once that is live or do I have to create a separate ticket for the fluent package?
@NPadrutt I believe the fix was made in foundation so we should see it propagate to the FluentUI package. If you're using NPM you could try to test with that version today. If you're using the CDN link from unpkg, there's a PR up to fix that now.
@chrisdholt Ah, I see. I tried the unpkg version, but the. i will try again tomorrow (or when it os fixed).
Thanks for the very quick answer! :)
@chrisdholt Ah, I see. I tried the unpkg version, but the. i will try again tomorrow (or when it os fixed).
Thanks for the very quick answer! :)
No worries! If we can get the fix in quickly I'll see if I can kick off a publish to get this out today. If not, the Fluent build should publish automatically overnight!
@NPadrutt, the CDN link should be working now, so you should be able to test. Let me know if you run into problems with the link.
@chrisdholt works as expected after adjusting all the components from fast- to fluent-, including the fix for this issue here. thanks! :)