3 ms·
Now I remember the main problem before switching to the render three was text rows. there is no good way of knowing where a text line will break without resorti
by callesgg 9y ago
Now I remember the main problem before switching to the render three was text rows. there is no good way of knowing where a text line will break without resorting to the render tree or to use some form of ocr.
- tombh 9y agoAh yes, that was a big hurdle, but that's actually fully supported now with DOM Ranges - basically codified selection boxes, those regions that highlight when you select with a mouse. There's still some extra leg work though to render whitespace in the same way as the browser.
- callesgg 9y agoI did that to if you are referring to getBoundingClientRect & getClientRects, before I switched over to the render tree. It does work perfecly for single line text but not multi line text. The rect will become larger than the text and you won't know where each line starts. Well that is what I remember happening.
- deleted 9y ago[deleted]
- tombh 9y agoOh! Sorry I just assumed they weren't around then. That's really interesting to know. Hey could I have a chat with somewhere, IM, or something? Would be really good to hear your story with this.