When adding a element, we have to click on the icon and we will get a floating modal. That’s ok.
But to get a needed element, we will mostly use the search. Once the Modal is closed and opened again, the last search is remembered, which is mostly not what we need. So we need to delete the last search before making the new one.
I think either there should be an “X” to clear the last search, or perhaps even better, the modal should open fresh, without the last search remembered.
Thanks!
I agree with adding a (x) button to the search field.
However, I’m the type of user who prefers the new persistent version of the Elements Panel. And it would drive me nuts to have the search field clearing every time I added something to the page.
So, I wonder if it makes sense to reset the search field like you described when the user has the new preference set for element panel behavior (I forget what that new setting is called at the moment).
For example, if you’ve set the panel to disappear after you add each element to the page, the search field resets every time it disappears.
However, if you have the panel persistent on the page, it retains your search and scroll position like it does in the current beta.
(Alternatively, I like the idea of the search field clearing after a certain period of time too. For example, it remembers what you searched for for 1 minute, and clears after that. Etc.)
@devinelston, can you help me understand the scenario where you would want the search to stay after closing the modal?
I understand that it could be useful if the same element is being added again, but in such case duplicating the last one may be even faster because it has probably received some styling we want to reuse.
What would be another reason? I may be missing something obvious. To me it seems like In 90%+ cases we’d benefit from cleared search because we’ll be adding new elements to the page.
Great thoughts here. We tried a version with a “clear” button in the search, but it looked really weird to have to X buttons side-by-side since the input is in the same horizontal space as the floating modal header.
Quick aside: if you press escape, it will clear the search.
I think a good balance here is not automatically changing the search or scroll position while the panel is open. If the panel gets closed automatically via the preference, or even if you close it out yourself, I’m inclined to expect that the next time I open it I get a fresh slate and the search is cleared out.
@alexander, I think that’s the cleanest experience for users. If it were to reset search/scroll while the persistent element panel is open, it would feel jarring. But clearing while it’s closed “feels” right.
Looking at the X styling you guys use in the various search fields, I see why having two of them next to each other looked weird. I had it in my head that it would be an (x) contained in a circle like you commonly see in other search fields. For example, in the search on iOS:
I’ve accidentally closed the element panel a number of times because I’m used to clearing searches with the (x) button at the end of the search field. So, I wonder if you’ll be getting feedback about that when more users start getting their hands on this build. Good to know about esc though.
@Misho, given the changes Alexander’s going to make, it seems like both our ways of working will be addressed. So, I don’t know that my answer will be terribly useful to you, but I figured I’d address your question anyway, just so you understand where I’m coming from…
There are a variety of use cases where I run into frustrations with the behavior of the current elements “tab” in the release version of Pro (where it resets the search & scroll position every time).
The first, is that I typically set up a variety of presets for things like buttons, headlines, etc., and use a particular naming scheme (e.g. “V3 - H1”, “V3 - Button - Transparent” etc.). So, when I build a new page, I’ll need several different elements (a headline, a couple buttons, different text elements, etc.). So, I just type a partial search for “V3” and all those elements get pulled to the top. So, if I’m adding several elements in a row, it’s convenient for me to have the element panel remember the search.
Other times, when I’m just exploring the elements, I’ll scroll down the list and want to try out a few different elements in a layout. In this case, having the scroll position reset every time I drag an element is incredibly frustrating because I have to figure out how far down I scrolled again each time.
These are just a couple examples of how I use Pro, and how the auto-reseting behavior creates friction as I build. So, for me personally, I prefer the behavior where the element panel stays on the screen, and remembers my search/scroll position until I explicitly close it.
So, I think the solution Alexander’s going with solves both our problems. So I’m personally happy.
This is exactly what I meant. Great! And also, great tip with the Escape key!
@devinelston, it seems that I have not communicated my post clearly. I never meant that the search should auto-reset while the panel is open. It just doesn’t make sense to me to get the old search once the panel is reopened again, after it was closed.
I have similar naming conventions for various presets and I also like the fact that I can pull in multiple elements grouped by my search. Though, If I need some particular elements available for some short or longer period and I’d like them on the top, I’ll favorite them, even if it is favoriting for a brief time.
@Misho Just posting here to confirm the next patch (probably going out tomorrow) will have that correction.
