Log Message:
(www/R-htmlwidgets) Updated 1.3 to 1.5.3

htmlwidgets 1.5.3
-------------------------------------------------------

### New features

* Added a `reportTheme` argument to `shinyWidgetOutput()`. If `TRUE`,
  CSS styles of the widget's output container are made available to
  `shiny::getCurrentOutputInfo()`, making it possible to provide
  'smart' styling defaults in a `renderWidget()` context. (#361)

* `shinyRenderWidget()` now has a `cacheHint` parameter, for use with
  Shiny's new `bindCache()` function. (#391)

* Support a new `PACKAGE::widget_html.WIDGETNAME` convention for
  defining custom widget HTML. This replaces the earlier
  `PACKAGE::WIDGETNAME_html` convention, which continues to work but
  may be deprecated at some point in the future. The goal for the new
  convention is to prevent accidentally matching functions that were
  never intended for this purpose. (Thanks, @thebioengineer!) (#376)

* Export the `JSEvals` function, allowing other packages to support
  `JS()` in non-widget contexts.

### Bug fixes

* `saveWidget()` now `file` argument now properly handles relative
  paths. (#299)

* Fixed an issue with passing named function declarations to `JS()`
  and `onRender()` (introduced by v1.4). (#356)

htmlwidgets 1.5.2
-------------------------------------------------------

* Emergency patch release to fix an issue with rendering htmlwidgets
  in flexdashboard. More generally, this change implies that any
  htmlwidget is printed via a knitr code chunk with multiple values
  for fig.width/fig.height, only the first value is used for the
  widget's sizing policy. (#387)

htmlwidgets 1.5.1
-------------------------------------------------------

* Fixed an issue with dynamically rendered widgets (i.e., using
  `shiny::uiOutput()` to render a widget) with any version of shiny
  prior to 1.4. This issue was introduced by htmlwidgets 1.5. (#351)

htmlwidgets 1.5
-----------------------------------------------------------------------

* Fixed an incompatibility with Shiny v1.4.0: due to Shiny upgrading
  from jQuery 1.x to 3.x, the timing of some initialization routines
  has changed. This caused some widget `renderValue` calls to occur at
  an earlier point in Shiny's initialization process than with earlier
  versions of Shiny. (#345)

htmlwidgets 1.4 (unreleased)
-----------------------------------------------------------------------

* JavaScript statements can now be passed along to `onRender()` and
  `JS()` (#329).