-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[APM] Node keeps changing position until it's finally set on the page 🤯 #66528
Labels
apm:service-maps
Service Map feature in APM
bug
Fixes for quality problems that affect the customer experience
v7.8.0
Comments
cauemarcondes
added
[zube]: (7.8) Planned for release
bug
Fixes for quality problems that affect the customer experience
apm:service-maps
Service Map feature in APM
v7.8.0
labels
May 14, 2020
smith
added a commit
to smith/kibana
that referenced
this issue
May 14, 2020
After simplyfying the layout mechanism in elastic#66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node. Fixes elastic#66528.
zube
bot
added
[zube]: (7.8) Planned for release
and removed
[zube]: In Progress
labels
May 14, 2020
zube
bot
added
[zube]: (7.8) Planned for release
and removed
[zube]: (7.8) Planned for release
labels
May 14, 2020
smith
added a commit
that referenced
this issue
May 14, 2020
After simplyfying the layout mechanism in #66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node. Fixes #66528.
smith
added a commit
to smith/kibana
that referenced
this issue
May 14, 2020
After simplyfying the layout mechanism in elastic#66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node. Fixes elastic#66528.
smith
added a commit
to smith/kibana
that referenced
this issue
May 14, 2020
After simplyfying the layout mechanism in elastic#66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node. Fixes elastic#66528.
smith
added a commit
that referenced
this issue
May 15, 2020
After simplyfying the layout mechanism in #66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node. Fixes #66528.
smith
added a commit
that referenced
this issue
May 15, 2020
After simplyfying the layout mechanism in #66438, we made it so the `data` event handler would run even if there are no elements. This causes the `layoutstop` handler to run as well, but if we have multiple renders with no elements, multiple `layoutstop` events would by triggered after the elements were loaded, causing the map to jump around, which is especially visible with a single node. Fixes #66528.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
apm:service-maps
Service Map feature in APM
bug
Fixes for quality problems that affect the customer experience
v7.8.0
When you open the service map by clicking on its tab, sometimes the node keeps changing its position until it's finally set in the correct place.
The text was updated successfully, but these errors were encountered: