In our application we use a background worker to generate html that then is processed by chromium to print as pdf.
When looking at the code for the the tag helpers, all use the #path_to_asset to generate the url containing the proper digest etc. But the options passed to the method differ depending on the helper. Stylesheet and javscript honour the protocol and host options, whereas for images only skip_pipeline is used.
This required us to implement custom logic for #image_tag and #resolve_image_source.
We would like to extend/homogenize all tag and link helper methods to consistently support the path options host and protocol.