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

Errors with IE11, in hypergrid #27

Closed
voltcode opened this issue Feb 6, 2018 · 2 comments
Closed

Errors with IE11, in hypergrid #27

voltcode opened this issue Feb 6, 2018 · 2 comments

Comments

@voltcode
Copy link

voltcode commented Feb 6, 2018

using https://jpmorganchase.github.io/perspective/examples/superstore.html in IE 11,

scenario:

  1. switch to grid mode
  2. unselect country and city
  3. move country to columns, after sub-category

results:

  1. it's veeery slow - is it because of perspective or because of hypergrid?
  2. console shows:
    SCRIPT5022: Assertion failed
    webcomponents.min.js (11,1555)
    View cancelled
    View cancelled
    Setting up initial schema and data load into HyperGrid

that's probably indicating an internal fault?

@texodus
Copy link
Member

texodus commented Feb 7, 2018

Thanks for the detailed report, this is very helpful.

This is indeed an internal fault. The only way to get real diagnostics in this case is to re-build the library with debug flags, which is currently a bit painful to configure. I will try to repro.

IE11 will always lag in performance to modern browsers, but we intend to support it functionally until it is dead and buried in industry.

@texodus
Copy link
Member

texodus commented Feb 12, 2018

I've tested this on the copy of IE11 I have, and only seen out-of-memory errors on large data sets - but this should come with an associated error more detailed than "Assertion Failed."

I've added a build option to generate a debug build, which should give you more information about such issues. Can you please try running a build as below, and filing a separate report with the stack trace if you encounter any issues?

`PSP_DEBUG=1 npm start`

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