Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why aren't mobile browsers supported?... #56

Open
brandonros opened this issue Jun 3, 2016 · 2 comments
Open

Why aren't mobile browsers supported?... #56

brandonros opened this issue Jun 3, 2016 · 2 comments

Comments

@brandonros
Copy link

No description provided.

@tejacques
Copy link
Owner

It's due to the way that iOS and Android handle multiple tabs. All but the displayed tab(s) have their JS frozen, so if you're relying on other tabs to relay requests and communicate, they won't.

I have a strategy to try and work around this, but the use case isn't as compelling because you can't share resources among the frozen tabs anyway.

@massaroni
Copy link

massaroni commented Sep 5, 2018

if you're relying on other tabs to relay requests and communicate, they won't.

If crosstab were running on a mobile browser, would the active tab's outbound messages queue up for the frozen tab, so that the frozen tab could read them all when it un-freezes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants