responsively-org/responsively-app

State sharing between instances

Open

#1.010 aberto em 7 de jul. de 2023

Ver no GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (21.641 stars) (1.064 forks)batch import
bughelp wanted

Description

🐞 bug report

State sharing between instances

✍️ Description

When using two independent instances of the app they share some data and inputs. When scrolling a page on one app, the other gets scrolled simultaneously. Going back and forward in history is also shared across apps as the taps on the page.

🕵🏼‍♂️ Is this a regression?

No. 1.4.0 has a similar issue

🔬 Minimal Reproduction

  1. Open one app with a page
  2. Open the second app with a page
  3. Scroll on the first app
  4. The page on the second app is getting scrolled as well

🌍 Your Environment

Ctrl + F1 doesn't work

System: Ubuntu 22.04 App version: 1.5.0.AppImage

🔥 Exception or Error or Screenshot

Guia do colaborador

Pilha de tecnologia
javascriptelectron
Domain
desktop
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
clear
Prerequisites
Basic knowledge of ElectronJavaScript
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
60
Direção de pesquisa
The issue describes state sharing between two instances of the Responsively app, where scrolling, history, and taps are mirrored. The root cause likely lies in the Electron main process managing multiple BrowserWindow instances. Investigate how window specific data (e.g., scroll position, navigation history) is stored and whether it is accidentally shared via global variables or localStorage. Check the renderer process code for any use of shared resources like the same webview or persistent storage. Look at the app's source files in the GitHub repository, particularly the main process entry point and any state management utilities. The issue comments may contain additional clues or suggestions for a fix.