Add the message_serialization manifest key page and update the data cloning algorithm section
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start with the WebExtensions manifest.json key list and the Chrome incompatibilities page’s “Data cloning algorithm” section. Add a page for the message_serialization key, link it from the key list, and update the Chrome bullet to describe opting into structured clone; check the cited browser documentation and compatibility references. Done when all three documentation updates reflect the issue’s stated behavior.
Written by the indexing model from the issue text.
Description
MDN URL
What specific section or headline is this issue about?
Data cloning algorithm, and a missing page for the message_serialization manifest key.
What information was incorrect, unhelpful, or incomplete?
The message_serialization manifest key has no page. Chrome 148 supports it, and Safari Technology Preview 257 adds it. With "structured_clone", an extension sends messages with the structured clone algorithm instead of JSON. The default is "json".
The Chrome bullet in "Data cloning algorithm" says Chrome uses JSON and may switch to structured cloning in the future. Chrome now lets an extension opt in.
What did you expect to see?
A message_serialization manifest key page, a link to it from the manifest.json key list, and an updated Chrome bullet in "Data cloning algorithm".
Do you have any supporting links, references, or citations?
- Dominant language
- Markdown
- Stars
- 11.1k
- Forks
- 23.3k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 187
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from mdn/content
-
CSS Custom Highlight API: mention StaticRange for highlights that outlive DOM changesPossibly taken @abdul-karim-mia claimed this 4 days ago. OpenContent:WebAPI help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Content:Meta needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
can `name` of objects in `webRequest.HttpHeaders` repeat?Possibly taken @Ashish-CodeJourney claimed this 2 days ago. OpenContent:WebExt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mdn/content#46472 · 1 comment ·
Maintainers usually reply within 1 day
-
`filter` creating a containing block unmentionedPossibly taken @Ganeshguru5 claimed this 3 days ago. OpenContent:CSS
Difficulty 1/5 Under an hour Newbie friendliness 75/100
mdn/content#46414 · 2 comments ·
Maintainers usually reply within 1 day
-
<img> srcset and responsive images guide: image source selection is now defined normativelyPossibly taken @veersingh2007chauhan-cmyk claimed this 11 days ago. OpenContent:HTML
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mdn/content#46377 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 85/100
sindresorhus/eslint-plugin-unicorn#4034 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
francescopace/espectre#223 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100