Time to change x and y padding and margin to logical equivalents?

[hfournier]

There are obvious upsides to using logical properties, so are there any reasons not to change px-, py-, mx- and my- to output their logical equivalents?
For example, currently px-value results in:

{
    padding-left: value;
    padding-right: value;
}

Wouldn't it be preferable to have:

{
    padding-inline: value;
}

instead? Seems logical 😉
This was mentioned in #10166, but was not addressed.

[adamwathan]

What’s the benefit in your mind, just the reduction in CSS size? My main hesitation is px implies horizontal but padding-inline is only horizontal in horizontal writing modes.

[hfournier]

Yeah, I guess size would be one thing (about 50%), although fairly minor (for me), and more concise code-wise.
However, now that I think about it, since the padding (or margin) would be the same on either side (left-right), there's no benefit of using inline. and the same for block. I thought it might be a good option after reading this article.
Is there a way to provide it as a config option, so devs could choose whether they want physical or logical properties? That way, if you're only dealing with horizontal (most cases), you get some benefit without the risk.