-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Open
Description
What is this about?
Currently:
- We reload each page each time the tab is switched
- We reload the active tab when you move away from browser and back to browser
Both of these are contributing to feeling of slowness/clunkiness
Previously, we've kept the connection open for each open tab, spending a lot of device resources - and the number of open tabs was limited to 5 to keep resource utilization at bay
Scope:
- Explore the possibility of caching the active tab and several last visited tabs without significant impact on device resources
- Implement the caching solution identified during the exploratory phase
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
- Engineering (needed in most cases)
- Design
- Product
- QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- Security
- Legal
- Marketing
- Management (please specify)
- Other (please specify)
References
No response
Metadata
Metadata
Assignees
Labels
No labels