After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778889 - The search bar doesnot go away unless you click on the search button
The search bar doesnot go away unless you click on the search button
Status: RESOLVED DUPLICATE of bug 747962
Product: gnome-calendar
Classification: Applications
Component: User Interface
3.20.x
Other Linux
: Normal normal
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
: 778890 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-02-18 21:18 UTC by nikhilnandyala97
Modified: 2017-04-28 20:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The screen shot of the calendar application using the search bar (143.14 KB, image/png)
2017-02-18 21:18 UTC, nikhilnandyala97
Details

Description nikhilnandyala97 2017-02-18 21:18:25 UTC
Created attachment 346149 [details]
The screen shot of the calendar application using the search bar

The search bar when clicked on the search button appears in the centre of the application blocking the calendar(blocking the calendar is not the issue). After our search is over  the search bar which blocks the calendar wont go unless you click on the search button which is on to the top right of the application.And the search button is not near the search bar so there is no way one would guess that we should click on the search button again.The screen shot is attached below.So better way for it to close is if we click anywhere except the search bar,just like the other two buttons right to the search button.
Comment 1 Mohammed Sadiq 2017-02-19 01:12:59 UTC
*** Bug 778890 has been marked as a duplicate of this bug. ***
Comment 2 Georges Basile Stavracas Neto 2017-04-28 20:53:27 UTC
This issue is actually being tracked in bug 747962. Closing as a duplicated.

*** This bug has been marked as a duplicate of bug 747962 ***