I mean finding the top/left pixel position of the cursor, rather than the character offset.
The reason I want to do this is because I want to show a small tooltip-like div next to the cursor (think of the newer MS Word's floating formatting box) that follows the cursor as you type or click. I can use the mouse coordinates if the user clicks, but not sure how to do this for typing.
Is there a reliable way? If not for finding the top/left position of the cursor, then the alternative is to just find the top position for the line.
Sample code isn't 100% necessary, as long as the method works and is well-explained.
Javascript - Caret Position The mouse moves the cursor. Text fields use a caret to indicate where text is inserted. Left clicking the mouse typically sets the caret location.
try this
var cursorY = window.getSelection().getRangeAt(0).getBoundingClientRect().top;
cursorY is the cursor Y position in window.
A Selection object represents the range of text selected by the user or the current position of the caret.
Selection.getRangeAt() return a range object representing one of the ranges currently selected.
This not really an answer but concepts to think about:
In contenteditable, everything consists of nodes just like anything else HTML, so you can get the node's position, the problem is where in the node you are (if it's text, you might be 100 characters inside the node). So you have to make your own single character nodes.
To get the position as someone types, you'd have to capture the onkeypress event, stop the propagation bubble, take the character they are asking for, stuff it in a node (maybe a span ala a "marker") and then insert that node. Then you'd calculate the exact position of that span/node by it's offsets.
You'll probably have to remove the span and replace it with just the character afterwards.
There is also the problem I've encountered where if you mess with the bubble events when scrolling is supposed to happen, the caret may go outside the viewport.
Optionally, and this might be a slightly better idea, instead of messing with the propagation, allow the browser to insert the character on it's own, then immediately insert a zero-width unicode character (invisible) in a span/node before or afterwards, and calculate it's position instead. Then yank out the markers either on the fly or when they pause typing.
Yup, it's that messy, sorry. If someone has a better way, I am all ears.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With