Which version of WebSharper (3.6 or 4.0) are you using, and which templating system (WebSharper.Html or UI.Next)? I am failing to reproduce this issue on the current recommended WebSharper 4.0 with UI.Next.

By on 10/3/2017 9:12 AM ()

We're using WebSharper 3.6 with WebSharper.Ui.Next 3.6.

I'll try upgrading to 4.0 to see if that resolves the issue.

Thanks.

By on 10/3/2017 11:30 PM ()

I believe this is a bug, we should definitely keep the namespace. I'm sure we can retrieve it from HtmlAgilityPack's parser and pass it along.

I posted this in the issue tracker, will work on it ASAP.

By on 10/3/2017 4:38 AM ()