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 703253 - Unable to specify CSS transition based on start and end state
Unable to specify CSS transition based on start and end state
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Class: GtkStyleContext
3.9.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-06-28 13:48 UTC by Allan Day
Modified: 2018-04-15 00:11 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8



Description Allan Day 2013-06-28 13:48:12 UTC
GTK+'s CSS theming doesn't provide a way to specify transitions
according to beginning and end states. Instead, each style class can
have a transition associated with it, and it is triggered whenever
that style is applied.

The problem is that, in order to use CSS transitions, we need to specify which transition should be used depending on the start and end point. For example:

insensitive button > sensitive button : fast transition
sensitive button > hovered button : slow transition
insensitive button > hovered button : fast transition

Without this specificity, it's not really possible to make use of CSS transitions.

https://mail.gnome.org/archives/gtk-devel-list/2013-May/msg00043.html
Comment 1 Allan Day 2014-07-21 10:48:33 UTC
It's worth checking with Lapo and Jakub about whether this bug is needed, since I think that they are using CSS transitions in Adwaita now.
Comment 2 Daniel Boles 2017-08-15 20:26:36 UTC
Hi all - is this still a problem?

Transitions can be applied to any property by any selector, so my guess is that the requested patterns can be done - though in reality the themes use 200 ms for transitions everywhere or near-as.
Comment 3 Matthias Clasen 2018-04-15 00:11:03 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new