Skip to content

plotly interfering with other controls that may be using off screen realestate #393

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

Closed
jmsunseri opened this issue Apr 5, 2016 · 10 comments

Comments

@jmsunseri
Copy link

I had an issue where once i called the plotly constructor and the graph is drawn then a few of my angular ui bootstrap based calendar controls completely disappeared. I never had a problem with it in the past and it is still not a problem in IE but when working in Chrome the issue began to pop up. After modifying the drawing.makeTester function it began to work without interfering with my other controls. making the left and top properties below even greater into negative space seemed to solve the problem. I'm not an expert on what's going on in this function but it was causing me a lot of trouble. I wish I could reproduce the issue for you but i can't even reproduce the issue for myself right now.

drawing.makeTester = function(gd) {
    var tester = d3.select('body')
        .selectAll('#js-plotly-tester')
        .data([0]);

    tester.enter().append('svg')
        .attr('id', 'js-plotly-tester')
        .attr(xmlnsNamespaces.svgAttrs)
        .style({
            position: 'absolute',
            left: '-90000px',
            top: '-90000px',
            width: '9000px',
            height: '9000px'
        });

    // browsers differ on how they describe the bounding rect of
    // the svg if its contents spill over... so make a 1x1px
    // reference point we can measure off of.
    var testref = tester.selectAll('.js-reference-point').data([0]);
    testref.enter().append('path')
        .classed('js-reference-point', true)
        .attr('d','M0,0H1V1H0Z')
        .style({
            'stroke-width': 0,
            fill: 'black'
        });

    if(!tester.node()._cache) {
        tester.node()._cache = {};
    }

    gd._tester = tester;
    gd._testref = testref;
};
@mdtusz
Copy link
Contributor

mdtusz commented Apr 5, 2016

Without more details of what the issue is, we likely won't be able to remedy it.

If/when you can reproduce the issue, post a link to a working example (jsbin/codepen or the like) and we'll take a look.

@jmsunseri
Copy link
Author

I've created a plunker to display what's going on though I can't reproduce
the issue exactly

http://plnkr.co/edit/xNLXcglEIA8Q9dgAjnb8?p=preview

after pressing the search button in my application the plotly constructor
is called and the input box and date picker button would completely
disappear.

Sincerely

Justin Sunseri
Please don't print this e-mail unless you really need to.

On Tue, Apr 5, 2016 at 9:59 AM, Miklos Tusz [email protected]
wrote:

Without more details of what the issue is, we likely won't be able to
remedy it.

If/when you can reproduce the issue, post a link to a working example
(jsbin/codepen or the like) and we'll take a look.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#393 (comment)

@mdtusz
Copy link
Contributor

mdtusz commented Apr 20, 2016

Are you still experiencing this issue?

@jmsunseri
Copy link
Author

If you want I can replace my modified version of plotly.js with the the
latest available version and see if it is still happening.

Sincerely

Justin Sunseri
Please don't print this e-mail unless you really need to.

On Wed, Apr 20, 2016 at 9:35 AM, Miklos Tusz [email protected]
wrote:

Are you still experiencing this issue?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#393 (comment)

@mdtusz
Copy link
Contributor

mdtusz commented Apr 20, 2016

Please do. If the issue cannot be recreated, we will close this issue.

@jmsunseri
Copy link
Author

It looks like with the 1.9 release we are in the clear. Did you guys make
a change on purpose to fix this?

Sincerely

Justin Sunseri
Please don't print this e-mail unless you really need to.

On Wed, Apr 20, 2016 at 9:40 AM, Miklos Tusz [email protected]
wrote:

Please do. If the issue cannot be recreated, we will close this issue.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#393 (comment)

@mdtusz
Copy link
Contributor

mdtusz commented Apr 20, 2016

Nope. Nothing done for this issue.

@mdtusz mdtusz closed this as completed Apr 20, 2016
@jmsunseri
Copy link
Author

sorry to do this but it is still broken

Before:

[image: Inline image 2]

After:
[image: Inline image 1]

Maybe the size of the window has something to do with it?

Sincerely

Justin Sunseri
Please don't print this e-mail unless you really need to.

On Wed, Apr 20, 2016 at 11:23 AM, Miklos Tusz [email protected]
wrote:

Nope. Nothing done for this issue.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#393 (comment)

@mdtusz
Copy link
Contributor

mdtusz commented Apr 20, 2016

In the future, please respond directly on Github. Email replies pollute the issue with unnecessary text and things like images will not display.

We will not be able to do anything for this issue without concrete information e.g. what the element is, what classes the elements have, and what your plot is doing. As this seems to be a problem specific to your usage of plotly.js and no an issue with the library, I will point you in the direction of the plotly forums for further support.

@jmsunseri
Copy link
Author

I tried to help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants