silverwind

I won't, had too many bad experiences with opening issues at eslint because they always refuse any behaviour changes in their rules. At this point, I think it's better to...

Would make it a generic `no-instanceof` with default config like `["Array", "Function"]`.

Some overridable CSS variables for the colors would be a start. I imagine this would cover most people's themeing needs.

I recently did styling for this module and I needed to do a few more changes besides colors like removing the border and the opinionated font changes. So at least...

If we validate for the specced [Date Time String Format](https://tc39.es/ecma262/multipage/numbers-and-dates.html#sec-date-time-string-format), which every JS engine is guaranteed to support, it would be ideal. It should be a pretty trivial regex.

As for errors, I would prefer something that can be caught in [window.onerror](https://developer.mozilla.org/en-US/docs/Web/API/Window/error_event), console logging is easier to miss, but it might serve as a start to help people migrate...

FWIW, I avoid private fields in all my code because of [this](https://lea.verou.me/blog/2023/04/private-fields-considered-harmful/). Not sure if it's really relevant to this element or whether consumers would install Proxies on it.

> make everything public I prefer all-public fields because they enable advanced use cases that the original author has not considered. For example, there are numerous cases in Node.js API...

Okay. I'm not suggesting changing these private fields now, but for new code, I would definitely consider using them and if there's no strong reason, I wouldn't, so that I...

One particular use of non-`title` tooltips is that they can allow the interactive selection of the value, which I find useful for referencing a date. Hover the time element, move...