filechooser: Document the settings XML
Avoid compiler warnings
Update Kazakh translation
Make testtitlebar more versatile

Test adding multiple custom widgets at each end. This exposes
that we're doing it wrong - the pack-end widgets are ordered
in the wrong way.
GtkHeaderBar: Fix positioning of pack-end widgets

This makes the positioning of pack-start and pack-end
widgets symmetric.
Updated Spanish translation
Updated Spanish translation
Add GtkActionBar

A widget intended to offer contextual actions for a given view.
It allows packing children into the start or end as well as offering
a single centered child box.

https://bugzilla.gnome.org/show_bug.cgi?id=721665
tests: use actionbar in headerbar test

This is a great example of where headerbar should not be used.

https://bugzilla.gnome.org/show_bug.cgi?id=721665
widget-factory: add actionbar

https://bugzilla.gnome.org/show_bug.cgi?id=721665
Fix order of pack-end widgets

https://bugzilla.gnome.org/show_bug.cgi?id=721665
Add an action bar test

https://bugzilla.gnome.org/show_bug.cgi?id=721665
Updated Hungarian properties translation
Make testsplitheaders more robust

Same empty string issue that I fixed in GtkHeaderBar a few days
ago.
Release-note the headerbar child order change
GtkActionBar: Just leave the center widget as NULL, initially

No need to construct a box that gets thrown away later.
Plus, this fixes the defaultvalue test for GtkActionBar.
Updated POTFILES.in
Add a reftest for GtkActionBar child ordering

This shows that GtkActionBar and GtkBox treat pack-start/-end
the same.
Fix GtkApplicationWindow action group implementation

GtkApplicationWindow frees its internal action group on dispose for the
usual reasons: to avoid the possibility of reference cycles caused by
actions referring back to the window again.

Unfortunately, if it happens to be inside of a GtkActionMuxer at the
time that it is disposed, it will (eventually) be removed from the muxer
after it has been disposed.  Removing an action group from a muxer
involves a call to g_action_group_list_actions() which will crash
because the internal action group to which we normally delegate the call
has been freed.

A future patch that reworks the quartz menu code will introduce a use of
GtkActionMuxer in a way that causes exactly this problem.

We can guard against the problem in a number of ways.

First, we can avoid the entire situation by ensuring that we are removed
from the muxer before we destroy the action group.  To this end, we
delay destruction of the action group until after the chain-up to the
dispose of GtkWindow (which is where the window is removed from the
GtkApplication).

Secondly, we can add checks to each of our GActionGroup and GActionMap
implementation functions to check that the internal action group is
still alive before we attempt to delegate to it.

We have to be careful, though: because our _list_actions() call will
suddenly be returning an empty list, people watching the group from
outside will have expected to see "action-removed" calls for the
now-missing items.  Make sure we send those. but only if someone is
watching.

https://bugzilla.gnome.org/show_bug.cgi?id=710351
app window: test actiongroup across destroy

Make sure that we don't violate the interface contract of GActionGroup
just because gtk_widget_destroy() was called.

https://bugzilla.gnome.org/show_bug.cgi?id=710351