Add the message_serialization manifest key page and update the data cloning algorithm section

Open Beginner friendly
#46,590 0 comments 0 reactions 0 assignees View on GitHub

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

Content:WebExt needs triage
MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Chrome_incompatibilities#data_cloning_algorithm

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.