GitLab

PPD_CUSTOM_UNKNOWN was introduced in cups 2.3.
and has been backported to 2.2.12.
Only handle it when we build against a new enough cups.

Fixes: #2968

Matthiasc/for master

See merge request !2741

To make this possible enable the doc shooter
to take screenshots of popovers.

Show the new palette.

Now that the volume button image is small, move it
to a better place in its section. Improves the layout.

Give up on showing the popup, we don't do that
for other buttons either.

It has been missing far too long.

Improve the breaks in the container section.

Makes it fit better with the other entries.

Align things better.

Make the GtkPicture gallery image stay within its
limits, by overpowering its request mode.

Move GtkSpinButton to the entries, where it
belongs, despite its name.

It turns out gtk-doc can't even parse its own custom
links if you don't arrange for the <link> element to
on a single line, since it is just a glorified sed
script :(

Test some of the attributes that GTK maintains
for every widget.

This ensures that keybindings for small-step changes
work despite draw-value being FALSE now. This was
fallout from 8ca612c9 that showed up
as arrow keys not working anymore for the color scales
in the color chooser.

Remove some comments that refer to no longer
existing menu code.

Turn more options into "feature"

See merge request !2708

Flush events

See merge request !2740

The current code was marking queued events as flushed,
but left them in the queue. That doesn't make sense to
me - we should deliver all events we have before we
reach the paint phase of the frame cycle.

Matthiasc/for master

Closes #3226

See merge request !2739

Unparenting the stack finalizes the entry and label,
but at least the label is available via the
gtk_editable_get_delegate API, and the a11y
implementation uses that at dispose time. So, clear
the pointers to prevent them from being dangling.

This was showing up as a segfault of the doc-shooter.

This was first requested for the search entry in
GtkDropDown, but it is better to be consistent and
give every search entry an icon.

Related: #3291

When the compositor unmaximized the window, we get a
state-changed signal, and we update the maximized field.
But then we go and recompute our layout based on the
maximize_initially field, and that is still TRUE, when
we were maximized initially. So we need to update both
fields.

This fixes a problem where using the window menu to
unmaximize an initially maximized window would not
work.

Fixes: #3226

Matthiasc/for master

See merge request !2737

These tests are a bit fragile because the initial focus
that is taken depends on what ends up in the center of
the window, horizontally or vertically, which depends
on things like fonts, or theme spacing.

This commit makes some tweaks to push things in the
widget-factory example around far enough to make the
tests work again.

We should figure out a way to make this more robust.

Ebassi/for master

See merge request !2735

A small detail for #3291.

We are not using a box layout here since we want
to ignore the icons for measuring. But we still
want the layout to respect border spacing that
comes from the theme.