I have tested this item ✅ successfully on bacf8ff

If I'm correct we don't use inset-inline-end till now, is it save for us to use it?

Perfectly safe to use https://caniuse.com/?search=inset-inline-end

RTC

I have tested this item ✅ successfully on bacf8ff

I have seen this too JM, and I think it breaks our policy CURRENT - 2 (also current depends of the time of the major or minor release, but I'm not sure on this topic).

based on this information all PRs including 'inset-inline-end' is too early for us but have to be discussed by production

i thought it was changed to current -1

#PROD2019/005 - Change minimum version requirements for all browsers to n-2 and drop support for Internet Explorer. (per 19/05/16)

was the last motion I found... should be moved to the development strategy

@HLeithner Your package.json states otherwise:

"browserslist": [
    "last 1 version",
    "not ie < 11"
],

and before that it was in settings.json where it was merged 5july 2018

FYI, concerning Safari versions: 14.1 was an update for Mac OS Big Sur, i.e. all former versions of MacOS using Safari 14 or lower will not be compatible. Mac OS Monterey has Safari 15.

@HLeithner Your package.json states otherwise:

"browserslist": [
    "last 1 version",
    "not ie < 11"
],

then the package.json is wrong and has to be fixed

lol, after 3 and a half years?
Sounds like the motion was incorrectly written without prior research.

lol, after 3 and a half years? Sounds like the motion was incorrectly written without prior research.

no idea why it's funny when an error happens. we have 15 year old bugs.

I leave it to those far more important than me to decide. note that the settings are used to determine if autoprefix etc needs to do something to ensure old browser support

Changing to last 2 version will result in a massive amount of changes to the css generated by the autoprefixer. As a very quick example we will see the following changes in build_incomplete.html

Setting RLDQ label so release leads can decide about usage of inset-inline regarding our browser support policy.

Further information. Please remember that we have been wrorking and testing with last 1 version for 3.5 years. If you rebuild the current css with last 2 version you will see how much is different - about 9% bigger. (these tests are without by pull requests as they're not merged)

CSS Line Count

FYI, concerning Safari versions: 14.1 was an update for Mac OS Big Sur, i.e. all former versions of MacOS using Safari 14 or lower will not be compatible. Mac OS Monterey has Safari 15.

So based on this high sierra is the highest OSX version that is affected by this but already had no security support when Joomla 4.0.0 came out (security support ended december 2020). Given our CSS is already bugged in terms of giving support for this version as well I don't think it's a big deal merging these Pull Requests at this moment in time. Especially given the big savings we get in maintainability.

@wilsonge Thanks for this decision which I fully support.

Thanks for making a sensible decision.