Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generated HTML should be valid XML (XHTML) #10187

Closed
wants to merge 1 commit into from

Conversation

icnocop
Copy link
Contributor

@icnocop icnocop commented Sep 4, 2024

No description provided.

@icnocop icnocop marked this pull request as draft September 5, 2024 19:02
@icnocop icnocop changed the title Fixed typo to make toc.html.primary.tmpl valid xhtml Generated HTML should be valid XML (XHTML) Sep 5, 2024
@icnocop icnocop closed this Sep 5, 2024
@icnocop icnocop reopened this Sep 5, 2024
@icnocop icnocop marked this pull request as ready for review September 5, 2024 23:59
@icnocop icnocop marked this pull request as draft September 6, 2024 01:01
@filzrev
Copy link
Contributor

filzrev commented Sep 6, 2024

Currently docfx output HTML files that based on HTML Living Standard(HTML5)
So I thought default HTMLPostProcessor behaviors should not be changed with following reasons.


What's about adding custom XHtmlPostProcessor and specify custom postprocessor with docfx.json?

"build": { 
  "postProcessors": ["XHtmlPostProcessor"]
}

@icnocop
Copy link
Contributor Author

icnocop commented Sep 6, 2024

Thank you @filzrev !
It worked and added the code for the solution to #10191

@icnocop icnocop closed this Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants