Marco Bonardo fb0662edda Bug 1628906 - First search in a tab from location bar could trigger an "Invalid URL" error page. r=Gijs,nika,mattwoodrow ... Before 1496578, URIFixup::keywordToURI used to do a synchronous IPC call to be able to access search engines from the content process. Consumers of URIFixup didn't care. Bug 1496578 moved the IPC messaging to the callers, in particular nsDocShell, but assumed nsDocShellLoadState wasn't loading from content. It looks like in some cases it does, so this adds another sync IPC call for GetFixupURIInfo. The total numer of sync IPCs should not change from before Bug 1496578, URIFIxup was just doing it internally, while now it happens at the call point. Note the long term plan would be for these docshell objects callers to just handle URIs, while the UI code should do fixup. Bug 1375244 tracks the removal of these sync IPC messages. Differential Revision: https://phabricator.services.mozilla.com/D70607 --HG-- extra : moz-landing-system : lando		2020-04-15 22:39:38 +00:00
..
app
chromium
contentproc
glue
gtest
ipdl	Bug 1628906 - First search in a tab from location bar could trigger an "Invalid URL" error page. r=Gijs,nika,mattwoodrow	2020-04-15 22:39:38 +00:00
mscom
testshell
moz.build
pull-chromium.py