Emilio Cobos Álvarez (:emilio) Reporter
	Description • 7 years ago

The docs of this property say that only relevant values are zero and one.

Gecko accepts all integers as valid, yet it later computes it in a weird way (mod 256, basically).

For example, in Gecko:

 -moz-force-broken-image-icon: 23;

is both valid and computes to 23. Yet:

 -moz-force-broken-image-icon: 256;

is valid, too, but computes to _zero_.


We're going to implement it in a way that values other than zero or one are rejected at parse time. We think this is fine, because it's an internal property and the rest of values are not either documented nor tested (and behave just as "1").

We could reconsider that if needed, but the behavior is so bizarre that I'd prefer not having to.

	Anthony Ramine [:nox]
	Comment 1 • 7 years ago

Maybe we could consider unshipping the weird modulo thing and allowing values different from 0 and 1 from Gecko before 57?

	Chris Peterson [:cpeterson]
	Comment 2 • 7 years ago

status-firefox57=wontfix unless someone thinks this bug should block 57