Closed
Description
Here's what we're going to do for v2, targeting a release in January or February 2020:
- switch to
native-promise-only
and officially drop support for IE9 and IE10stop exporting D3stop exportingPlotly.plot
droparea
,contourgl
andpointcloud
tracesdrop support for polar plots inscatter
(aka "micropolar"?) i.e.scatter.r
andscatter.t
andlayout.angularaxis
andlayout.radialaxis
and anything else related (cc @alexcjohnson anything else I missed?)
For reference, the primary trigger for version 2.0 is the native-promise-only
change, with which we fully drop support for IE 9/10, even though that support has been eroding severely over the last couple of years. This change is driven by a desire to remove function constructors from as many of our bundles as possible for security reasons, as tracked in #897. Since we're doing a v2, we're trying to shed as much deprecated stuff as we can without being otherwise too-disruptive.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
nicolaskruchten commentedon Jan 11, 2021
@alexcjohnson suggested the following, which I approve if they take less than a day:
isPlainObject
- either just drop the second clause or use something like the new one I found in Validation fails when running via JsDom in NodeJs #5151 - in principle this needn’t be a major but it feels a bit risky to me for some straight JS usersPlotly.Fx
to just{hover, unhover, loneHover, loneUnhover}
andPlotly.Plots
to just{graphJson, resize}
nicolaskruchten commentedon Jan 11, 2021
Note to self: the plotly.com/javascript docs will need to stop relying on the built-in D3 :)
21 remaining items
dhirschfeld commentedon Jan 28, 2021
Just wondering if #5230 will make it in 2.0?
archmoj commentedon Jan 28, 2021
I think new features like that could possibly be added in a minor afterwards e.g. v2.x.0