🔍 hard to be visually identified on MuseScore website pages on black background as in Windows `Night sky` high contrast theme

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

Steps

1. Apply the Night sky theme in Windows (see #27393).
2. Visit MuseScore website.

Behaviour

• Actual: The search icon (the magnifying glass) cannot be visually identified. The user has to move the pointer near there untill the pointer style changes to link selection. To check and modify what that style looks like,
  • see Microsoft Support documentation or
  • enter the following command (see the Microsoft Learn documentation):

    control.exe /name Microsoft.Mouse /page 1
    

    
• Expected: The search icon should be able to be visually identified.

Supporting files, videos and screenshots

• 🔍 can hardly be visually identified in Night sky theme:
  
• It can be seen in a normal theme:
  

In which versions of MuseScore Studio is this issue present?

Not applicable

Regression

No.

Operating system

版本	Windows 11 家庭版
版本号	25H2
安装日期	‎2024/‎8/‎7
操作系统版本	26200.6899
体验	Windows 功能体验包 1000.26100.253.0

Additional context

You may find the contrast themes sometimes exiting in seconds after applied, especially in such a case in which your computer wakes up after sleeping for long. Do not worry. This is a [bug](feedback-hub:?contextid=941&feedbackid=07d66c7b-e427-4683-9bbf-28567f7fdb12&form=1&src=1) in Windows.

Closing per the comment above; I'll notify the .com team about it. (I do note that this affects MSStudio users as they are redirected to this login page when trying to log in in the app.)

Originally posted by @cbjeukendrup in #30666

I am sure this is a .org bug rather than a .com one.

This bug is originally reported on MuseScore website #378119.

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible