Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Error and retry are included in the history pulldown #2856

Closed
luixxiul opened this issue Aug 2, 2016 · 3 comments
Closed

Error and retry are included in the history pulldown #2856

luixxiul opened this issue Aug 2, 2016 · 3 comments

Comments

@luixxiul
Copy link
Contributor

luixxiul commented Aug 2, 2016

Describe the issue you encountered: Error & retry are included in the history pulldown

Expected behavior: I think they should not be there. Either a page only successfully loaded or a failed page should.

@luixxiul
Copy link
Contributor Author

luixxiul commented Aug 6, 2016

WDYT? /cc: @bsclifton

@bsclifton
Copy link
Member

bsclifton commented Aug 7, 2016

Good catch- our "about:" pages are counted in history.

We could try interesting approach which I had thought about a few weeks ago:

  • Creating an empty webview tag (not bound to any frame object).
  • Error happens- load the about:page in that webview's webcontents object
  • We could then temporarily:
    • remove the active webview from the webviewContainer in the frame which had the error
    • add the webview which points at the about:page into the webviewContainer. React would then render that one instead.

Once the frame is "resolved" (person goes back or forward in history; clicks acknowledge on a cert error page, etc), then we'd swap it back.

I don't think this would be too difficult to do, although it does add extra complexity to the code. I'm going to self-assign and give it a shot 😄

cc: @bridiver, @diracdeltas

@bsclifton bsclifton added enhancement polish Nice to have — usually related to front-end/visual tasks. labels Aug 7, 2016
@bsclifton bsclifton self-assigned this Aug 7, 2016
@luixxiul
Copy link
Contributor Author

luixxiul commented Nov 4, 2017

It's been fixed 😄

@luixxiul luixxiul closed this as completed Nov 4, 2017
@luixxiul luixxiul added bug and removed polish Nice to have — usually related to front-end/visual tasks. labels Nov 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants