uxp - uxp [Local Fork]

	Commit message (Collapse)	Author	Age
*	Issue #21 - Remove use counters telemetry	FranklinDM	2022-04-24
\| \| \| \| \| \|	This reverts Bug 968923 - Implement some equivalent of Chrome's use counters (on top of telemetry?) For reference: https://bugzilla.mozilla.org/show_bug.cgi?id=968923
*	Issue #1619 - Convert Intrinsic Ratio to Float	Andy	2020-07-31
\| \| \| \| \| \| \| \| \|	https://bugzilla.mozilla.org/show_bug.cgi?id=1547792 Aspect Ratio handling simplified by using floating point integers: - Multiplication of value (or inverse value) to a known side for Scaling - No unequal equal values such as "4/3" vs "8/6" vs "20/15" - Truly "Empty" aspect ratios, even if one dimension is not 0
*	Telemetry: Remove stubs and related code	adeshkp	2019-01-12
\|
*	Make vector image surface caching smarter.	wolfbeast	2018-04-05
\| \| \| \|	This resolves #91.
*	Use int instead of uint for vector dimension cap.	wolfbeast	2018-02-04
\|
*	Don't cache vector images in the surface cache if they are too large.	wolfbeast	2018-02-04
\| \| \| \| \| \|	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).
*	Add m-esr52 at 52.6.0	Matt A. Tobin	2018-02-02