[css-backgrounds-4] Add background-repeat-x/y

[mstange]

It looks like recent versions of Edge and Chrome support the properties background-repeat-x and background-repeat-y. I haven't checked how far back support goes. Gecko does not support them, and Webkit doesn't appear to either.
If this is something people want, then it should be added to the spec.

[yisibl]

Agree, I think it should be consistent with background-position-x/y.

[fantasai]

What's the use case for cascading them independently?

[SebastianZ]

Backgrounds and Borders Level 4 already defines those two properties plus background-position-inline and background-position-block. So, I'm wondering why this issue was opened.

Gecko does not support them, …

That info is outdated. They were implemented in Gecko 49.

… and Webkit doesn't appear to either.

I don't have the means to test it, but the related MDN articles suggest that WebKit does support background-position-x and background-position-y. Could someone please verify that and update the articles accordingly (or let me know about it, so I can do that)?

Sebastian

[mstange]

Sebastian, this is about background-repeat, not background-position. (Also, I'm the person who implemented background-position-x/y in Gecko.)

Fantasai, I don't have a use case. Maybe it's just about consistency with background-position? To me, background-repeat "feels" like a shorthand property because it allows you to specify different values for each axis.

[fantasai]

If there's no use case for cascading them independently, then we should not add longhands. And Chrome and Edge should remove them.

[tabatkins]

Our usage numbers show it at .05%, above our standard removal threshold.

[SebastianZ]

Sebastian, this is about background-repeat, not background-position. (Also, I'm the person who implemented background-position-x/y in Gecko.)

Oops! Please forgive me my blindness! I saw you've also already filed bug 1273244 for it.

Sebastian

[dbaron]

I wrote a few tests to allow testing which implementations support these.

[gregwhitworth]

Updating here that Edge does not support the longhands.

[dbaron]

It turns out that the group resolved to add these in April 2014.

(We also re-discussed them today, twice.)

[gregwhitworth]

After discussing this after the resolution, I wasn't aware that deprecated implied that all other UAs that don't support this need to add this - my understanding of it's implication was more inline with obsolete. I would like to re-open this issue and discuss roughly defining it but marking it as obsolete. In addition to this, @FremyCompany looked into why Edge removed this and it was due to us implementing multiple backgrounds, and when testing Chrome sure enough you can't have multiple backgrounds in conjunction with background-repeat-x/y (https://jsfiddle.net/u5L8ak8b/2/ - I tried numerous vals to see if they mapped them together to no avail). By switching to obsolete, it allows us to vocalize to authors not to use it and allows Blink to, when possible take the necessary steps to remove it and doesn't burden others to implement it.