Repository navigation
Roadmap #219
Description
Activity
- pinned this issue
on Dec 9, 2025 @ArthurHub Pinging you here, since I don't know if you're monitoring that one Gmail account 😄
What I need your help with:
- Access to the HtmlRenderer.* nuget.org NuGet packages
- My profile: https://www.nuget.org/profiles/eXpl0it3r
- Replace the repository URL from the dead CodePlex page to the archive page
- If I have access to the HtmlRenderer.Mono package, I can deprecate it myself, otherwise you may need to do it
- Access to the HtmlRenderer.* nuget.org NuGet packages
Definitely better on GitHub :)
added you to all NuGet packages and updated the URL
thanks for reviving this project!Reacted by Lukas Dürrenbergerhey @eXpl0it3r I'd be happy to make a PR to pull in some of the stuff we've been doing out in fork land. We added some more skia features and have made a bunch of other small fixes as well, but having this finally come back to the mother branch would be great :)
Reacted by Lukas Dürrenberger@mstancombe That would be awesome! I've spent some time in fork land, but it's vast and lots of abandoned work. As such, it would be awesome if someone could condense some of the changes and PR them. ❤️
I started creating PRs to bring this project up to parity with PeachPDF -- which has 10 years of HTML5 + CSS3/4 features implemented, and gets new features all the time. There are going to be some gaps since PeachPDF focuses entirely on print rendering, and it uses a private fork of PdfSharpCore which allows me to improve the PDF output directly where PdfSharp falls short, but for where I can, I'll gladly bring the improvements over.
The current roadmap will be:
- HTML 5 parsing via HtmlKit
- CSS parsing via bringing in the fork of ExCSS
- Layout and painting engine improvements building on top of those
Reacted by Lukas Dürrenberger and tecAmoRaller
Taking over maintenance work for now, here's a rough roadmap I want to follow.
Join the discussion of you have any ideas / wishes.
Phase 1 ✅
Phase 2 ✅
Phase 3 ✅
Phase 4
Future