-
Notifications
You must be signed in to change notification settings - Fork 975
about: pages fail load in private tabs #1817
Comments
about:error
instead of about:newtab
about:error
instead of about:newtab
actually looks like any |
opening a private tab triggers a did-fail-load event with for addressUnreachable (-109). Not sure why |
it's really only failing the provision load, but electron fires did-fail-load and did-fail-provisional-load in that method. I'm not sure why it only happens with private tabs, but I have a workaround until we can figure it out. |
maybe not. The workaround still doesn't actually load the page for about:preferences and other non-blank pages |
This is actually not a new issue, we just never noticed that the page didn't actually load. Trying to view about:preferences in a private tab results in a blank page. It probably doesn't make sense to view about pages (other than newtab) in a private session because they don't have their own set of persistent preferences, bookmarks, etc... The workaround I have will at least show newtab instead of error, but I think we should open other about:* pages in a new tab if the url is manually entered into a private tab. about:certerror will also display a blank error page in a private tab. |
Moving t 0.10.1 since there's as workaround |
Thanks @bridiver. I believe at least the following pages should be displayable in a private tab:
In FF, all the about:about pages are displayable in a private window. In Chrome, at least settings, history, and bookmarks (but not downloads) open in a regular window if you try to open them in incognito mode. |
related #1817 auditors: @diracdeltas
about:error
instead of about:newtab
Moving t 0.10.5 for now. |
Was due to incognito manifest setting of spanning not allowing main frame url loads. |
Test plan
Original issue description
started happening today or yesterday
The text was updated successfully, but these errors were encountered: