- Issue created by @catch
- 🇮🇳India annmarysruthy
Given the potential GDPR implications and the increasing security expectations around personal data handling, Drupal.behaviors.fillUserInfoFromBrowser could be removed from form.js. I think this can be safely removed in a minor release as it doesn’t break core form functionality.
We could:
- Remove the fillUserInfoFromBrowser behavior entirely from form.js bypassing deprecations
- Split remaining behaviors into separate files with their own libraries
- Update dependencies in existing modules to reference the new libraries
- Add a change record documenting both the removal and restructuring
- 🇩🇪Germany jan kellermann
The original issue is #2409107 🐛 Do not prepopulate the user register form with the email address and username of the last person who registered using the same web browser Needs work (and is celebrating its 10th birthday soon). In this comment 🐛 Do not prepopulate the user register form with the email address and username of the last person who registered using the same web browser Needs work some module are linked which are using this functionality.
So I opened a ticket to find a fast lane to remove this in core, see #3498834 🐛 Dont use core's prepopulate function for core forms (Privacy) Active . Maybe we can quick bring this ticket to an end and then remove this from core general with deprecation in this ticket.
- 🇮🇳India annmarysruthy
Since this is being used in core and contrib modules, Can I create a CR and add a deprecation notice for Drupal.behaviors.fillUserInfoFromBrowser.
- 🇩🇪Germany jan kellermann
A draft for a CR → is already created. See #3498834 🐛 Dont use core's prepopulate function for core forms (Privacy) Active
- 🇬🇧United Kingdom catch
Marking duplicate of 🐛 Do not prepopulate the user register form with the email address and username of the last person who registered using the same web browser Needs work .