Commits on Source (20)
-
Scrambled 777 authored
-
Jose Riha authored
-
Chao-Hsiung Liao authored
-
AsciiWolf authored
-
Florian Müllner authored
Now that we no longer provide a portal implementation ourselves, the only expected callers are the GNOME portal implementation and (since recently) the remote desktop daemon. Make that explicit and restrict callers to these senders, like we do for other D-Bus APIs. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3411> (cherry picked from commit 1a12bd4f)
-
Florian Müllner authored
Instead, use CSS to request a monospace font selectively where it makes sense (the evaluator). Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7776 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3413> (cherry picked from commit 6f2c9914)
-
Florian Müllner authored
All styling currently happens on the ScrollView child, which means that instead of a scrollbar inside the dialog to move the content, we have a scrollbar next to the dialog that moves the dialog as a whole. Fix this by simply moving the style classes to the up-most parent. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3414> (cherry picked from commit 811a4103)
-
Sohrab Behdani authoredRemove duplicate and unnecessary keys, and add missing ones (e.g. ZWNJ). Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3409> (cherry picked from commit 459981ef)
-
Martin Abente Lahaye authored
Besides building custom fedora images, we will build system extensions for GNOME OS. Since GNOME OS uses a a different libdir compared to what meson defaults to, we must allow setting libdir in this script. See https://discourse.gnome.org/t/towards-a-better-way-to-hack-and-test-your-system-components/21075 See https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/837 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3390> (cherry picked from commit dfafc972)
-
Martin Abente Lahaye authored
To build a system extension we need to: 1. Add dependencies to the container (to build it), and also 2. Add dependencies to the extension (to run it, later). So there's effectively two locations where we need to install those dependencies. See https://discourse.gnome.org/t/towards-a-better-way-to-hack-and-test-your-system-components/21075 See https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/837 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3390> (cherry picked from commit 2e5c3aec)
-
Florian Müllner authored
The eslint job occasionally fails because node hits an illegal-instruction error. There's a chance that a package update fixed that issue in the meantime, so rebuild the image. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3415> (cherry picked from commit 6dc07b41)
-
Will Thompson authored
In commit e69da360, Florian Müllner wrote: > We currently complete the animation using an onComplete handler, > which only runs if the corresponding transition was stopped when > finished. > > While it is unexpected that the transition is interrupted, it can > apparently happen under some circumstances (like VMs with qlx). > The consequences of that are pretty bad, mainly due to the cover > pane that prevents input during the animation not getting removed. > > Address this by always completing the animation when the transition > is stopped, regardless of whether it completed or not. There are effectively four branches of the startup animation: 1. if Meta.is_restart() is true, no animation is run on startup; I believe this is the X11-only case of restarting the shell mid-session. 2. if Main.sessionMode.isGreeter is true, just the panel is eased onto the screen; this is the GDM case. 3. if Main.sessionMode.hasOverview is true, then a whole sequence of animations are run; this is the normal session case. 4. otherwise, the whole UI zooms in to full size, and from full transparency to full opacity; this is the Initial Setup case. The fix above handles cases 2 and 4, but not 3. This patch applies the same fix to case 3, so that the callback is always called on session startup even if the transition is interrupted. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3422> (cherry picked from commit 93b33cf3)
-
sorelz authored
It wasn't possible to navigate by keyboard inside app folders due to the focus being grabbed by the dialog. Changed vfunc_key_press_event() to use the focus manager's navigate_from_event(), which is the same method used by modal dialogs (also making use of the focus group already assigned to AppFolderDialog). Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6331 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3338> (cherry picked from commit 30615896)
-
sorelz authored
The AppFolderDialog would lose keyboard focus after editing the title (likely due to the folder entry grabbing key focus). This commit adds navigate_focus() to _showFolderLabel() to send key focus back to the dialog's elements after editing the title. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3338> (cherry picked from commit a04b35b5)
-
sorelz authored
When an app folder is opened it would do so without grabbing the keyboard focus, so one could not navigate with the arrow keys without pressing Tab. This adds the focus parameter to popup()'s grab, which sets the key focus to the elements of the folder when it is opened. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3338> (cherry picked from commit 9569239e)
-
Will Thompson authored
During session startup, we have the following chain: LayoutManager._prepareStartupAnimation() `- LayoutManager._startupAnimation() `- LayoutManager._startupAnimationComplete() (a) | or `- LayoutManager._startupAnimationGreeter() (b) | or `- LayoutManager._startupAnimationSession() (c) `- Overview.runStartupAnimation() (d) `- OverviewActor.runStartupAnimation() (e) `- ControlsManager.runStartupAnimation() (f) Branch (b) calls LayoutManager._startupAnimationComplete() once the animation is complete. Branch (c) does the same, except that ControlsManager.runStartupAnimation() is an async function that awaits LayoutManager.ensureAllocation(). LayoutManager._prepareStartupAnimation() is an `async` function, and its caller catches & logs any error it raises. Previously, ControlsManager.runStartupAnimation() – (f) in the above diagram – was declared `async`, because it uses `await` internally, but also accepted a callback, which was called on successful completion of the function and the animation it triggers. If an exception is raised during execution of the function, its callback would never be called, and because the promise it implicitly returns is discarded, the exception would never be logged either. And, stepping a few levels up the call stack, the callback that LayoutManager._startupAnimationSession() (c) provided would never be called, and so LayoutManager._startupAnimationComplete() would never be called, meaning the cover pane that prevents input would never be removed and the session would be unusable. Remove the callback parameter from ControlsManager.runStartupAnimation() (f), and instead make it resolve in the case where the callback would previously have been called. Remove the callback parameter from OverviewActor.runStartupAnimation() (e) – it is just a wrapper around ControlsManager.runStartupAnimation(). Adjust Overview.runStartupAnimation() (d) accordingly: rather than passing a callback to OverviewActor.runStartupAnimation(), await its return and then proceed. There is a slight behaviour change here: previously, in the branch where this._syncGrab() is false, the callback would be called before calling this.hide(), whereas now this.hide() is called before the async function returns. Adjust LayoutManager._startupAnimationSession() and its siblings to be async, rather than each calling _startupAnimationComplete() directly. Finally, in _prepareStartupAnimation() await _startupAnimation() either succeeding or failing, and in either case call _startupAnimationComplete(), removing the cover pane that prevents all input. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3428> (cherry picked from commit 3d061345) -
Tuomas Nurmi authored
Use the right variable. A static WirelessNetwork._securityTypes variable does exist, but the correct variable when checking autoconnect possibility is this._securityType; this._securityTypes is undefined, causing clicking an enterprise network name in panel network selector do nothing instead of properly opening GNOME Settings panel. Closes https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7698 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3426> (cherry picked from commit a21558d6)
-
Florian Müllner authored
In the early days of shell development, someone accidentally pushed their eclipse configuration. Most of it was removed at one point, but one file was missed. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3432> (cherry picked from commit 949af345)
-
Florian Müllner authored
Update NEWS.
-
Jeremy Bícha authored
.settings/.jsdtscope
deleted
100644 → 0
