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 756731 - Style classes not taken into account on custom widgets inclusions
Style classes not taken into account on custom widgets inclusions
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Class: GtkBuilder
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: GtkBuilder maintainers
GtkBuilder maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-17 03:40 UTC by Arnaud B.
Modified: 2018-04-15 00:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Hello World. (92 bytes, text/plain)
2015-10-17 23:01 UTC, Arnaud B. 		Details
Hello World. (2.11 KB, application/x-xz)
2015-10-18 17:23 UTC, Arnaud B. 		Details

Description Arnaud B. 2015-10-17 03:40:44 UTC 
May that be related to a similar bug with construct-only properties[1]?

In Dconf Editor[2], I have an “image-button” style class written in the (template) file “editor/bookmarks.ui”[3], that is not correctly applied to its widget constructed from the (template) file “editor/dconf-editor.ui”[4]. Writing the style class in “editor/dconf-editor.ui” works as expected.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=744324
[2] https://git.gnome.org/browse/dconf-editor/tree/?id=a53621b56a78f68a4fa470bc766b260c3d4927d7
[3] https://git.gnome.org/browse/dconf-editor/tree/editor/bookmarks.ui?id=a53621b56a78f68a4fa470bc766b260c3d4927d7#n99
[4] https://git.gnome.org/browse/dconf-editor/tree/editor/dconf-editor.ui?id=a53621b56a78f68a4fa470bc766b260c3d4927d7#n47
Comment 1 Matthias Clasen 2015-10-17 15:24:50 UTC 
What does 'not correctly applied' mean, exactly ? it is not applied ? or it is applied but does not affect the visuals ? does it show up in the inspector ?
Comment 2 Matthias Clasen 2015-10-17 15:25:56 UTC 
The most likely explanation is that it gets overwritten when the button constructs its contents.

A small, self-contained testcase would help a lot.
Comment 3 Arnaud B. 2015-10-17 23:01:51 UTC 
Created attachment 313596 [details]
Hello World.
Comment 4 Arnaud B. 2015-10-17 23:02:58 UTC 
Not sure it helps a lot, but this is a quite little Vala program showing the problem.
Comment 5 Matthias Clasen 2015-10-18 13:48:10 UTC 
Doesn't look like a vala program to me.
Comment 6 Arnaud B. 2015-10-18 17:23:11 UTC 
Created attachment 313626 [details]
Hello World.

/o\ Bugzilla is a so complicated thing at 1 AM…
Comment 7 Matthias Clasen 2018-02-10 05:08:53 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 8 Matthias Clasen 2018-04-15 00:33: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