I agree with the contributor's choice of dialetc over plotly's default.

However, I think adding piece-meal rules to change how stuff is built
will ultimately make it more complicated to refactor, maintain, and read
in the future.

The current dialect of javascript (enforced primarily by the linter at
least in the pull-request stage), is limiting and inconvenient.
Migrating to a more modern javascript, I believe, requires a broader
strategy.

Update to your pull-request for making es5/require work.

Adding a closed caption div to plotly interefered with plotly's
management of it.

We now start by default outside of the generated plotly divs.

But we add options to users can a) generate it with any id/class.

Or specify that it already exists and use an existing element by id.

…into pikul-music-import-promise

Passing named empty arrays to chart2music makes it angry during
validation.

accessibility.js takes configuration variables from `plot_config.js`, modifies
them, and passes them directly to `chart2music`.

The problem is that assigning an object to a new variable doesn't copy
it, so any change to that variable also changes the original object.

Plotly uses changes (or lack thereof) in the config variables to decide if it can
shortcut certain redraw steps. It cannot if config variables change. So
if `accessibility.js` is run on every redraw, the config variables will look
different (even if they are not), and plotly will always take the long
way around during its rerendering.

That being said, this solution here may need more thought. Questions
like: when _should_ chart2music ask plotly to do a full redraw? Should
it ever? Would it do that by changing a config it has access to? Will it
ever change plotly config variables frequently.

I can't think of instance where

1) the caption div wouldn't be specified by the user
2) would maybe do some really fancy interaction w/ the graph
3) be completely invisible because its meant to be read outloud anyway

Either way, the generation strategy needs work.

* Tests now create their closed caption div

FIX and Add options to chart2music plotly integration

1) Since accessibility.js will support multiple accessibility libraries,
   there is now a C2M library that contains the API for initializing C2M
   to plotly charts.
2) The initialization process is split into it's various phases.
3) Trace types now have specific codecs to map plotly-C2M. See the
   README in each file.
4) xy-scatter codec was refactored a bit to not assume the x-y is
   domain-range.
5) All config variables are now copied from defaults so C2M doesn't mess
   with plotly's config obect.

…usic_dev

This reverts commit 129eb3b.