| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Use gtk_text_iter_starts_tag() instead.
https://bugzilla.gnome.org/show_bug.cgi?id=759092
|
|
|
|
| |
We use these cursors in GTK+, so check for their existence.
|
|
|
|
|
|
|
|
| |
GtkStatusIcon tests don't work well under xwayland either, so just
skip them unconditionally.
GtkEntry now fails because the update of the im-module is no longer
deferred to an idle, and (gtk-im-simple) is not a valid module
name, so skip this property.
|
|
|
|
|
| |
Add a test that ensures that missing images get the icon-effect properly
applied.
|
|
|
|
| |
This will be used for drag highlighting.
|
|
|
|
| |
This is a property for icons, so we should name it as such.
|
|
|
|
|
|
|
| |
Instead of just working for image surface, this should now work for all
bounded surfaces.
Test included.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'win.lines' contains the same content as the GtkTextBuffer, so to find
@match_start, forward_chars_with_skipping() is called with
skip_decomp=FALSE (the last parameter). So far so good.
On the other hand, the content 'lines' (the needle split in lines) is
casefolded and normalized for a case insensitive search. So,
forward_chars_with_skipping(..., skip_decomp=TRUE) must be called only
for the portion of text containing the needle.
Since 'start_tmp' contains the location at the start of the match, we
can simply begin at that location to find the end of the match.
Unit tests are added.
https://bugzilla.gnome.org/show_bug.cgi?id=758698
|
| |
|
|
|
|
|
|
|
|
|
| |
This makes custom CSS properties no longer configurable. But it avoids
crashes when loading custom themes, so that's a good thing.
Testcase included.
https://bugzilla.redhat.com/show_bug.cgi?id=1281234
|
|
|
|
|
|
| |
For some reason, GtkFileChooserNative is causing the defaultvalue
test to fail. I couldn't track this down quickly, so skip the
type for now.
|
|
|
|
|
| |
Without iterating a mainloop for a bit, g_test_dbus_down() will
give us an error.
|
|
|
|
|
|
|
|
|
|
|
|
| |
When loading a nonexisting CSS file using
gtk_css_provider_load_from_file() or gtk_css_provider_load_from_path()
we would emit the error using a NULL scanner. Don't do that, because
we'll have a NULL section in that case and error handlers don't like
that.
Testcase attached.
https://bugzilla.redhat.com/show_bug.cgi?id=1277959
|
|
|
|
|
| |
Add an E + F selector to the selector parsing tests.
It is a CSS selector that we support.
|
|
|
|
| |
Otherwise, we are causing warnings that break make check.
|
|
|
|
|
| |
Like all the other GtkFileChooser implementations, this one
emits some unneeded notifications.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid crashes when passing an invalid location to a
gtk_text_buffer_get_iter_at_*() function.
A first attempt added boolean return values to know if @iter has been set to
the exact location, but it breaks Python and JS bindings because the out
parameter is already a return value in those languages.
Unit tests are added.
https://bugzilla.gnome.org/show_bug.cgi?id=735341
|
|
|
|
|
|
|
|
| |
This reverts commit a9a1c00cc9255ee9a7f73695f69abe172cde7bfa.
Unfortunately, adding the boolean return broke both the python
and javascript bindings, since they now return a tuple consisting
of the boolean and the out argument.
|
|
|
|
|
| |
These tests have either been commented out for way too long or use APIs
that we don't want to support.
|
|
|
|
|
|
|
|
|
| |
Signal handlers expect a section to be present, so provide them with
one.
New testcase included.
https://bugzilla.gnome.org/show_bug.cgi?id=757240
|
|
|
|
|
|
| |
Multiple reftests were damaged by the element name transition.
Repair them. The region reftests are no longer needed, since
we no longer do regions.
|
|
|
|
|
| |
Don't try setting GtkShortcutsShortcut::accelerator to a
random value, it only accepts strings that it can parse.
|
|
|
|
| |
We generally use ->next directly.
|
|
|
|
| |
These tests contain non-canonical and non-existing property names.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid crashes when passing an invalid location to a
gtk_text_buffer_get_iter_at_*() function.
A boolean is returned to know if @iter has been set to the exact
location.
Unit tests are added.
https://bugzilla.gnome.org/show_bug.cgi?id=735341
|
|
|
|
|
| |
Test appending text as well as replacing the entire text.
Insert non-ASCII text to verify offsets are correct.
|
|
|
|
|
|
|
| |
After figuring out what the actual problem is, name the reftest
properly.
The actual problem is that the use-fallback property is ignored when
using an icon-name on GtkImage.
|
|
|
|
|
|
|
|
|
| |
Fallback seems to be working in the GtkIconTheme test suite, but fails
in GtkImage itself.
This is a test for a bug in the Bluetooth settings. An icon named
"phone-apple-iphone" should fallback to "phone" if the
gnome-icon-theme-extras package isn't installed.
|
|
|
|
| |
This test failed before the previous commit.
|
| |
|
|
|
|
|
|
| |
Plug and Socket require X11 windowing. Often times this is compiled
on systems with both wayland and x11, but not always. Quartz is an
example where it is usually not compiled.
|
|
|
|
|
|
| |
The script uses bash features, after all.
https://bugzilla.gnome.org/show_bug.cgi?id=755274
|
|
|
|
|
|
|
|
| |
The speed-up in 7da1f8a1ce145f48b6299fd8be86a64389ff0b0d was wrong in
certain conditions, even though it didn't trigger the existing
testsuite.
New testcase /bitmask/invert_range_hardcoded included.
|
|
|
|
| |
GLib considers these an bug now.
|
|
|
|
|
| |
Skip tests that don't work under Wayland, such as tests for GtkPlug
and GtkSocket.
|
|
|
|
|
| |
This test really only works under X, since it relies on modifying
the DISPLAY env var.
|
|
|
|
|
|
| |
Makefile.decl does not work well with scripts that stay
in srcdir, so generate test-simplify from test-simplify.in,
just os that it ends up in builddir.
|
|
|
|
|
| |
Underlines now need to be manually specified in CSS since GTK got
text-decoration support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Yo, we heard you like traversing NULL-terminated arrays to operate on
them, so we called g_strv_length() as the for condition, so you can
iterate the array while iterating the array."
Instead of making famed rapper and television producer Xzibit proud, we
should avoid calling g_strv_length() on an array while looping on the
array, to avoid quadratic complexity.
We do this in various places that deal with arrays of strings that we
cannot really guess are short enough not to matter — e.g. the list of
CSS selectors in the inspector, or the required authentication
information for printing.
|
|
|
|
|
| |
Support letter-spacing CSS property on GtkLabel.
Reftest is included.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the unpremultiplied values from the GdkRGBA were taken. Now
we premultiply the color values as specified by the CSS specs.
This is only relevant when transitioning with translucent colors.
An example is the halfway transition between transparent (0, 0, 0, 0)
and white (1, 1, 1, 1). Previously, all 4 values where transitioned
separately and the result was semi-transparent gray (0.5, 0.5, 0.5,
0.5).
By depending on the alpha value, the result is now semi-transparent
white (1, 1, 1, 0.5) which is what one would naively expect.
New reftest: color-transition
|
|
|
|
|
| |
These changed due to th extra box that GtkAssistant now
inserts for each page.
|
|
|
|
|
|
| |
Fixes reftests.
https://bugzilla.gnome.org/show_bug.cgi?id=750605
|
|
|
|
|
|
| |
To verify the previous fix.
https://bugzilla.gnome.org/show_bug.cgi?id=750605
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
On some slower machines (e.g. an ARM OBS builder), this test is failing
with a race condition where we're trying to fetch the style before it's
applied.
https://bugzilla.gnome.org/show_bug.cgi?id=749593
|
|
|
|
|
| |
The output of the about dialog test is affected by the keynav
fixes.
|
|
|
|
| |
Don't spew so many 0s and 1s.
|
|
|
|
|
|
| |
Don't test types that rely on a pre-existing dbus session bus.
https://bugzilla.gnome.org/show_bug.cgi?id=749009
|