Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix mapbox visible false first draw #900

Merged
merged 1 commit into from Sep 7, 2016
Merged

Conversation

etpinard
Copy link
Contributor

@etpinard etpinard commented Sep 2, 2016

Passing in scattermapbox trace with visible: false to Plotly.plot resulted in plot code exceptions (updates with visible: false worked and work fine).

- this handles the case where a 'visible: false' are passed in
  during the first plot call (the restyle case worked and works fine)
- note 'that visible: false' traces do not get fullTrace._module
  during supply defaults.
@@ -212,7 +212,7 @@ proto.updateData = function(calcData) {
traceObj = traceHash[trace.uid];

if(traceObj) traceObj.update(calcTrace);
else {
else if(trace._module) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that visible: false traces do not get fullTrace._module during supply defaults.

@etpinard etpinard added this to the v1.17.0 milestone Sep 2, 2016
@mdtusz
Copy link
Contributor

mdtusz commented Sep 7, 2016

💃

These are perfect lil breaks while my tests run!

@etpinard etpinard merged commit a0bfe09 into master Sep 7, 2016
@etpinard etpinard deleted the mapbox-visible-false branch September 7, 2016 18:34
@etpinard etpinard restored the mapbox-visible-false branch September 7, 2016 21:16
@etpinard etpinard deleted the mapbox-visible-false branch September 7, 2016 21:20
etpinard added a commit that referenced this pull request Sep 8, 2016
Fix mapbox visible false first draw
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants