Collectively, these commits get rid of all CSS warnings printed during application startup. See individual commit messages for details.
However, I’m not sure if this is a good idea. The warnings are a bit annoying (especially when they end up polluting the journal, as is the default when launching the app from a GNOME desktop), but on the other hand this will remove compatibility with some older GTK+ releases: specifically, we would now require GTK+ 3.19.6 (just under three years old as of this writing) or newer. Are we likely to have users that need compatibility with older GTK+ versions?
Collectively, these commits get rid of all CSS warnings printed during application startup. See individual commit messages for details.
However, I’m not sure if this is a good idea. The warnings are a bit annoying (especially when they end up polluting the journal, as is the default when launching the app from a GNOME desktop), but on the other hand this will remove compatibility with some older GTK+ releases: specifically, we would now require GTK+ 3.19.6 (just under three years old as of this writing) or newer. Are we likely to have users that need compatibility with older GTK+ versions?