You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jupyterlab allows multiple notebooks to be opened simultaneously in the same browser tab by using its own internal jupyter tabs. That seems to play very badly with WebIO.jl. For example, try running the random_print_button() demo from the Readme in two different jupyterlab notebooks (living in jupyterlab tabs in the same browser tab):
functionrandom_print_button()
w =Scope()
obs =Observable(w, "rand-value", 0.0)
on(obs) do x
println("JS sent $x")
endw(
dom"button"(
"generate random",
events=Dict("click"=>@js () ->$obs[] = Math.random()),
),
)
endrandom_print_button()
Running this code in both notebooks causes the first Julia kernel to receive the messages from both tabs, even though their scope IDs are different. The result is that the "JS sent $x" message is printed in the output of the first notebook even when you click buttons in the second notebook.
Running the cell a few more times eventually gets WebIO into a state where neither button does anything except throw "invalid message received" warnings in the JS console and no output is printed at all.
The text was updated successfully, but these errors were encountered:
Jupyterlab allows multiple notebooks to be opened simultaneously in the same browser tab by using its own internal jupyter tabs. That seems to play very badly with WebIO.jl. For example, try running the
random_print_button()
demo from the Readme in two different jupyterlab notebooks (living in jupyterlab tabs in the same browser tab):Running this code in both notebooks causes the first Julia kernel to receive the messages from both tabs, even though their scope IDs are different. The result is that the "JS sent $x" message is printed in the output of the first notebook even when you click buttons in the second notebook.
Running the cell a few more times eventually gets WebIO into a state where neither button does anything except throw "invalid message received" warnings in the JS console and no output is printed at all.
The text was updated successfully, but these errors were encountered: