You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all resources will be individually converted to data: URIs. In one case, a single image of 1.8 MB was referred to 166 times from the HTML file. This led to an out of memory error. Even if it succeeded, it is not advisable to create a 400 MB HTML report.
One solution might be to attach a class to each image that is derived from its @src. Then you can include a CSS chunk with the data: URIs, only a single data: URI per @src, even if the image is referred to repeatedly.
Currently, all resources will be individually converted to data: URIs. In one case, a single image of 1.8 MB was referred to 166 times from the HTML file. This led to an out of memory error. Even if it succeeded, it is not advisable to create a 400 MB HTML report.
One solution might be to attach a class to each image that is derived from its
@src
. Then you can include a CSS chunk with the data: URIs, only a single data: URI per@src
, even if the image is referred to repeatedly.This is inspired by http://stackoverflow.com/questions/28832129/replace-image-src-location-using-css#answer-28832261
Apparently, though, Firefox does not support
content:
for images, onlybackground:
.Image scaling will also be important. We’ll deal with it in another issue.
The text was updated successfully, but these errors were encountered: