Ok I love JavaScript but this is enough.
I know selectors like these shouldn't exist, but double escaping? Hell no! I didn't even know it was a thing! I wonder what's the highest level of n escaping there is out there.

So this is what happens when you tell a back end dev CSS works with classes.

Multiple escape levels aren't a novel thing introduced by JS. I hate to say it but that's not the fault JS

Arent those xpaths?

Not only did you group css IDs with prefixes
Not only did you use the wrong character twice, despite the fact that dashes are recommended, thus breaking an unenforced rule of the platform (which doesn't make it any less of a rule).
But you have used the shitshows separator.
Paths are separated with /. Period. Just because some idiotic buggy os decided to break the standard, that doesn't make it any different.

Imagine jsons within jsons within jsons and you’ll have fun decoding

@010001111 ahha, some dudes even manage to put and encode JSON in highly relational databases, real life story with Enovia, smh