-
Notifications
You must be signed in to change notification settings - Fork 32
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
Minimized report causes JS error #300
Comments
It even does not need recalculation, you just need to minimize/maximize a report. |
I don't understand this change;
31f9c5a#diff-bd59f22ea95f9de04f76e1fe585c1e14R176
The $scope.apply was unnecessary so I removed it. I don't think you want to
run $digest explicitly.
|
The $apply or $digest is needed or the reports don't resize with the page. [image: Inline image 1] On Thu, Aug 18, 2016 at 10:00 AM, Rob Nagler [email protected]
|
The event comes from angular, because I changed it to $interval.
|
I reverted the debounce() back to setTimeout() / clearTimeout(). The change Paul On Thu, Aug 18, 2016 at 11:39 AM, Rob Nagler [email protected]
|
We can't use setTimeout because of
angular/protractor#169
|
How is it supposed to work? I thought the function should only be called once no matter how many times debounce was called. |
Each plot registers to get called back on a resize event. When the resize scope.windowResize = debounce(function() { For some reason, the $interval code was only calling windowResize() for the Paul On Thu, Aug 18, 2016 at 12:37 PM, Rob Nagler [email protected]
|
I understand. I'll fix
|
Fix 8e7b244 |
Minimized report after maximizing causes this JS error both in the browser console and server log:
It can be reproduced in any example, but I used
Young's Double Slit Experiment
example and minimizedIntensity at W30 Report, 30m
report, changed some parameters (e.g., sampling factor) to trigger recalculation of the reports and then maximized the minimized report.The text was updated successfully, but these errors were encountered: