Currently, when phoenix is opened in the browser, it will try to load the last active project. But due to chrome security policy, if the opened project is using fs native access APIs, the local will fail as at least one user interaction in the page is required before the fs access apis can be called. So we have to change Phoenix project open experience as follows:
-
When phoenix loads, the default project is always opened.
-
A project selection dialogue will open if a native file system access API folder is the current project to open and the fs access API errors out 
-
We should finalize the design of the project selection dialogue.
-
Should the dialogue always appear for ux consistency instead of only at project load failure time?
Currently, when phoenix is opened in the browser, it will try to load the last active project. But due to chrome security policy, if the opened project is using fs native access APIs, the local will fail as at least one user interaction in the page is required before the fs access apis can be called. So we have to change Phoenix project open experience as follows:
When phoenix loads, the default project is always opened.
A project selection dialogue will open if a native file system access API folder is the current project to open and the fs access API errors out
We should finalize the design of the project selection dialogue.
Should the dialogue always appear for ux consistency instead of only at project load failure time?