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
Creating a new tab causes the "load-stop" signal to be emitted, running the associated webcontent.progressMonitor code.
This changes the Go/Refresh/Stop button to Refresh and calls faviconUpdate on an empty URI.
The text was updated successfully, but these errors were encountered:
Hmm, I thought this might be caused by a conditional in the newTab function always evaluating to true so that the navigate() function is called regardless of whether a URL was passed to the function... but I get the same behaviour even if I comment out the navigate() call so I'm not sure what is causing this
Creating a new tab causes the "load-stop" signal to be emitted, running the associated webcontent.progressMonitor code.
This changes the Go/Refresh/Stop button to Refresh and calls faviconUpdate on an empty URI.
The text was updated successfully, but these errors were encountered: