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 786483 - Backport CSS border-spacing to GTK+ 3.22?
Backport CSS border-spacing to GTK+ 3.22?
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Class: GtkStyleContext
3.22.x
Other All
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-08-18 19:33 UTC by Daniel Boles
Modified: 2018-05-02 18:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Boles 2017-08-18 19:33:46 UTC 
commit 0eecc6f686f6c4a23549d2185e842d0fafa9b17b added this to GTK+ 4 as a theme-based replacement for Box::spacing and Grid::(row|column)-spacing.

Although I acknowledge unlikely - if possible, it would be really nice to sneak this into GTK+ 3.

Currently in order to do spacing there in CSS - which is preferable both semantically and because it e.g. enables spacing based on font size (via r/em units) - some mind-bending hacks with classes and margins seem to be required - especially if the spacing has any degree of variability, whereupon SASS seems to become near-essential to generate all the required boilerplate, and that of course means the possible spacings must be known at sassc-time.


This was requested as part of Bug 762397, and while the title of that was fixed, it was left open for a different purpose, namely getting border-spacing. Since I meant to open this one a while ago, we can close that other one - and maybe this one too, but at least it will be clear what's been resolved and what hasn't. :)
Comment 1 GNOME Infrastructure Team 2018-05-02 18:52:39 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/880.