aboutsummaryrefslogtreecommitdiffstats
path: root/extension/background.js
diff options
context:
space:
mode:
authorTeddy Wing2021-02-21 02:37:11 +0100
committerTeddy Wing2021-02-21 02:37:11 +0100
commit16c8122254725805be666cf065c590d54d66dfad (patch)
treec0bfec632feb3be312655d55ad7c9949350cf57a /extension/background.js
parent8af40a7846f2aebba6eedc978f694d57e169af0e (diff)
downloadextreload-16c8122254725805be666cf065c590d54d66dfad.tar.bz2
main: Replace hard-coded call IDs with a new counter
Looks like this was the answer to the problem of the active tab not reloading consistently. Previously, if I had two instances of an extension loaded in two separate Chrome profiles, the following could happen: 1. Neither profile's active tab reloaded 2. Only one profile's active tab reloaded 3. Both profiles' active tabs reloaded With this change, both profiles' active tabs reload correctly and consistently.
Diffstat (limited to 'extension/background.js')
0 files changed, 0 insertions, 0 deletions