although I wonder if it should at least log these to let the developer know
Preact internals #3: some fiddly little bits
Adam Solove

That seems like a good idea. There’s a PR in to circumvent this in a nice and debuggable way though: for Strings (which tend to be the offending values here), we’d always set the value via `setAttribute()`, so erroneous values are displayed as attributes in Web Inspector like they would be if set manually.

Like what you read? Give Jason Miller a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.