Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature request: Change `HTMLWidgets.shinyMode` to integers 0, 1, 2...

Open
#421 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
frontend, web-dev

Research direction

Start by tracing the HTMLWidgets.shinyMode entry point and review the linked rmarkdown issue for the shinyrmd and shiny_prerendered runtime behavior. Define whether the existing flag should become integer-valued or a separate runtimeMode should be added, then verify the three requested states without breaking existing widget integrations.

Written by the indexing model from the issue text.

Description

Recently I was trying to render the htmlwidgets in rmarkdown with shinyrmd runtime, but then I encountered rendering errors.

The reason is because when rendered in shinyrmd or shiny_prerendered runtime, Shiny has invalid onInputChanged method. This will invalidate many widgets that are expecting this feature, for example, visNetwork and threeBrain, etc. are expecting to communicate with shiny, which will definitely fail.

Please see more details from this issue: https://github.com/rstudio/rmarkdown/issues/2232

I was wondering if HTMLWidgets.shinyMode could be integers such that:

  • HTMLWidgets.shinyMode=0 means no shiny is detected
  • HTMLWidgets.shinyMode=1 means shiny is detected and is in normal dashboard mode or shiny runtime in rmarkdowns
  • HTMLWidgets.shinyMode=2 means shiny is detected but rendered in rmarkdown with shinyrmd or shiny_prerendered runtime

If this change could break many packages, when maybe add HTMLWidgets.runtimeMode?

Dominant language
R
Stars
801
Forks
202
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ramnathv/htmlwidgets

All issues in ramnathv/htmlwidgets

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.