Support for HbbTV about history

[mjackson]

What mechanisms do you have for persisting state between page loads on an HbbTV? We should be able to easily create a custom state storage engine that works on those devices. For example, memory history creates its own state storage, which is really just a hash.

[taion]

@soutar Are you using hash history or browser history? If you're using hash history and not persisting things in history state, you might be able to just set queryKey: false.

[mjackson]

Any intention of following up here @soutar? Please close if not.

[soutar]

Yes, I had intended to reply here but had forgotten. Sorry @mjackson, and thanks to both you and @taion for your replies.

We discovered that the issue we were having with sessionStorage was actually device-specific and we were able to get around it. After doing some spec reading, I found that the OIPF Web Standards TV Profile (essentially part of HbbTV) mandates that "Terminals SHALL support the Web Storage API", so it's safe to say that this issue is not your responsibility.

I'm happy to close this off as history & react-router both work flawlessly on standards-compliant HbbTV devices. Thanks for providing such high quality packages 👍