vectorBase: a value of the wrong kind is the property's default

A colour the canvas cannot read, a keyword its property does not take, or
a number given as a string was handed to the canvas, which ignored it and
drew the last feature's style. Colours now go through parseColor (which
now knows every CSS colour name), keywords are checked against their
property's values, and only finite numbers are numbers; anything else is
the property's default, as MapLibre coerces it. The style's background is
read the same way, so a value it cannot use is black at opacity 1 rather
than no background.
This commit is contained in:
Sameh Khamis committed 2026-11-11 20:22:44 -08:00
1 parent 727a6a2f5e
commit ba0fad3c35
5 files changed
+192 -67

No files matched your search

+4 -2
View File
@@ -347,8 +347,10 @@ What it draws of the style specification:
`line-gradient` or a translation; layers whose values use an expression
not listed (or are malformed). As MapLibre does, a paint or layout value
that cannot be evaluated for a feature (a type that does not fit, a
`step` or `interpolate` over what is not a number) or comes to nothing
(null, or not a finite number where one is needed) is the property's
`step` or `interpolate` over what is not a number) or is not of the
property's kind (null; not a finite number, a string included, where a
number is needed; not a colour `parseColor` reads, which takes the CSS
colour names; not one of the property's keywords) is the property's
default; a legacy function's miss is its `default`, else the property's.
A feature whose filter cannot be evaluated is left out. Nothing
unsupported throws.