Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MATE: Text caret navigation not visible when renaming files/folders on Desktop with dark themes #3537

Closed
flexiondotorg opened this issue Mar 23, 2022 · 1 comment · Fixed by #3544
Assignees

Comments

@flexiondotorg
Copy link
Contributor

flexiondotorg commented Mar 23, 2022

Expected Behavior

The text caret navigation should be visible when renaming files/folders on the Desktop using a dark Yaru theme.

Actual Behavior

The text caret navigation is not visible while renaming files/folders on the Desktop using a dark Yaru theme.

Steps to Reproduce the Problem

  • Download the Ubuntu MATE 22.04 daily-live image.
  • Run from USB or in a VM
sudo apt-add-repository ppa:flexiondotorg/quickemu
sudo apt-get -y update
sudo apt-get -y install quickemu
quickget ubuntu-mate daily-live
quickemu ubuntu-mate --vm ubuntu-mate-daily-live.conf
  • Use the Appearance control center applet to change the theme to Yaru-MATE-Dark
  • From the desktop session, right-click on the desktop to Create Folder
  • Right-click on the folder you created and select Rename

Software that presents the issue

  • Name: Caja
  • Version: 1.26
  • OS version: Ubuntu MATE 22.04 daily-live

Yaru version

  • 22.04.2-49-gf23d33752

Aditional information

Previously problem was solved for Caja in issues:

Screenshots

Yaru-MATE-dark without text caret navigation

image

Yaru-MATE-light with text caret navigation

image

@Jupi007 Jupi007 self-assigned this Mar 23, 2022
@Jupi007
Copy link
Member

Jupi007 commented Mar 23, 2022

I found the problem, I'll send a patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants