-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Output bounding box to hover event data (new attempt) #5872
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You shouldn't commit 'npm run build'. Please drop that commit as we only commit the dist for releases. If you are interested in the build files you could simply find them in the 'publish-dist' container on CircleCi under Artifacts tab.
Thanks.
2083dfb
to
3533631
Compare
Thanks for the heads up. I removed the content of |
// TODO: These coordinates aren't quite correct and don't take into account some offset | ||
// I still haven't quite located (similar to xa._offset) | ||
bbox: { | ||
x0: pt.x0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these coordinates correct for pie
?
// a sibling of the graph div, it will be positioned correctly relative to | ||
// the offset parent, whatever that may be. | ||
var hot = gd.offsetTop + gd.clientTop; | ||
var hol = gd.offsetLeft + gd.clientLeft; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's rename hot
and hol
to topOffset
and leftOffset
.
Please update the PR description similar to #5512 and mention that PR. |
Please pull |
Please also provide |
@alexcjohnson can you help get this one over the finish line plz, even after @xhlulu leaves? :) |
No remarkable commit added when compared to the original PR #5512. |
Thanks for your interest in plotly.js!
Translations:
lib/locales/
, not those indist/
Features, Bug fixes, and others:
Before opening a pull request, developer should:
master
branch of their fork as usingmaster
for a pull request would make it difficult to fetchupstream
changes.upstream/master
into your fork i.e.origin/master
then pullorigin/master
from you localmaster
.git rebase master
their local dev branch off the latestmaster
which should be sync withupstream/master
at this time.git add
thedist/
folder (thedist/
is updated only on version bumps).package-lock.json
file (if any new dependency required).After opening a pull request, developer:
1010_fix.md
or1010_add.md
insidedraftlogs
folder as described in this README, commit it and push.git push -f
) to remote branches associated with opened pull requests. Force pushes make it hard for maintainers to keep track of updates. Therefore, if required, please fetchupstream/master
and "merge" with master instead of "rebase".