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

Better error handling for IE11 users accessing large dashboards #6531

Closed
tbragin opened this issue Mar 14, 2016 · 6 comments
Closed

Better error handling for IE11 users accessing large dashboards #6531

tbragin opened this issue Mar 14, 2016 · 6 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience IE11 PR sent

Comments

@tbragin
Copy link
Contributor

tbragin commented Mar 14, 2016

Today, when IE 11 users access large dashboards, they hit the following error message: #4919

We understand the root cause, but the fix is not easy and may take a while to arrive at: #3947

Known workarounds are:

  • Do not use IE11 to load or modify large dashboards
  • Break up bigger dashboards into multiple smaller dashboards
  • Allow users to access big dashboards using shortened URLs (but if they go to modify them, they’ll still hit this problem)

This ticket calls for handling this error explicitly and showing a user an error message directing them to use another browser (instead of crashing) until resolution below is implemented.

@w33ble
Copy link
Contributor

w33ble commented Mar 14, 2016

FYI, the error isn't limited to modifications, as simply loading the dashboard ofter triggers a "modification" as gridster updates the layout for your screen. This is why users can and do see the error immediately upon loading dashboards.

@tbragin
Copy link
Contributor Author

tbragin commented Mar 14, 2016

Thanks, @w33ble, I updated the workarounds above

@tbragin tbragin added P1 bug Fixes for quality problems that affect the customer experience and removed release_note:enhancement labels Mar 17, 2016
@tbragin
Copy link
Contributor Author

tbragin commented Mar 17, 2016

Btw, relabeling to "bug", since as discussed with @rashidkpc not handling a stack trace and showing it directly to a user should be considered a bug.

@simianhacker
Copy link
Member

This bug needs to be fixed in the next patch release for 4.5.1

@georgewfisher
Copy link

I'm seeing the same error on Edge 13.1 (it isn't restricted to IE11). This is odd given that Edge is supposed to support longer URLs.

@georgewfisher
Copy link

correction: Edge appears not to support longer URLs after all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience IE11 PR sent
Projects
None yet
Development

No branches or pull requests

6 participants