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 "sticky"-position of the label-container is not really suitable for micronode lists. If the list of alllowed microschemas is too long the list becomes larger than the screen and nodes at the bottom of the list can no longe be picked.
Example
This bug is also related to #313. Due to the fixed position, the label list is no longer within the normal document flow. This causes microschemas with long names to overlap with the list-container.
Possible solutions
Probably the easiest solution would be to disable the sticky-position for micronode lists. A more sophisticated solution may be to offer the allowed microschemas within a popover/dropdown-component. This could lead on the other hand to issues with the drag&drop-logic of the lists.
The text was updated successfully, but these errors were encountered:
@micstra Thanks for reporting this. We have unfortunately no resources to review PR / Issues on the mesh-ui on github. I'll let you know when / if this changes.
Problem
The "sticky"-position of the label-container is not really suitable for micronode lists. If the list of alllowed microschemas is too long the list becomes larger than the screen and nodes at the bottom of the list can no longe be picked.
Example
This bug is also related to #313. Due to the fixed position, the label list is no longer within the normal document flow. This causes microschemas with long names to overlap with the list-container.
Possible solutions
Probably the easiest solution would be to disable the sticky-position for micronode lists. A more sophisticated solution may be to offer the allowed microschemas within a popover/dropdown-component. This could lead on the other hand to issues with the drag&drop-logic of the lists.
The text was updated successfully, but these errors were encountered: