fix #95: error 'Could not compute content quads'

[alexanderadam]

Hi @route,

sorry that it took so long. 😞

So the thing is: in theory DOM.getContentQuads is absolutely the right thing to do. But depending on the used browser, this seem to be unstable, though (and I'm sure it will change in the future).

Thus, if we're running into this unstable state (and only then!) we're going to calculate the position via JS instead.
This might be slower, but at least it's working flawlessly. And hopefully getContentQuads will become more stable and we won't run into this anymore anyway.

I hope it's working for you and others. At least it's working in the projects of my clients.

PS: We should definitely get rid of all the sleeps in the specs and migrate to a more stable solution. Maybe this would be related to #81 / #82 (I still don't know why you created another issue for this). 😉

[route]

Thank you

[alexanderadam]

I have to thank you buddy. 🙌
Thank you so much for the RubyCDP projects. I wish @crystal-lang would have libraries like these.

[route]

Haha maybe some day :)