Enabling dash-to-dock messes up search results navigation #1612

yoursred · 2021-12-07T06:06:36Z

GNOME: 41.1
dash-to-dock: 71
Kernel: 5.14.21-2-MANJAR

Description: With dash-to-dock enabled, side-to-side navigation with the arrow keys is nonfunctional, and trying to navigate takes the search bar out of focus.

yoursred · 2021-12-07T06:12:04Z

Update: intelligent autohide seems to be cause

yoursred · 2021-12-07T06:13:21Z

Update: enabling it, regardless of its settings, seems to be the cause

3v1n0 · 2021-12-07T15:23:46Z

Please, explain exactly how to reproduce because it's not clear to me.

If it's about the fact that using arrow-keys while moving around the search text, moves the focus to the app icons, that's an upstream bug/feature as well.

yoursred · 2021-12-07T17:45:59Z

I guess it's a combination of gnome and the extension

.

JustCryen · 2021-12-10T17:51:09Z

I've been having the same issue for quite some time.
I just narrowed it down to Dash To Dock but nothing more.
For now I can confirm that either disabling the extension or Intelligent Autohide feature fixes it.
OS: archlinux
Gnome: gnome-shell 1:41.1-1

yoursred · 2021-12-10T18:55:59Z

I want to add another thing, it only happens with intelligent autohide when the dock is not extended and is on the left side of the screen.

JustCryen · 2021-12-10T20:13:48Z

You're right… sadly that's exactly how I use it.

yoursred · 2021-12-10T20:15:50Z

I would recommend extending it until a fix is found

JustCryen · 2021-12-10T20:18:48Z

Actually, under Appearance, disabling "Shrink the dash" makes it work again.
That's something I can tolerate, extending it is too distracting for me.

yoursred · 2021-12-10T20:27:39Z

Quite the bizarre bug

rollflick · 2021-12-20T09:35:12Z

The issue in Activities Overview only occurs for me after suspending, not after a reboot. Occurs whether using Wayland or Xorg (though maybe need to do reboot rather than just logging out, which I didn't do).

Turning off Ubuntu Dock in extensions seems to have sorted it for me. Never needed to do that before for this extension to work well.

yoursred · 2021-12-20T09:44:40Z

I can confirm that it happens regardless of session type (Xorg or Wayland), but for me at least, it doesn't care about being woke up or a cold boot.

JustCryen · 2021-12-20T09:50:30Z

Same as @yoursred.
For now I just have "Shrink the dash" disabled.
Ideally I would like to turn it back on.

sirianni · 2022-01-06T21:58:08Z

Same issue here. Note that strangely this only happens when the dock is placed on the left. If I place the dock on bottom or right side of the screen then keyboard navigation works properly.

muflone · 2022-03-13T13:08:17Z

Confirmed in GNOME 41.4 for Arch Linux

Disabling the dash reduce fixes the navigation

S0llarCode · 2022-06-14T16:18:05Z

Same in GNOME 42.2 with Wayland, Manjaro 21.2.6 (Arch Linux)
Dash to dock 72

Fixed when disabling "Intelligent autohide"

When "Intelligent autohide" is enabled and i try to navigate in my search, such as @yoursred #1612 (comment), messages like this appear.

journalctl -b 0 -e:

gnome-shell[944]: Timelines with detached actors are not supported. [<Gjs_ui_iconGrid_BaseIcon>:0x55ff47ec5d30] in animation of duration 100ms but not on stage.

S0llarCode · 2022-07-09T17:20:20Z

Additional bug report
GNOME 42.2 with Wayland, Manjaro 21.3.2 (Arch Linux)
Dash to dock 72

When "Intelligent autohide" is enabled and the maximum icon size number is odd (like 37px), then the same bug occurs. If the maximum icon size is changed to an even size (like 38px) then the bug disappears.

You can fix the bug by choosing a maximum icon size with a even number. Examples : 32px, 36px, 38px...

Fix idea..
Settings.ui

Change property step-increment by 2

  <object class="GtkAdjustment" id="icon_size_adjustment">
    <property name="lower">16</property>
    <property name="upper">128</property>
    <property name="step-increment">2</property>
    <property name="page-increment">10</property>
  </object>

vanvugt · 2022-09-12T11:03:05Z

Downstream Ubuntu bug: https://launchpad.net/bugs/1979096

siddhpant · 2022-09-12T14:34:27Z

On Sat, 9 Jul 2022 22:50 +0530 @S0llarCode wrote:

When "Intelligent autohide" is enabled and the maximum icon size number is odd (like 37px), then the same bug occurs. If the maximum icon size is changed to an even size (like 38px) then the bug disappears.

You can fix the bug by choosing a maximum icon size with a even number. Examples : 32px, 36px, 38px...

For me, the setting was already even. Changing it to an odd number works/fixes for me, i.e., restores the intended behaviour.

soumyaDghosh · 2022-09-13T18:15:39Z

Please, explain exactly how to reproduce because it's not clear to me.

If it's about the fact that using arrow-keys while moving around the search text, moves the focus to the app icons, that's an upstream bug/feature as well.

To reproduce this, in ubuntu specifically, install the gnome-4x-ui-improvements extension. Then logout and login. The overviews cannot be seen anymore. Disable the hide search bar option in the above said extension, things will work again.

3v1n0 · 2022-09-24T08:28:52Z

Wondering if commit 3431f5f has anything to do with this...

siddhpant · 2022-09-26T08:56:45Z

On Sat, 24 Sep 2022 at 13:58 +0530, @3v1n0 wrote:

Wondering if commit 3431f5f has anything to do with this...

I am still experiencing the bug after updating to v74 (i.e. even number icon size breaks the search), so the commit probably doesn't fully address the bug...

jabossu · 2022-10-04T06:09:28Z

Additional bug report GNOME 42.2 with Wayland, Manjaro 21.3.2 (Arch Linux) Dash to dock 72

When "Intelligent autohide" is enabled and the maximum icon size number is odd (like 37px), then the same bug occurs. If the maximum icon size is changed to an even size (like 38px) then the bug disappears.

You can fix the bug by choosing a maximum icon size with a even number. Examples : 32px, 36px, 38px...

Fix idea.. Settings.ui

I can confirm this solution worked for me.

Manjaro (up to date)
Dash-To-Dock v74
Other extensions enabled : Caffeine, Emoji Selector, GSConnect

For some reason we need to use an even value, this is probably due to the fact that such value is going to be proportional to the available space. Closes: micheleg#1612

For some reason we need to use an even value, this is probably due to the fact that such value is going to be proportional to the available space. Closes: micheleg#1612 LP: #1979096

3v1n0 · 2022-10-09T23:03:10Z

Please check if #1849 solves the issue.

For some reason we need to use an even value, this is probably due to the fact that such value is going to be proportional to the available space. Closes: micheleg#1612 LP: #1979096

For some reason we need to use an even value, this is probably due to the fact that such value is going to be proportional to the available space. Closes: #1612 LP: #1979096

We were allocating the ControlsManagerLayout using the whole work area geometry but then in the auto-hide mode we were reducing the size of the available area again, creating problems when the available space was reduced. Leading to non-clickable or activatable search results. To prevent this, perform layout allocation using the available space even when the dock is in autohide mode. Closes: micheleg#1612 LP: #1979096

3v1n0 · 2023-05-31T00:30:38Z

This does not seem to have really fixed in all the cases, but the good news is that it looks like I got a solution at #2020

We were allocating the ControlsManagerLayout using the whole work area geometry but then in the auto-hide mode we were reducing the size of the available area again, creating problems when the available space was reduced. Leading to non-clickable or activatable search results. To prevent this, perform layout allocation using the available space even when the dock is in autohide mode. Closes: #1612 LP: #1979096

We were allocating the ControlsManagerLayout using the whole work area geometry but then in the auto-hide mode we were reducing the size of the available area again, creating problems when the available space was reduced. Leading to non-clickable or activatable search results. To prevent this, perform layout allocation using the available space even when the dock is in autohide mode. Closes: micheleg#1612 LP: #1979096

vanvugt mentioned this issue Sep 12, 2022

Activities Not working when Dash to Dock 72 is enabled #1747

Closed

3v1n0 linked a pull request Oct 9, 2022 that will close this issue

Overview layout sizes fixes #1849

Merged

3v1n0 closed this as completed in #1849 Oct 13, 2022

3v1n0 reopened this May 31, 2023

3v1n0 mentioned this issue May 31, 2023

docking: Do ControlsManagerLayout allocation with box-adjusted workArea #2020

Merged

3v1n0 closed this as completed in #2020 Jun 2, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Enabling dash-to-dock messes up search results navigation #1612

Enabling dash-to-dock messes up search results navigation #1612

yoursred commented Dec 7, 2021

yoursred commented Dec 7, 2021

yoursred commented Dec 7, 2021

3v1n0 commented Dec 7, 2021

yoursred commented Dec 7, 2021

JustCryen commented Dec 10, 2021

yoursred commented Dec 10, 2021

JustCryen commented Dec 10, 2021

yoursred commented Dec 10, 2021

JustCryen commented Dec 10, 2021

yoursred commented Dec 10, 2021

rollflick commented Dec 20, 2021

yoursred commented Dec 20, 2021

JustCryen commented Dec 20, 2021

sirianni commented Jan 6, 2022

muflone commented Mar 13, 2022

S0llarCode commented Jun 14, 2022 •

edited

S0llarCode commented Jul 9, 2022 •

edited

vanvugt commented Sep 12, 2022

siddhpant commented Sep 12, 2022 •

edited

soumyaDghosh commented Sep 13, 2022 •

edited

3v1n0 commented Sep 24, 2022

siddhpant commented Sep 26, 2022 •

edited

jabossu commented Oct 4, 2022

3v1n0 commented Oct 9, 2022

3v1n0 commented May 31, 2023

Enabling dash-to-dock messes up search results navigation #1612

Enabling dash-to-dock messes up search results navigation #1612

Comments

yoursred commented Dec 7, 2021

yoursred commented Dec 7, 2021

yoursred commented Dec 7, 2021

3v1n0 commented Dec 7, 2021

yoursred commented Dec 7, 2021

JustCryen commented Dec 10, 2021

yoursred commented Dec 10, 2021

JustCryen commented Dec 10, 2021

yoursred commented Dec 10, 2021

JustCryen commented Dec 10, 2021

yoursred commented Dec 10, 2021

rollflick commented Dec 20, 2021

yoursred commented Dec 20, 2021

JustCryen commented Dec 20, 2021

sirianni commented Jan 6, 2022

muflone commented Mar 13, 2022

S0llarCode commented Jun 14, 2022 • edited

S0llarCode commented Jul 9, 2022 • edited

vanvugt commented Sep 12, 2022

siddhpant commented Sep 12, 2022 • edited

soumyaDghosh commented Sep 13, 2022 • edited

3v1n0 commented Sep 24, 2022

siddhpant commented Sep 26, 2022 • edited

jabossu commented Oct 4, 2022

3v1n0 commented Oct 9, 2022

3v1n0 commented May 31, 2023

S0llarCode commented Jun 14, 2022 •

edited

S0llarCode commented Jul 9, 2022 •

edited

siddhpant commented Sep 12, 2022 •

edited

soumyaDghosh commented Sep 13, 2022 •

edited

siddhpant commented Sep 26, 2022 •

edited