Skip to content

fix: autofill on server side #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

mosespace
Copy link
Contributor

Fix: Autofill on Server Side

This issue has been successfully resolved by implementing a fix for the server-side autofill functionality as seen in gh-40 . Previously, there were inconsistencies and error messages when trying to fill in the form, causing inconvenience and inaccuracies in data entry. With the recent fix, users can now experience a seamless and accurate autofill process on the server side. This improvement ensures that relevant data is automatically populated with precision, enhancing user efficiency and reducing manual data entry errors. Our team should thoroughly test and implemented the fix to guarantee a reliable and efficient autofill experience. Thanks!

@netlify
Copy link

netlify bot commented May 22, 2023

Deploy Preview for pyconug ready!

Name Link
🔨 Latest commit 0879310
🔍 Latest deploy log https://app.netlify.com/sites/pyconug/deploys/646b89a818425d000802b65c
😎 Deploy Preview https://deploy-preview-47--pyconug.netlify.app/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@HassanBahati
Copy link
Member

hi @mosespace thank you for opening this pr

  1. please elaborate more on autofillling on server side
  2. please guide on how the changes in this PR can be tested out

@mosespace
Copy link
Contributor Author

Attention:

Hello, @HassanBahati It appears that using chrome causes the error message to appear. I've tested it on various browsers, and to my surprise, it functions flawlessly. However, it seems that after completing out the form, nothing is sent; instead, a blank email window is opened, requiring the user to input their message again.

@HassanBahati
Copy link
Member

Attention:

Hello, @HassanBahati It appears that using chrome causes the error message to appear. I've tested it on various browsers, and to my surprise, it functions flawlessly. However, it seems that after completing out the form, nothing is sent; instead, a blank email window is opened, requiring the user to input their message again.

ohh that could...i have been testing this on chrome..

please share screenshorts/screencasts of what your test results are like on the other browsers

@HassanBahati
Copy link
Member

also please elaborate more on autofillling on server side....how this is happening and how it is being implemented..

from what i see happening is that the changes here are addition of autoComplete="on" attribute on the input tag

please help me understand how its translating into autofilling on server side

@mosespace
Copy link
Contributor Author

This preview is of Fire Fox

image

@mosespace mosespace closed this May 23, 2023
@mosespace mosespace reopened this May 23, 2023
@mosespace
Copy link
Contributor Author

also please elaborate more on autofillling on server side....how this is happening and how it is being implemented..

from what i see happening is that the changes here are addition of autoComplete="on" attribute on the input tag

please help me understand how its translating into autofilling on server side

On the server side, autofilling often combines client-side input with server-side processing. One of the ways to enable autofilling in HTML forms is by using the autoComplete="on" attribute, as I previously indicated. This attribute tells the browser to offer autofill suggestions based on previously entered data when it is added to an input tag.

I hope this explanation helps clarify how autofilling on the server side works. Let me know if you have any further questions!

@mosespace mosespace closed this Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants