(In reply to Emilio Cobos Álvarez (:emilio) from comment #6) > So, Chromium has a bunch of XPS-specific code dealing with [these Win32 APIs](https://docs.microsoft.com/en-us/windows/win32/api/prntvpt/). > > It still seems like what we do should be enough though, so this really needs more investigation. emilio, can you elaborate a bit more about this? (What **do** we do here, i.e. where should/would someone start poking to see what's going wrong?)
Bug 1674081 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #6) > So, Chromium has a bunch of XPS-specific code dealing with [these Win32 APIs](https://docs.microsoft.com/en-us/windows/win32/api/prntvpt/). > > It still seems like what we do should be enough though, so this really needs more investigation. emilio, can you elaborate a bit more about this? (What **do** we do here, i.e. where should/would someone start poking to see what's going wrong?) (in particular: I'm confused since in comment 4 it sounded like throwing up our hands might be all we could do, vs. in comment 6 it sounds like we have code that's supposed to already handle this in some way or another. :))