| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
We already have the depth of a tree expander in order to compute the
indentation.
Fixes: #3892
|
| |\
| |
| |
| |
| |
| |
| | |
window: Fix up resize borders
Closes #3856
See merge request GNOME/gtk!3467
|
| | |
| |
| |
| |
| | |
As pointed out by Alberts Muktupāvels, without this,
we are missing the inner edge of the frame.
|
| | |
| |
| |
| |
| | |
The selectors did not apply anymore.
Based on a patch by Alberts Muktupāvels.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Deriving the resize border size from the shadows
carries the risk that we might end up with uneven
resize borders (or none at all, on some sides).
So, justs enforce that we have a big enough shadow
width on all sides.
|
| | |
| |
| |
| |
| |
| | |
Make windows resizable in the padding and border
area of the css box as well. This naturally makes
solid-csd borders work again.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The invisible resize borders have been wider than they
should, for a while. Go back to a size close to what
we have in GTK3.
To summarize: resize borders will be at most 12 pixels
on each size, but never wider than the windows shadow.
The resize corners have 'legs' of 24 pixels where you
still get a corner resize cursor.
Fixes: #3856
|
| |\ \
| | |
| | |
| | |
| | | |
Some a11y improvements
See merge request GNOME/gtk!3455
|
| | | |
| | |
| | |
| | |
| | | |
Whenever we change the :child property, we need to update the
labelled-by relation.
|
| | | |
| | |
| | |
| | | |
Instead of setting it on its internal child.
|
| | | |
| | |
| | |
| | |
| | | |
Orca needs both events in order to decide whether or not to subscribe to
other event/state changes in a window.
|
| | | |
| | |
| | |
| | |
| | | |
We're not moving focus here, so we can't rely
on that to conjure the a11y objects into existence.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only send selection-changed events when we either
had a non-empty selection before, or have one now.
This should help orca speak the right things, and
not the wrong things.
Related: #3549
|
| | | |
| | |
| | |
| | |
| | | |
Orca uses the window:activate event type to track top levels, and avoid
being spammed by events coming from non-focused windows.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This makes the tabs in about dialogs come out as
'About', 'Credits', and 'System', instead of
'Tab', 'Tab', 'Tab'.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Orca relies on these to keep track of the focus location,
ignoring the focused state. With this change, orca can
once again speak text in entries as I type.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We are starting with a pretty empty a11y object tree,
and we want orca to bring more of it into existence
by navigating the tree. But that only happens when we
send it events. Primarily focus events, which come in
from GTK via the platform_change mechanism. So realize
the context when we are sending platform_changes,
otherwise, orca never gets the mesage.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With most context realization happening inside
GtkAtspiContext in response to D-Bus calls, the
code in gtk_widget_realize_at_context that sets
the role is not executed for most accessibles,
causing them to be stuck with the 'filler' role
that makes orca ignore them.
To fix this, split gtk_widget_realize_at_context
into the actual context realization (getting on
the bus) and the setting of widget-specific
properties, and do the latter part when the
widget is rooted.
This makes accerciser report proper roles for
entries and buttons. Orca still has an issue
with getting the hierarchy populated.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Orca ignores events unless the object is inside an object
with role window and states ACTIVE and SHOWING. To arrange
for this, introduce a new ACTIVE platform state, and set it
for windows when they are active.
This gets orca to be a lot more talkative.
|
| | | |
| | |
| | |
| | |
| | | |
Not 100% sure this is necessary, but maybe it helps
to get orca up to speed.
|
| | | |
| | |
| | |
| | | |
We don't make any use of the cache field, so drop it.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
imcontextsimple: Ignore more modifiers in compose
See merge request GNOME/gtk!3468
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously it was impossible to compose characters on higher levels of
some keyboard layouts as pressing the level selection key would just
exit compose mode.
Examples for affected keyboard layouts include the Latvian
apostrophe-variant "lv(apostrophe)" (latched third level), the extended
German keyboard layout "de(e1)" (latched fifth level) as well as the
multilingual Canadian keyboard layout "ca(multix)" and the German
neo-layout "de(neo)" and its descendants (shifted fifth level).
To reproduce, set a compose key and select the Latvian apostrophe layout.
Notice that you now can input [ by pressing first the ' and then the 8-key.
Then pressing <compose>'8'8 should produce ⟦, but prior to this patch it
did not.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
theme: fix solid-csd style
See merge request GNOME/gtk!3460
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Move .solid-csd style out of .csd parent and adjust it so windows
look similar / same to GTK 3 windows:
- 4px padding.
- extra shadow.
https://gitlab.gnome.org/GNOME/gtk/-/issues/3879#note_1086351
https://gitlab.gnome.org/GNOME/gtk/-/issues/3879#note_1086377
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
imcontext: Fix cursor positions
Closes #3885
See merge request GNOME/gtk!3464
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
gtk_im_context_get_preedit_string is documented to
return the cursor position as a character offset,
not a byte count. So return that.
Fixed: #3885
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
placesview: Open location even if mount was not found
Closes nautilus#1811
See merge request GNOME/gtk!3435
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some locations have to be mounted, but their mounts are not user-visible
(e.g. smb-browse). Though this is maybe a bit weird, it is how it works
for years. The problem is that the commit 267ea755, which tries to get the
default location for opening, caused regression as it doesn't expect such
possibility. Before this commit, such locations were opened without any
issue, but nothing happens currently after clicking to "Connect" except of
clearing the "Connect to Server" entry. Let's fallback to the original
location if the mount was not found to fix this regression.
Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1811
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
x11: Don't beep on untrusted displays
Closes #3862
See merge request GNOME/gtk!3463
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
This can trigger BadAccess, and we don't
want that.
Fixes: #3862
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Fix a possible crash in gtk_show_uri
Closes #3883
See merge request GNOME/gtk!3457
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
g_file_get_basename can return NULL.
Deal with it somehow.
Fixes: #3883
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
gsk: Fix shader gresource paths
See merge request GNOME/gtk!3453
|
| | | |
| | |
| | |
| | | |
They were never updated after having been moved.
|
| | | |
| | |
| | |
| | | |
(cherry picked from commit 2a8fd6a4880c6e484cb8be081dff32095033cf2a)
|
| |/ /
| |
| |
| | |
(cherry picked from commit 4e243d7d121eac1743f4103ff8af8bc3caba0c99)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
gtksecurememory: Request that secure memory not be dumped to disk
See merge request GNOME/gtk!3452
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Linux 3.4 added support for the MADV_DONTDUMP option to madvise(), which
requests that the covered memory not be included in coredumps. It makes
sense to use this to prevent cases where application crashes could
result in secrets being persisted to disk or included in dumps that are
uploaded to remote servers for analysis. I've avoided making this fatal
since there's a chance this code could be built on systems that have
MADV_DONTDUMP but run on systems that don't.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
testatcontext: Print out platform changes
See merge request GNOME/gtk!3451
|
| | | | |
| | | |
| | | |
| | | | |
This is in an attempt to figure out why orca won't speak.
|
| |/ / /
| | |
| | |
| | | |
This helps debugging what changes orca sees.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
image, picture: Move pixbuf code to gdkpixbufutils
See merge request GNOME/gtk!3449
|
| | | | |
| | | |
| | | |
| | | | |
We weren't properly resetting the in-entry progress.
|
| | | | |
| | | |
| | | |
| | | | |
This was broken by a stupid copy-paste error.
|
| | | | |
| | | |
| | | |
| | | | |
Fix up the dialog minimally.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Rely on the gdkpixbufutils api that gives us
a paintable.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
This cleans up and moves the code to load files
while taking the scale into account. Along the way,
we drop the last uses of GdkPixbufAnimation, and
consolidate the pixbuf using code in one place.
|
