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

Dialog (A script on this page may be busy,...) is stuck #34

Open
taboca opened this issue Nov 27, 2013 · 1 comment
Open

Dialog (A script on this page may be busy,...) is stuck #34

taboca opened this issue Nov 27, 2013 · 1 comment

Comments

@taboca
Copy link

taboca commented Nov 27, 2013

I would like very much to help with the following issue:

When JS is slow (use case is open Google Analytics Real Time and leave for 1-2 hours or more) a "JS is busy dialog" shows up. I think that this is an area that we can improve this custom version of the Firefox OS. The major issues/observation:

  • The dialog appears covering the whole screen, similar to an app view
  • The dialog won't go away either clicking Continue or Stop Script
  • An & amp appears next to the check box that says "Don't ask me again"

My proposal, on how to tackle this and add value to APC and custom Firefox OS versions:

  1. We find the place in Firefox OS or Gaia code that manages this dialog.
  2. We propose patch for initial solution (or workaround) and to see if this is on Firefox OS code, Gaia, or if it is in APC.

And I would like to use this, and possible initial fix, to propose a further research or investigation if we need to have these kind of screens under a more managed scenarios. One use case I can think of is for TV appliances or other scenarios where a direct user touch experience is not in place. For these cases, and perhaps also in some other real-time cases, we could improve user experience by having these events to be managed (for example, like the concept of intents). So by having this kind of events going through a certain channel of control, we could improve in many ways:

  • Allow developers to discover new ways to decide about this dialog condition
  • Allow systems to reach new user cases: TVs other systems where no direct input exists
  • Allow accounting on the amount of times such even happens
@ntlc
Copy link
Contributor

ntlc commented Dec 2, 2013

@taboca Thank you for the proposal. Can you explain why this should be applied only to custom FF? I'd advise to propose this directly to Mozilla. The JS is busy issue happens even with FF browser in different OSes, it would be FF related IMO.

However, if you prefer to start with APC before tackling a more general approach, pls feel free to submit patches here, or to a separate branch, our team will perform review and merge. Thanks.

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

2 participants