Intended meaning/precision of WebKit engine version?
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
Since Safari 9, WebKit engine version numbers in safari.json and safari_ios.json are given with 3 version components. For example, Safari 14 is 610.1.28:
https://github.com/mdn/browser-compat-data/blob/e05c9e9ad76ff6023d5c717059d682e8b4e778f8/browsers/safari.json#L170-L176
However, current Safari 14.0.2 has "16610.3.7.1.9" in "About Safari", which I take to be WebKit 610.3.7.
Neither 610.1.28 or 610.3.7 are WebKit trunk versions, those reached only 610.1.26 and 610.2.2 before bumping to 611.
Since I've used these numbers to figure out the Safari version for a change from WebKit trunk, knowing how to interpret it is important.
So, should this be the WebKit version given in the earliest release of that Safari version, or should it be the version of WebKit trunk it was based on?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Safari entries in safari.json and safari_ios.json linked in the issue, then compare their recorded WebKit versions with the version formats described in the issue. Determine whether the data should represent the earliest release, the WebKit trunk base, or another convention; the issue is done when that interpretation is resolved and the affected data or guidance can be updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100