Chris Parmer

thanks for reporting @johnpauls ! could you elaborate more on what you would expect the keyboard interactions to be?

In this UI 

@Biswa5812 - It's in here: https://github.com/plotly/dash/tree/dev/dash-renderer/src/components/error/FrontEnd

@Biswa5812 - Let us know if you end up taking a look at this one! This would be a good first issue to get started contributing to Dash.

> I can't see any reason why config wouldn't update like any other prop in dcc.Graph. This is how I've been testing it out, the dropdown should just remove the...

@charleyferrari - Can you push up a PR? Then I can comment on your code directly. In particular, this logic looks wrong: ``` const configChanged = this.props.figure !== nextProps.config; ```...

I believe that we aren't actually using this token anymore, as we removed CSRF protection in https://github.com/plotly/dash/pull/146. This logic wasn't removed in the dash front-end, and so I believe we...

Looks like this is causing some other folks issues as well, like https://github.com/refinery-platform/heatmap-scatter-dash/issues/53

> some folks won't be able to remove CSRF protection from those routes due to their own security concerns. > I'd also like to point out the logic mentioned here:...

Here is how the config logic works in Dash: 1. Dash backend exposes them through `app.config`: https://github.com/plotly/dash/blob/9a4c50c415d77f68f4b19ab7e25836b8e5c3683a/dash/dash.py#L48-L52 2. Dash backend templates them into HTML: https://github.com/plotly/dash/blob/9a4c50c415d77f68f4b19ab7e25836b8e5c3683a/dash/dash.py#L293 3. Dash frontend reads the...