This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
Go To Definition / F12 from Razor class attribute to CSS class definition no longer works in Visual Studio 18.5.1. CSS IntelliSense works, full text search finds the CSS definition, F12 works for C#, but CSS class navigation from Razor/HTML does nothing. Reproducible in a new Blazor Web App with a simple <div class="rm-test-f12"> and app.css definition.
Original Comments
Feedback Bot on 03/05/2026, 08:43 PM:
Based on similar issues resolved with Microsoft in the last 6 months, the following can help resolve this issue faster.
Possible workarounds
Try updating to the latest Visual Studio build and re-test the Razor/HTML Go To Definition (F12) behavior. Since the issue is reproducible in a new Blazor Web App, also try deleting the solution’s .vs folder and reopening the project, then test again.
If not already included, please provide:
Detected: OS: 10.0.26200.0, VS: 18.5.2 (18.5.11723.231), Project type: C# / Blazor Web App
Please share a few more specifics so we can investigate:
- Does the issue reproduce in every new Blazor Web App, or only in this one solution?
- What exact file are you invoking F12 from, and is the
class value in a Razor file or plain HTML file?
- Is the CSS definition in
app.css, and is the CSS file definitely included/open in the same solution?
- Does Ctrl+click / Go To Definition behave the same way as F12?
- Did this work in a previous VS version or does it fail immediately after opening VS 18.5.2?
Dirk-Matthias Metzger on 03/05/2026, 08:46 PM:
(private comment, text removed)
Feedback Bot on 04/05/2026, 00:24 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
Go To Definition / F12 from Razor class attribute to CSS class definition no longer works in Visual Studio 18.5.1. CSS IntelliSense works, full text search finds the CSS definition, F12 works for C#, but CSS class navigation from Razor/HTML does nothing. Reproducible in a new Blazor Web App with a simple <div class="rm-test-f12"> and app.css definition.
Original Comments
Feedback Bot on 03/05/2026, 08:43 PM:
Based on similar issues resolved with Microsoft in the last 6 months, the following can help resolve this issue faster.
Possible workarounds
Try updating to the latest Visual Studio build and re-test the Razor/HTML Go To Definition (F12) behavior. Since the issue is reproducible in a new Blazor Web App, also try deleting the solution’s
.vsfolder and reopening the project, then test again.If not already included, please provide:
Detected: OS: 10.0.26200.0, VS: 18.5.2 (18.5.11723.231), Project type: C# / Blazor Web App
Please share a few more specifics so we can investigate:
classvalue in a Razor file or plain HTML file?app.css, and is the CSS file definitely included/open in the same solution?Dirk-Matthias Metzger on 03/05/2026, 08:46 PM:
(private comment, text removed)
Feedback Bot on 04/05/2026, 00:24 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.