Closed Treora closed 7 years ago
Hey @Treora
I tried it out with query-in-url
-branch and it's not working for me on chrome.
Though I may expect something different than you actually did.
When typing a query in the search field, the url in the address bar automatically changes to something like that:
chrome-extension://ikhdjbhnddpfbfaompkhmlbhgchogffh/overview/overview.html?searchQuery=test
It stays empty though.
Did you build and reload the extension? It does work like that for me.
Oh of course; the URL is not visible when viewing the overview as a new tab (I opened it with Ctrl+Y or the browser action button).
Oh of course; the URL is not visible when viewing the overview as a new tab (I opened it with Ctrl+Y or the browser action button).
Yes, I just figured and wanted to add that to my description :) Is that a bug or restriction?
Oh of course; the URL is not visible when viewing the overview as a new tab (I opened it with Ctrl+Y or the browser action button).
Yes, I just figured and wanted to add that to my description :) Is that a bug or restriction?
That's just what Chrome|ium does. It still works fine though. E.g. if you follow a link and go back, your query is still there (thus fixing your complaint in #52).
The UI logic should not have to bother about which pieces of state are exposed in the location query (in my opinion). Therefore, this commit introduces a listener that bidirectionally syncs variables between the state and the window location.