зеркало из https://github.com/mozilla/gecko-dev.git
c1e5d642df
We use `ShellExecuteByExplorer` to open a uri because applications may not support the mitigation policies inherited from our process. Unlike Firefox, Thunderbird runs `ShellExecuteByExplorer` to launch a browser to open an HTTP/HTTPS uri. If a uri includes credentials like http://user:password@domain.com/, `ShellExecuteByExplorer` succceds, but explorer.exe refuses to open the uri by design. In this case the fallback to `ShellExecuteExW` does not happen because the API is async and no error is returned The proposed fix is to skip `ShellExecuteByExplorer` if it's Thunderbird. Because Thunderbird does not apply additional mitigation policies which may cause compat issues, we don't need to run `ShellExecuteByExplorer` in the first place. Differential Revision: https://phabricator.services.mozilla.com/D67339 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
base | ||
docs | ||
exthandler | ||
prefetch | ||
moz.build |