responsively-org/responsively-app

State sharing between instances

Open

#1010 opened on Jul 7, 2023

View on 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

Contributor guide

Tech stack
javascriptelectron
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of ElectronJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.