pageGutter and scrollPadding properties are conflicting

[JayPanoz]

We've been historically using pageGutter as a way to handle space between columns as it is a lot easier to handle padding on body for scrollX progression, etc. than column-gap, which is not being applied at the start and the end of the columns context.

We recently added scrollPadding properties as a way to add padding in scroll view so that, for instance, you can handle safe inset areas or, more simply, make sure content at the start or end of the resource is not displayed under UI such as top and bottom bars, etc.

Problem is pageGutter conflicts with two scrollPadding properties depending on the writing mode (pageGutter behaving as a logical property), and it's been really hard to reach a resolution. In TS-Toolkit for instance, left and right scrollPadding are currently disabled.

The current design is not very developer-friendly, and I'm afraid we won't be able to ever make it friendlier. It should probably be rethought so that it makes sense independently of the paginated/scroll view.

The challenge remains that we cannot apply block padding in columns tho, as it would mess up vh pretty badly, which is why it was specific to scroll in the first place.

Other options include:

• restricting pageGutter to paginated view and requiring scrollPadding to be handled programmatically if you want to apply the same value in scroll view
• making scrollPadding a logical property for block-start|end, with pageGutter – possibly renamed – being its inline counterpart.