First of all, thanks for this lovely piece of software, which has done a good job repl

thanks <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-u

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Urs asked me to take a look and I found the following: <div class="snippet-clipboa

"Process data" button eternally showing "Loading" after upgrading to nfsen-ng v0.3 about nfsen-ng HOT 4 CLOSED

urscale commented on September 5, 2024

"Process data" button eternally showing "Loading" after upgrading to nfsen-ng v0.3

from nfsen-ng.

Comments (4)

mbolli commented on September 5, 2024 1

thanks @href and @urscale for the additional information!

from nfsen-ng.

mbolli commented on September 5, 2024

@urscale

Thanks for the report.

Please open the browser dev tools and set a break point on line 343 (inside setButtonLoading()).
Then reload the page. You should now see in the call stack why the button was set to loading.

Unfortunately in my installations I can't reproduce the issue.

from nfsen-ng.

href commented on September 5, 2024

Urs asked me to take a look and I found the following:

setButtonLoading (nfsen-ng.js:343)
(anonymous) (nfsen-ng.js:855)
each (jquery.min.js:2)
each (jquery.min.js:2)
display_message (nfsen-ng.js:854)
(anonymous) (nfsen-ng.js:90)
c (jquery.min.js:2)
fireWith (jquery.min.js:2)
l (jquery.min.js:2)
(anonymous) (jquery.min.js:2)
load (async)
send (jquery.min.js:2)
ajax (jquery.min.js:2)
S.<computed> (jquery.min.js:2)
(anonymous) (nfsen-ng.js:80)
e (jquery.min.js:2)
t (jquery.min.js:2)
setTimeout (async)
(anonymous) (jquery.min.js:2)
c (jquery.min.js:2)
fireWith (jquery.min.js:2)
fire (jquery.min.js:2)
c (jquery.min.js:2)
fireWith (jquery.min.js:2)
ready (jquery.min.js:2)
B (jquery.min.js:2)

The setButtonLoading function is called exactly once and never again. It seems like it is done when the following message is loaded after the refresh: