Skip to content

[Feature Request] Editor Canvas Padding #5386

Description

Context

  • This issue is not a bug report. (please use a different template for reporting a bug)
  • This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description

It looks to me that there's no support for padding the editor canvas effectively between the margin gutters and the scrollbar.

While it's possible to muck with the CSS and get left padding to apply, there's no right padding support and content is just shifted over to the right cutting off.

What I'm after is actual canvas padding support.

Currently the closes I can get to this is like this:

Image

but this is pretty ugly. Not quite as bad if there are no gutter items (line numbers or other gutter markers). Essentially what I'd like to see is a way to pad out between the gutter and the scrollbar to allow filling the container panel that might be much bigger but limit the size of the actual editor canvas to a certain width.

Here's a more extreme example where this is annoying using the diff editor where the padding could help spread out the gutter and scroll bars which are very wide into the host container:

Image

(and yeah I could just use the whole canvas but then the text gets annoyingly wide and harder to read)

In the editor depicted I can configure the max editor pixel width (ie. 920px) and if the container expands like in full screen view the editor pads and still works well.

I can see two ways for this to be addressed:

  1. provide a way to apply padding (left and right or only a single value)
  2. provide a way to provide a max-editor canvas width which would automatically provide the padding

In both cases the max-editor canvas width refers to the actual rendered text area. Smaller it fills the area. Bigger it pads.

Out of these 2. is preferrable, but 1. works as host can recalc the editor width and padding on resize operations.

It's not a critical feature, but more of a aesthetics feature. However, in searching I've found quite a few requests around this on SO and other places, and none seem to have solved this issue satisfactory. This could probably be fixed fairly easily with explicit padding in the line format along with recalculating the actual pixel width of the absolute editor surface width.

Maybe this is possible with CSS but neither I or any of the coding agents I tried could make this work.

Metadata

Metadata

Labels

feature-requestRequest for new features or functionality

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions