features and TODOs based on or reflected in shiny issues

[nteetor]

• tabset and navbar IDs - Feature request: Allow tabset and navbar to have nameable ID values for hyperlinking rstudio/shiny#1066

  • even if an id argument is not specified all dull UI builder functions allow ...

• security concerns regarding downloadEvent, does downloadEvent and the corresponding dull:download event worsen the problem? - Minor security vulnerability (user tokens in URL) rstudio/shiny#1845

• radioInput over radioButtons - radioButtons don't follow input widgets naming scheme - add alias radioButtonsInput? rstudio/shiny#844

  • renamed to radioInput on api-consistency branch

• button groups (which seem to have disappeared, past Nate must have removed them) - Feature Request: buttonGrid rstudio/shiny#1919

• viewport responsive columns - Feature request: allow for more flexible manipulation of bootstrap grid rstudio/shiny#1836

• Input validation - Input validation rstudio/shiny#33

  • part of *Input toolkit #12

• ... for all inputs - Add ... to all outputs rstudio/shiny#1516

  • motivation for dull, part of dull since conception

• tableInput - Feature Request: inputTable rstudio/shiny#1555

  • partially handled by tableInput

• buttons with more contexts - Make buttons more customizable by allowing more bootstrap colors rstudio/shiny#1675

  • currently buttonInput has an argument context

• color input - feature request - color picker rstudio/shiny#718

  • comes with bootstrap textual inputs, only supported by browsers
  • does not show in RStudio viewer
  • meh

• bundling inputs - Feature: way of affecting a family of inputs all at once rstudio/shiny#1448

  • perhaps handled by form group inputs? However, form groups will undergo significant changes soon.
  • after reviewing the issue the motivation could be solved by a UI design change

[nteetor]

(removed help wanted tag as the issue is very general)