GNOME Bugzilla – Bug 720764
GdTaggedEntryTag: Fix close button states
Last modified: 2013-12-19 22:54:02 UTC
When clicking on a tag's close button, the close buttons of all tags where drawn with the active state (well, except the button you actually clicked on, which kept showing the hover state), because of a wrong if-clause and setting two states at the same time. I'm not sure if it is necessary to avoid setting GTK_STATE_FLAG_ACTIVE and GTK_STATE_FLAG_PRELIGHT at the same time on the tag buttons, I guess ACTIVE should take precedence here, but I'll leave that to the CSS experts to figure out.
Created attachment 264564 [details] [review] GdTaggedEntryTag: Fix close button states
Created attachment 264565 [details] [review] GdTaggedEntryTag: Fix close button states When clicking on a tag's close button, the close buttons of all tags where drawn with the active state (well, except the button you actually clicked on, which kept showing the hover state), because of a wrong if-clause and setting two states at the same time. I'm not sure if it is necessary to avoid setting GTK_STATE_FLAG_ACTIVE and GTK_STATE_FLAG_PRELIGHT at the same time on the tag buttons, I guess ACTIVE should take precedence here, but I'll leave that to the CSS experts to figure out.
Attachment 264565 [details] pushed as 0a9a80e - GdTaggedEntryTag: Fix close button states