I'd also like to add that setting page color has been a normal feature of Microsoft Word since at least Office 95. Market penetration of the feature is 100% and all DOCX files can be expected to set page color.

The workaround is not a complete workaround because it assumes the application knows what the document file's page color is. Otherwise, the file has to be loaded twice: once to populate the document object, and once to expand the DOCX and parse the XML to manually find the page color. This is very inefficient for large files. I would have to do the same for HTML files and parse the HTML syntax a second time to know what the page color should be.

Also, the workaround only applies to reading files. I use Telerik’s library to write DOCX files too. The workaround would suggest I have to write the DOCX once, then read it back, then write it a second time with the page color.

Is this a complicated feature on your side? I considered implementing this myself and offering it as a pull request, but I wouldn't even know where to begin, and it seems overwhelming for me to learn that area of the library code within the time I can commit. In the meantime, I am unable to read dark-themed documents created by Microsoft Word users, or to create dark-themed documents that they can read.