daattali / daattali/shinybrowser
Consider supporting browser dimensions even after change
Open
- Dominant language
- R
- Stars
- 40
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Did not include it for 2 reasons: 1. performance, 2. all other fields are returned on init only. But a few people asked about this so look into it
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests; start by locating how browser dimensions are collected and how the other fields are returned during initialization in the Shiny app. Investigate the performance trade-off and define how dimensions should update after a browser change. Done means the requested updates work without an unacceptable performance cost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100