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 724096 - search-bar: don't show the widget until we're ready to reveal
search-bar: don't show the widget until we're ready to reveal
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 738354 754243 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-02-11 04:47 UTC by William Jon McCann
Modified: 2018-02-13 16:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
search-bar: don't show the widget until we're ready to reveal (2.98 KB, patch)
2014-02-11 04:47 UTC, William Jon McCann
rejected Details | Review
Only add search-bar style class when revealed (2.12 KB, patch)
2014-12-03 05:25 UTC, Trinh Anh Ngoc
none Details | Review
Screenshot (37.01 KB, image/png)
2014-12-03 05:25 UTC, Trinh Anh Ngoc
  Details

Description William Jon McCann 2014-02-11 04:47:40 UTC
Apps that use a searchbar have a spurious border visible when
the searchbar isn't revealed. You can see this in devhelp or
in gtk demo.
Comment 1 William Jon McCann 2014-02-11 04:47:42 UTC
Created attachment 268753 [details] [review]
search-bar: don't show the widget until we're ready to reveal

Otherwise we leave a border visible.
Comment 2 Matthias Clasen 2014-02-13 12:27:03 UTC
After debugging a little, the problem here is that we enforce the allocation of visible widgets to be at least 1x1. This is a historic relic from when every widget had a window (X11 windows must be at least 1x1).

The real fix here is to take out that restriction. The core of GTK+ should not have any assumptions about minimum widget size, and window widgets should just request a suitable minimum size.
Comment 3 Bastien Nocera 2014-09-20 16:35:57 UTC
This problem has 4 duplicates in totem's repo. Could we use Jon's hack until we really fix it?
Comment 4 Matthias Clasen 2014-10-12 11:42:41 UTC
*** Bug 738354 has been marked as a duplicate of this bug. ***
Comment 5 Trinh Anh Ngoc 2014-12-03 05:24:20 UTC
https://github.com/GNOME/gtk/commit/8fcf3a8e882844023b0118b7d47cb2bd556623fd

This commit does not work for me. I still get search bar border leak. I made a patch for this.
Comment 6 Trinh Anh Ngoc 2014-12-03 05:25:11 UTC
Created attachment 292039 [details] [review]
Only add search-bar style class when revealed
Comment 7 Trinh Anh Ngoc 2014-12-03 05:25:42 UTC
Created attachment 292040 [details]
Screenshot
Comment 8 Trinh Anh Ngoc 2014-12-03 05:26:23 UTC
The patch is not perfect. Need better solution.
Comment 9 Allan Day 2015-01-27 12:35:17 UTC
I'm confused about the status of this bug.

1. The status is fixed, but I don't see any committed patches, and Trinh Anh Ngoc is apparently still working on it. Is it fixed or not?

2. The screenshot in comment #7 doesn't seem to actually show the search bar or the problem as reported (since the problem is only apparent when the search bar is supposed to be hidden).
Comment 10 Trinh Anh Ngoc 2015-01-27 13:23:57 UTC
Allan. That screenshot was taken after applying my patch.

Matthias Clasen with his commit:
https://github.com/GNOME/gtk/commit/8fcf3a8e882844023b0118b7d47cb2bd556623fd
But it didn't solve the problem.
Comment 11 Matthias Clasen 2016-01-23 06:34:54 UTC
*** Bug 754243 has been marked as a duplicate of this bug. ***
Comment 12 Matthias Clasen 2018-02-10 05:12:04 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 13 Bastien Nocera 2018-02-13 16:16:28 UTC
I took screenshots of devhelp with and without the patch, and there were no differences visible using devhelp.

Trinh, please reopen if the problem persists, and update your patch as well. Thanks!