MicrosoftEdge / MicrosoftEdge/WebView2Feedback

CSS - cursor loaded from URL doesn't work.

Open
#1,925 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Version
Runtime: 95.0.1020.44
Framework: WinUI3 / .NET MAUI Blazor (webview2)
OS: Win10

Repro Steps

  • Create a basic WinUI3 app with a WebView2 browser component.
  • Create an html string with a style section and one element that has a class name defined in that style section.
  • In the style for that class, set the cursor to some url that loads a 32x32 pixel png image in BASE64 format.
  • run the application.

Expected Result
When hovering over the html element, the cursor should change into the one defined in the style section.

Actual Result
The default cursor is used when hovering over the html element.

Extra Information
In a .net maui blazor (webview2) context, I experienced this issue too, and there I use a style sheet that loads the url from a file with the same result.

In both contexts it is possible to load and show the image as a background;

A blazor webassembly application that uses the same code (including style sheets) behaves as expected.

AB#29849024

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported CSS cursor URL behavior in a basic WinUI3 app with a WebView2 browser component, using the 32x32 base64 PNG and the file-based stylesheet variant. Compare cursor loading with the working background-image case and the WebAssembly result. Done means the cursor changes to the image when hovering over the styled element.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.