| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is causing warnings now that make the tests fail.
|
|
|
|
|
|
|
| |
The reftest depends on a schema we install ourselves. Instruct GIO to
look in the build directory to avoid a cyclic dep.
https://bugzilla.gnome.org/show_bug.cgi?id=768930
|
| |
|
|
|
|
|
| |
GdkDrawingContext is not freely constructible, so we need
to skip it in the notify and finalize tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously a style cascade's parent could not have a parent itself. That
represented the two levels at which you could add a style provider: at
the screen level, with gtk_style_context_add_provider_for_screen(), and
at the style context level, with gtk_style_context_add_provider().
This commit changes no functionality, but this change will be necessary
for adding style providers in the future that apply to a subtree of the
widget tree. It relaxes the requirement that a style cascade's parent
must not have a parent, since in the future a style context may be
affected by any number of parent widgets' style contexts.
https://bugzilla.gnome.org/show_bug.cgi?id=751409
|
|
|
|
|
|
| |
The maximum content size does not increase the minimum request
but only ensures that both minimum and natural requests do not
exceed the maximum setting.
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 023f406c9617284ee3b88727df489f20cd066fd6 has a typo that results
in this error:
../../../testsuite/gtk/notify.c: In function 'test_type':
../../../testsuite/gtk/notify.c:679:54: error: expected expression
before ')' token
(g_str_equal (pspec->name, "max-content-width") ||)
^
|
|
|
|
|
|
|
| |
The allowed values for the max-content- properties depend
on the value of the min-content- properties, in a way that
our simple test is not prepared to deal with. Just skip
them for now.
|
|
|
|
|
|
|
| |
Old patch found in bugzilla, it still applies and doesn't
cause the test to fail.
https://bugzilla.gnome.org/show_bug.cgi?id=556254
|
|
|
|
|
|
|
|
| |
This patch adds a set of tests for scrolled window
sizing, covering both min- and max-content width and
height.
https://bugzilla.gnome.org/show_bug.cgi?id=742281
|
|
|
|
| |
These changes were caused by the introduction of GtkStackAccessible.
|
|
|
|
|
| |
We no longer add the redundant .slider style class in GtkSwitch.
Update expected results to reflect that.
|
|
|
|
|
| |
We were not propagating direction changes in some places,
evidently. Now we do.
|
|
|
|
| |
The style classes are reflected in the output here.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=373745
|
|
|
|
| |
Verify rebeccapurple too.
|
|
|
|
|
| |
We never return NULL for ::geometry and ::workarea. Just skip
these properties.
|
| |
|
| |
|
|
|
|
|
| |
These tests were affected by the font and linear-gradient parsing
changes.
|
|
|
|
| |
This is not freely settable.
|
|
|
|
| |
Surprisingly we had no unit test for this method
|
|
|
|
| |
Test more of the syntax of the font: shorthand.
|
|
|
|
|
|
|
|
|
| |
Setting the font: shorthand to something like smaller is not
in line with the css spec. Just set the font-size: property
for this.
Also fix the other font: shorthand to specify size and family
according to the css spec.
|
| |
|
|
|
|
|
|
| |
The default font size of 10pt will now properly render as 13.33px,
but we shouldn't use the default anyway as that can be controlled
by user settings
|
| |
|
| |
|
|
|
|
| |
bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=764686
|
|
|
|
|
| |
In particular, we're testing corner cases with empty rectangles
here.
|
| |
|
|
|
|
| |
These are just some basic sanity tests.
|
|
|
|
|
| |
All the 'make check' and installed tests are now in testsuite/,
and tests/ is just a collection manual test programs.
|
|
|
|
|
| |
These are just basic tests to ensure that the visual implementation
of a backend is sound.
|
|
|
|
|
| |
The main point of this test is to ensure that the pixel_details
getters work as expected.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit a4ed154b037aaf03f8c166a711c326a030225eed.
The misparsing that is tested here will not be fixed in 3.20,
so keep this test out of the stable branch.
|
| |
|
|
|
|
|
| |
I've made this change for installed tests a while ago. It doesn't
make sense for distcheck to do it differently.
|
|
|
|
|
|
| |
This test has a word that wouldn't fit in the room we have with
a window width of 100, and then we get clipped in the one case
but not the other. Make the window a little wider, so it fits.
|
|
|
|
|
|
|
| |
We were computing the wrong progress, in particular when the iteration
count was non-integer.
Test included.
|
|
|
|
|
| |
This one was causing us to install invalid .test files and thereby
breaking all continuous tests :-(
|
|
|
|
|
| |
This was causing the tools tests to not be installed and,
consequently, never run on continuous.
|
|
|
|
|
| |
Small thinko: We only get to see the test artifacts in
continuous if the test fails. So make it fail, temporarily.
|
|
|
|
|
|
| |
With csd, the allocation of the window will be larger than the
default size, since it includes borders and decorations. Just
remove this check.
|
|
|
|
|
|
| |
This is not much of a test, tbh. But it will give us a convenient
dump of all GTK+ settings in continuous, which helps with tracking
down test failures that might depend on settings.
|
|
|
|
| |
These tests can now assume that the csd header bar will be there.
|
|
|
|
|
| |
This avoids differences in the output that are caused
by the presence or absence of the header bar.
|