6 Commits

Author	SHA1	Message	Date
Pale Moon	2bccdcbcc0	Make the SVG scaling limit for the surface cache more lenient. ... Increase the limit to a royal 32MB/element as cap (if the SVG is square). This still avoids performance regressions when scaling large vector images, but also allows for large SVG backgrounds to be cached. We'll have some performance loss here on e.g. the Chalkboard test (1-2 seconds) because of increased cache management, but it's still considerably faster and smoother than Firefox. At the same time 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 2850 px in the largest dimension. This resolves #1446, because the largest dimension in use there falls within the new bounds.	2018-07-25 09:28:40 +08:00
janekptacijarabaci	a839da1f08	Fix build bustage when compiler warnings as errors (int32_t/uint32_t)	2018-07-25 07:58:39 +08:00
janekptacijarabaci	1613731be0	Fix build bustage when compiler warnings as errors	2018-07-25 07:58:25 +08:00
Pale Moon	19738af3c0	Reinstate some caching for vector images with small enough dimensions. ... A dimension of 400 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. Final solution for #757.	2018-07-25 07:45:24 +08:00
Pale Moon	5b6de5f6cd	Bypass surface cache for vector images; always draw them as-is. ... This fully fixes the regression in #757.	2018-07-25 07:45:17 +08:00
Moonchild	baf46a6bf1	Merge pull request #1 from mozilla/esr38: Esr38 upstream pull	2018-07-24 23:04:07 +08:00