Ryan Lortie bc3867eb85 GtkApplicationWindow: give up on handling dispose ... Stop trying to deal with "theoretical possibilities". We can't possibly continue to be a faithful GActionGroup implementation across dispose because dispose has a side effect of removing everyone's signal handlers. The code that we ran after the dispose chainup to do all of the fancy signal emulation was therefore dead. The test that aimed to verify this was buggy itself due to an uninitialised variable, so really, it never worked at all. We keep the re-ordering of the chainup from the original commit to avoid having trouble with GtkActionMuxer and keep the checks in place that will prevent an outright segfault in the case that someone else tries to use the interface post-dispose. https://bugzilla.gnome.org/show_bug.cgi?id=722189		2014-01-14 10:41:35 -05:00
..
a11y	Add some treeview a11y tests	2014-01-13 23:51:26 -05:00
css	testsuite: Ignore generated .test files	2013-07-11 12:57:06 -04:00
gdk	testsuite: Ignore generated .test files	2013-07-11 12:57:06 -04:00
gtk	GtkApplicationWindow: give up on handling dispose	2014-01-14 10:41:35 -05:00
reftests	reftests: Add reftest for 0px border fix	2014-01-14 03:38:04 +01:00
Makefile.am	build: Move tests/reftests to testsuite/reftests	2013-05-15 15:37:17 +02:00