"InternalError: too much recursion" in Firefox during print

[williammck]

Hi! I noticed that when printing in Firefox, InternalError: too much recursion is thrown twice, at the beforeprint and afterprint events. Printing still works fine, but only after about a second of delay once the JS engine stops the infinite recursion.

It's happening here: https://github.com/mkoryak/floatThead/blob/master/src/jquery.floatThead.js#L139, as triggerHandler then again calls the handlers set in that if statement.

This isn't personally causing me an issue (other than filling up my Sentry logs), but I'd imagine for sites with some functionality in the before/after print handlers it could create some trouble.

Reproduction URL: https://mkoryak.github.io/floatThead/ (it occurs on any normal install of floatThead from what I can tell)

Browser: Firefox 59
OS: Windows 10, macOS 10.13
jQuery version: 3.3.1 (latest)
floatThead version: 2.1.1 (latest)

[mkoryak]

Thanks, I'll look tomorrow. Sorry about the sentry logs.

…

On Wed, Mar 21, 2018, 7:30 PM William McKinnerney ***@***.***> wrote: Hi! I noticed that when printing in Firefox, InternalError: too much recursion is thrown twice, at the beforeprint and afterprint events. Printing still works fine, but only after about a second of delay once the JS engine stops the infinite recursion. It's happening here: https://github.com/mkoryak/floatThead/blob/master/src/jquery.floatThead.js#L139, as triggerHandler then again calls the handlers set in that if statement. This isn't personally causing me an issue (other than filling up my Sentry logs), but I'd imagine for sites with some functionality in the before/after print handlers it could create some trouble. Reproduction URL: https://mkoryak.github.io/floatThead/ (it occurs on any normal install of floatThead from what I can tell) Browser: Firefox 59 OS: Windows 10, macOS 10.13 jQuery version: 3.3.1 (latest) floatThead version: 2.1.1 (latest) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#409>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXbSUS4OLVcxYLjVqbazCyD0uUmNX9tks5tguKngaJpZM4S2OAx> .

[williammck]

Quick update: am seeing it happening now all the way back to FF47 on macOS 10.11.

I guess one way to fix it is to have a printing variable, check for false and set to true in beforeprint, then check for true and set to false in afterprint

No problem about the logs - wouldn't have known this was happening otherwise! :)

[mkoryak]

I cannot do what I promised, no time lately. Pull requests are welcome :)
Otherwise, ill get to it as soon as I get to it.

[williammck]

Not a problem! If I get some time (ha!) I’ll try and find a good way of fixing it and create a PR.

…

-- *William McKinnerney* [email protected] williammck.net

On March 27, 2018 at 13:12:14, Misha Koryak ***@***.***) wrote: I cannot do what I promised, no time lately. Pull requests are welcome :) Otherwise, ill get to it as soon as I get to it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#409 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABi1gCB-t7kNFwo55mvfqr8CpY_d0sGyks5tioD-gaJpZM4S2OAx> .

[mkoryak]

should be fixed in /src, let me know how bad you want a release :)

[williammck]

whenever! I don't really care, been super busy moving house.

just put it in with whatever next release, we're in education so our product won't see much usage until fall.

[williammck]

our product won't see much usage until fall

aaand, right on time, I've started getting reports of the issue again.

any chance you're rolling a new release in the near future? would greatly appreciate it. :)

[mkoryak]

Sure thing, I'm away until Tuesday. Expect a release around that time.

[williammck]

hey! sorry if you're busy, just checking back in about when to expect a release :)

[mkoryak]

good question. Got busy at work. Next week?

[williammck]

Sure! It's not happening a ton, just got another bug report of it and it reminded me. Take your time if needed.

[mkoryak]

Ok, that took forever, but finally I published it as 2.1.3

[williammck]

Much appreciated! 😄

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.