[ 
https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125970#comment-17125970
 ] 

Aashna Jena commented on CAMEL-14958:
-------------------------------------

This seems good to me. I have one suggestion. In this image, the two close 
buttons are a little confusing. I understand that one is for clearing the 
search and other for closing the search bar. Can we use a bigger cross icon, 
identical to the one used for closing the main menu? It's a bigger touch 
target, plus since it's used for closing the menu, perhaps it would help 
differentiate between the "clear" and "close" functionalities.


!nav-searchbar-1220.png!

> Suggestion on search bar within smaller screen width.
> -----------------------------------------------------
>
>                 Key: CAMEL-14958
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14958
>             Project: Camel
>          Issue Type: Improvement
>          Components: website
>            Reporter: Aemie
>            Priority: Major
>              Labels: outreachy2020, suggestions
>         Attachments: nav-search-icon-1220.png, nav-searchbar-1220.png, 
> nav-searchbar-414.png, navbar-search-414.png, searchbar-outreachy.jpeg
>
>
> Within the small width screen, the setting is to only display the social icon 
> button as of now. However, I thought it would be a good idea to include the 
> search icon alongside the social button icons. On click of the social button 
> icons, we could include animation, for instance, a fade-in effect of the 
> search bar occupying the entire navbar. The user can do the search as 
> required. On the left side of the search bar, there will be back arrow, which 
> on click would give us the original navbar look with a fade-out effect.
>  
> The representation would look similar to the diagram as shown.
>     !image-2020-05-25-18-16-52-529.png|width=326,height=166!
>  Before I start working on this, I would like an opinion about this idea.
>   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to