Field attributes do not show at: https://wwws.mint.com/login.event
Closed this issue · 3 comments
Separated from Issue #2 to focus just on the Mint self-contained logon page.
If you visit Mint.com and click the "Log In" link it will reveal an input form. The add-on works on this form. However, if you click the "Login In" button to submit the form and the fields are blank or on an error you are sent to a stand alone logon page at https://wwws.mint.com/login.event
Before reaching "login.event" you are first redirected from: https://wwws.mint.com/loginJumper.event
On https://wwws.mint.com/login.event if you have enabled "Show the field attributes when a text input field has focus?" selecting and input field will not add the form fields attributes to the title.
Diagnosis
So far in my research I have noted the following things.
The add-on is supposed to add a focus event. When using developer tools or firebug, once the page is loaded it does not have any of the events from the add-on present.
Once the page has finally loaded at https://wwws.mint.com/login.event if you view the source you do not actually see the log in form as part of the source. If you disable JavaScript the form does not even load. This form is injected by a JavaScript file Auth-XXXX.js where XXXX seems to be random number for cache management purposes.
Since the form is added after the add-on script has executed, the event will not be added. The add-on currently does not handle this because it would require observing the entire page for DOM mutations which could have a noticeable performance impact on JavaScript heavy sites. This may also be an issue on other sites which use Frameworks such as Meteor where a lot of the content is added after the DOM is initiated.
For the time being, it does not look like this can be resolved directly, but you can still use the add-on if you logon from the main page. This class of problems has been a known issue per the FAQ.
In my dev environment I have experimented with MutationObserver that tracks on <body />. Even on this simple mint log in page it fired over 20 times. While it may address this problem, on JavaScript heavy web apps this has the potential to have noticeable performance impact.
I will consider implementing this as a user definable option in the future, however, I want to balance performance and configuration complexity. If FireFox provided a secondary menu for advanced user configurations, it would help with all of these extra cases. I will need to also find some JavaScript heavy sites to study the performance impact in more detail. MutationObservers are designed not to have a large impact, but I have some concern when attaching so high up the DOM.
Repo Maintenance I am closing tickets for specific sites that are more than three years old, as those sites are likely different now and the problems may no longer exist. If this is still an issue with a modern browser version and the current version of the add on, please response and we can reopen the ticket.