You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser/Node.js & version : Firefox 72.0.2 & Chrome 79.0.3945.79
Current (buggy) behaviour
A call to a function like edge.midpoint() may return a value that is not fresh w.r.t. recent bounds changes to the connected nodes.
Desired behaviour
For an edge whose connected nodes have recently changed bounds (position, width, etc.), calls to functions like edge.midpoint() should cause the renderer to recalculate the rendered style synchronously.
… to getter #2608
Rendered style is generally recalculated at the start of a frame rather than synchronously at the time of dirtying. This avoids redundant calculations. Further an edge is not explicitly dirtied when at least one of its connected nodes changes in dimensions (position, width, etc.). Instead, it is implicitly marked as dirty via the `cleanConnected` flag on the node.
An immediate, synchronous recalculation of rendered style may happen for public functions that read rendered style, such as `edge.midpoint()`. For this case, `recalculateRenderedStyle()` must check whether an edge is implicitly dirty via `cleanConnected`.
… to getter #2608
Rendered style is generally recalculated at the start of a frame rather than synchronously at the time of dirtying. This avoids redundant calculations. Further an edge is not explicitly dirtied when at least one of its connected nodes changes in dimensions (position, width, etc.). Instead, it is implicitly marked as dirty via the `cleanConnected` flag on the node.
An immediate, synchronous recalculation of rendered style may happen for public functions that read rendered style, such as `edge.midpoint()`. For this case, `recalculateRenderedStyle()` must check whether an edge is implicitly dirty via `cleanConnected`.
…t be fresh on call to getter #2608#2609
Rendered style is generally recalculated at the start of a frame rather than synchronously at the time of dirtying. This avoids redundant calculations. Further an edge is not explicitly dirtied when at least one of its connected nodes changes in dimensions (position, width, etc.). Instead, it is implicitly marked as dirty via the `cleanConnected` flag on the node.
An immediate, synchronous recalculation of rendered style may happen for public functions that read rendered style, such as `edge.midpoint()`. For this case, `recalculateRenderedStyle()` must check whether an edge is implicitly dirty via `cleanConnected`.
Issue type
Bug report
Environment info
Current (buggy) behaviour
A call to a function like
edge.midpoint()
may return a value that is not fresh w.r.t. recent bounds changes to the connected nodes.Desired behaviour
For an edge whose connected nodes have recently changed bounds (position, width, etc.), calls to functions like
edge.midpoint()
should cause the renderer to recalculate the rendered style synchronously.Minimum steps to reproduce
See #2595
The text was updated successfully, but these errors were encountered: