Absolutely. So no thank you, I won't stop writing CSS like it's 2015 if those features aren't at least supported by all latest browsers.

The arts look a lot like Ankama work https://www.ankama.com

Yeah, that's a valid point though some text on a page can easily be made unselectable via css (html?). I think through user-select

Or just toggle off the timestamps before clipping.

That's no excuse imho. I see 2 different endpoints, 1 for llm stream and 1 for msg history (with stamps). New timestamps could be added FE as new messages start without polluting the user input for example

How many years experience do you have managing products with millions of users?

Could try the hacky 2147483647 max z-index. No issue on android firefox

Checked it out out of curiosity and it feels very much close to native

Yep, I believe you'd need to call Object.seal(foo) to prevent mutability. Haven't really had the chance to use it

Object.freeze is the one you're looking for.

const + Object.freeze is a lot to remember and cumbersome to use throughout a codebase, very relevant to Carmack's wish for immutability by default. I'm grateful Rust opted for that default.

This hit me harder than I thought it would.

A fair few will also just reset all css to avoid having to deal with different browsers opinionated stylings.

Made me laugh, “what the? No way, what if.. eh!? And maybe..” crash