mirror of
https://github.com/atom/atom.git
synced 2026-02-05 04:05:05 -05:00
81145eb35f
When translating a logical screen position (columns/rows) to a pixel position, the editor now builds a temporary version of the line for the given row. It then uses the DOM range API to insert an empty range at the correct text node and offset for the given column and determines the left position based on its clientRect. Depending on the speed impact, we may want to optimize this by recycling the existing line node if it exists on screen rather than building a new one every time. We will still have to build one if the line we're moving to isn't on screen yet. We could also increase the chances of the line being on screen by autoscrolling to the vertical position first, and *then* calculating the horizontal position. Lots to explore here.