Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Editor error when Frame is nested inside Frame

See original GitHub issue

That seems like a tooling error, but I’m not sure where would be better to log it.

Editor is not able to match start/end tags for Frame element when one Frame is nested inside another Frame. That breaks syntax highlighting and auto-format is broken.

Example:

<ContentPage>
    <Frame>
        <StackLayout>
            <Frame></Frame>
        </StackLayout>
    </Frame>
</ContentPage>

AtUhZ4rq3r

Issue Analytics

State:
Created 3 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

Eiloncommented, Nov 2, 2020

I logged a bug in the ASP.NET Core repo for Razor Tooling because this repros outside of a Mobile Blazor Bindings project: https://github.com/dotnet/aspnetcore/issues/27450

I’m closing this issue because there’s presumably no action needed here.

Thank you for the bug report, this one was a weird one!

1reaction

Eiloncommented, Nov 2, 2020

I feel like maybe Frame is conflicting with some other kind of Blazor thing. If you use the full type name there’s no warning:

<Microsoft.MobileBlazorBindings.Elements.Frame BorderColor="Color.Orange">
    <Microsoft.MobileBlazorBindings.Elements.Frame BorderColor="Color.Red">
    </Microsoft.MobileBlazorBindings.Elements.Frame>
</Microsoft.MobileBlazorBindings.Elements.Frame>

And other tags all seem fine. It seems like just this one <Frame> tag is not happy.