Feeling Lucky
NPM Resource Changed
?
[#39320] - Align the browserlist to the advertised support
- Fixed in Code Base
- 27 Nov 2022
- Medium
- Build: 4.2-dev
- # 39320
- Diff
- dgrammatiko:patch-4
User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Summary of Changes
Following the discussion on the #39315 it's obvious that what is used in the browserlist supported browsers IS NOT what the project actually advertises as the supported browsers.
- Mind that
last 2 versionsfor Safari will result to 16.0 and 16.1 (both Chrome based and FF have a few weeks [4 -6] for each0 version which btw is a MAJOR) - Using
last 2 major versionsfor Safari will result to 15.0 and 16.*
Testing Instructions
Actual result BEFORE applying this Pull Request
Expected result AFTER applying this Pull Request
Link to documentations
Please select:
-
Documentation link for docs.joomla.org:
-
No documentation changes for docs.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | NPM Change |
| Labels |
Added:
NPM Resource Changed
?
|
||
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-11-27 08:21:58 |
| Closed_By | ⇒ | HLeithner |
I would expect this has no impact on npm as long as no npm update is done, so I merge this into 4.2
thanks @dgrammatiko