You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with the scroll offsets and the width of the line number padding, users of the library will be able to determine what parts of the textarea are rendered and where, enabling a host of extensions to be built on top of the textarea without needing to alter the underlying library at all. for example:
mouse event handling to move the cursor to a specific location by clicking
tooltips / overlays
inlay hints / suggestions
dropdown menus for things like auto-completion
i think you could even make syntax highlighting work with just these numbers
possible solution
one method to expose top_col / top_row from the viewport, and another method to expose the width of the line numbers
The text was updated successfully, but these errors were encountered:
reason
with the scroll offsets and the width of the line number padding, users of the library will be able to determine what parts of the textarea are rendered and where, enabling a host of extensions to be built on top of the textarea without needing to alter the underlying library at all. for example:
possible solution
one method to expose top_col / top_row from the viewport, and another method to expose the width of the line numbers
The text was updated successfully, but these errors were encountered: