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
When adding or editing a context in context view, autocomplete options should be rendered as children.
In the following mockup, when "Art" is typed in, the "Artists" and "Articles" autocomplete options are rendered as children:
When the user arrows down, there should be a selection independent of the cursor that goes through each child. Here "Articles" is selected in lightblue:
Clicking a child or hitting enter should set the context to the child text and clear the children:
When a context is edited, its descendants (e.g. /Articles/hello/x; not pictured) should move to the edited context. This is the same behavior as editing a thought. Its descendants are moved with it.
When the user types # at the beginning of a thought in normal view, activate autocomplete. Remove the # after a thought is selected.
The text was updated successfully, but these errors were encountered:
When adding or editing a context in context view, autocomplete options should be rendered as children.
In the following mockup, when "Art" is typed in, the "Artists" and "Articles" autocomplete options are rendered as children:
When the user arrows down, there should be a selection independent of the cursor that goes through each child. Here "Articles" is selected in
lightblue
:Clicking a child or hitting enter should set the context to the child text and clear the children:
When a context is edited, its descendants (e.g.
/Articles/hello/x
; not pictured) should move to the edited context. This is the same behavior as editing a thought. Its descendants are moved with it.When the user types
#
at the beginning of a thought in normal view, activate autocomplete. Remove the#
after a thought is selected.The text was updated successfully, but these errors were encountered: