search

igvteam / igv-reports

Python application to generate self-contained pages embedding IGV visualizations, with no dependency on original input files.
MIT License
347 stars 51 forks source link

Embedded igv-report array length error #58

Closed azbard closed 2 years ago

azbard commented 2 years ago

Hi there - I'm embedding an igv-report in an iframe and it works fine except it pops up this error: invalid-aray-length-error Thoughts?

jrobinso commented 2 years ago

That's not a lot of information to go on. If you can zip and share the report I will look at it. Look in the console for errors.

azbard commented 2 years ago

Yes, sorry, that was vague. See attached. Open "array-error.html" and click on the "Pileups" tab array-error.zip .

jrobinso commented 2 years ago

I don't know but it must have something to do with the tab since the report itself does not have any errors that I could find. You might need to insert a call to "browser.visibilityChanged()" somewhere, see https://github.com/igvteam/igv.js/wiki/Browser-API-2.0#visibilitychange and also https://github.com/igvteam/igv.js/blob/master/dev/misc/tabs.html. That's just a guess.

On Tue, Dec 28, 2021 at 11:10 AM Adam Z Bard @.***> wrote:

Yes, sorry, that was vague. See attached. Open "array-error.html" and click on the "Pileups" tab array-error.zip https://github.com/igvteam/igv-reports/files/7786071/array-error.zip .

— Reply to this email directly, view it on GitHub https://github.com/igvteam/igv-reports/issues/58#issuecomment-1002244794, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHD2HCI74PXPUP647EZADDUTIDRBANCNFSM5K4OMDPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

azbard commented 2 years ago

Thanks for the quick response - will look into it and report back if I figure it out. In the mean time, may as well close the issue.