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
The framework seems to unnecessarily call render on Parts when they change their own Properties, resulting (most obviously) in visible overlays, for example when a SlickGrid column is resized, and potentially in lost state (e.g scroll position), stickiness etc.
Things to consider:
Existing Parts could potentially depend on applying their own changes to themselves via render.
Other potential cross-cutting future API changes such as removing explicit initialize, adding onOptionsChanged.
The text was updated successfully, but these errors were encountered:
Plan is to push this to a branch first to test for any real-world failures, then slowly move UDPs away from this behavior. The process of doing that should help us uncover any major spec risks that we haven't yet seen in making this change.
The framework seems to unnecessarily call
render
on Parts when they change their own Properties, resulting (most obviously) in visible overlays, for example when a SlickGrid column is resized, and potentially in lost state (e.g scroll position), stickiness etc.Things to consider:
initialize
, addingonOptionsChanged.
The text was updated successfully, but these errors were encountered: