No spec for webextension manifest parsing?

[dmurph]

e.g. how do we parse the icon sizes, do we just see if the integer parses and if so, expect a path? etc.

[dmurph]

(discussed here: https://docs.google.com/document/d/1DdU_3NhxOsEnzRUjxUrGqxaGgcom3s9jF5nYhtkG26E/edit?tab=t.0#bookmark=id.y5z5swmm78i0)

[carlosjeurissen]

@dmurph

Closing in favour of the description of the algorithm here:
w3c/manifest#975 (comment)

And:

webextensions/proposals/dark_mode_extension_icons.md

Lines 198 to 212 in 4ea25cb

	**Matching**
	1. If `icon_variants` contains an icon group with matching conditions, the icon
	(s) specified in the first matching icon group based on insertion order will be
	used. The other icon groups after that match will be ignored.
	1. If there is more than one matching icon object, any without `color_schemes`
	will be applied to every possible color scheme. Therefore, a subsequent matching
	icon object with a `color_schemes` will not be used.
	1. Incorrectly typed `color_schemes` values will be ignored, with an optional
	warning. For example, `color_schemes: ["unknown"]` will be treated as an empty
	array. An empty array means the browser should mark the icon group as invalid
	and ignore it.
	1. If only one icon object is defined with a specific color scheme, that icon
	object will be applied to all color schemes.
	1. **Fuzzy matching** Inexact size matches will return the icon closest in size,
	starting with smaller sizes if available, retreating to the nearest larger size.

And sizes algorithm described here:

webextensions/proposals/dark_mode_extension_icons.md

Lines 214 to 230 in 4ea25cb

	**Size**
	1. The `"16"` is a size in `{"16": "icon.png"}` and any number can be used as a
	size, per the browser’s icon requirements. The word `"any"` can also be used in
	place of a number to represent an icon that can be shown at any size (usually
	vector images). The icon size used by the browser will be determined as follows:
	1. **Raster images**: Sizes are in pixels. For high-density devices (2x, 3x,
	etc.), the browser looks for double or triple the desired point size (e.g., 32
	or 48 pixels for a 16 point request). If the exact pixel size is unavailable,
	the next largest pixel size or `"any"` will be used.
	1. **Vector images**: Sizes are in points, ensuring device independence. If the
	exact point size is unavailable, an integer multiple (e.g. 32, 48, etc.) or
	`"any"` will be used.
	1. If none of the specified icon groups have matching criteria, browsers should
	drop matching criteria in a specified order until it finds a group which results
	in a match. It will start by dropping any matching criteria which are
	unsupported/unknown. If still no match could be made, it will drop known
	matching criteria in a future agreed upon order.