diff options
| author | wolfbeast <mcwerewolf@gmail.com> | 2017-06-28 21:49:03 +0200 |
|---|---|---|
| committer | wolfbeast <mcwerewolf@gmail.com> | 2018-02-04 00:07:05 +0100 |
| commit | feeb4327304db5af1c4aa7f77c082bb6527eef5b (patch) | |
| tree | 6df08048816d276b7463126180030854c42e9d49 /layout/reftests/pagination/content-inserted-003.xhtml | |
| parent | de11930c3fecac13bc06da4f8b7818178c63f20e (diff) | |
| download | UXP-feeb4327304db5af1c4aa7f77c082bb6527eef5b.tar UXP-feeb4327304db5af1c4aa7f77c082bb6527eef5b.tar.gz UXP-feeb4327304db5af1c4aa7f77c082bb6527eef5b.tar.lz UXP-feeb4327304db5af1c4aa7f77c082bb6527eef5b.tar.xz UXP-feeb4327304db5af1c4aa7f77c082bb6527eef5b.zip | |
Don't cache vector images in the surface cache if they are too large.
A dimension of 3000 largest size x or y should cover all common caching cases for SVG icons and web app elements, but not caching large vector rasters that would exhaust the cache.
This limit is a royal 36MB/element (3000x3000x4) as cap (if the SVG is square). This avoids performance regressions when repeatedly scaling large vector images, but also allows for large SVG backgrounds to be cached.
It allows for the bad practice of slapping a large SVG on a site as html background, considering they are likely, even when using large sizes for "responsive" layout, not going to exceed 3000 px in the largest dimension (and if they do, the web designer needs to be slapped with a big trout).
Diffstat (limited to 'layout/reftests/pagination/content-inserted-003.xhtml')
0 files changed, 0 insertions, 0 deletions