Alaric.Baraou

> So that I understand it fully, can you explain why the two separate overlays (full text vs. selected range) are required? I would have assumed that you could use...

@lojjic sorry for delay I think I made something that kind of works as intended at least for the basic features. I still have to turn the "TextHighlighter" to a...

Sorry last couple of days happened to be quite busy. I made a few changes but I'm starting to feel a bit lost between the current vision and what I...

> I'd like to get this finished off and merged/released soon, and I'm willing to take over at any point for the finishing touches, but I won't step on your...

Starting now, I'll update this as I progress - [x] is tested and works as I would expect it - [ ] is implemented but don't work or not tested...

@lojjic Everything is fine for me feature wide. Let me know if you need some infos on some code or anything.

@lojjic Sorry it looks like there was one conflict remaining.. I thought I already resolved all of them. It's resolved now, sorry for the delay.

Personally I don't have enough time to dive into Troika in the near future and couldn't commit to maintain the feature. If I remember correctly "my part" is working but...

I'm not sure I understand this one. I understand it can prevent a NaN but why would it remain stuck at [0,0] if the first one fail ?

Sorry I just saw your comment. The position is part of the accessibility feature. The focus outline needs to be positioned correctly in the page to know what you're currently...