So I think if extension can ask MacPass to perform the login, it is better than doing it itself. There are mainly two advantages over this process:
Extension itself cannot perform {ENTER} or {TAB} the right way. Although it is possible to find some fixes, still the result might be different. So if users use an extension to perform login, they will have different experience compared to using autotype from MacPass.
In many cases you can define a custom autotype rule that can handle the login process for a domain. Currently the extension has no info about these custom autotype rules and hence always performs the normal login procedure, {USERNAME}{TAB}{PASSWORD}
Considering these issues, I would recommend to have a handler that accepts a login from the extension side and performs autotype to the currently selected window.
So I think if extension can ask MacPass to perform the login, it is better than doing it itself. There are mainly two advantages over this process:
Extension itself cannot perform
{ENTER}or{TAB}the right way. Although it is possible to find some fixes, still the result might be different. So if users use an extension to perform login, they will have different experience compared to using autotype from MacPass.In many cases you can define a custom autotype rule that can handle the login process for a domain. Currently the extension has no info about these custom autotype rules and hence always performs the normal login procedure,
{USERNAME}{TAB}{PASSWORD}Considering these issues, I would recommend to have a handler that accepts a login from the extension side and performs autotype to the currently selected window.