EasySocial Dropdown Login Module does not Prefill
By Neel on Monday, 10 November 2014
Posted in General Issues
Replies 4
Likes 0
Views 1K
Votes 0
I noticed with the Login drop-down box that comes with EasySocial Dropdown Menu Module, the browser does not pre-fill the saved username and password even when these details are saved. The prefill works in the standard login page or when I go to the dashboard but its just the drop-down login in the module that does not prefill. I tried this from both Chrome and Firefox and same behaviour is there.
Hi,

Try removing autocomplete="off" in the file /modules/mod_easysocial_dropdown_menu/tmpl/default.php

This works for me in Firefox but in Chrome, due to the fact that the form has a display:none, the form seems to be not auto filling. Removing the display:none on the dropdown however, Chrome will then autofills it properly.

I am not sure if this is a Chrome issue. Will have to research more on this.

UPDATE:

Upon further testing, it doesn't work on Chrome due to a technique of popbox that we are using. The form is cloned from an existing form that is embedded on the page, and when the element got cloned, Chrome seems to not populating the form properly. This is because forms are populated only on page load, and any forms created after that won't get populated.

I will have to discuss this with the developer to see how to remedy this.
Jason Rey
·
Tuesday, 11 November 2014 11:04
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Jason, you are right. Once I remove autocomplete="off" from the input fields, it works in Firefox and even partly in Internet explorer (with IE it completes after username is filled in), but it doesnt work in Google Chrome and Safari. Looks like its different for webkit browsers and interesting that it doesnt work in them. Did you find anything?
Neel
·
Thursday, 13 November 2014 20:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Jason Rey wrote:
UPDATE:

Upon further testing, it doesn't work on Chrome due to a technique of popbox that we are using. The form is cloned from an existing form that is embedded on the page, and when the element got cloned, Chrome seems to not populating the form properly. This is because forms are populated only on page load, and any forms created after that won't get populated.

I will have to discuss this with the developer to see how to remedy this.

Just now I read the update. Good you identified the cause. I'll wait to hear from you whenever you get chance to discuss this with the dev.
Neel
·
Thursday, 13 November 2014 20:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Unfortunately, this is a Chrome issue and temporarily we do not have any short term solution to this.
Jason Rey
·
Monday, 17 November 2014 12:31
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post