docs: add ResourceType.json

[seia-soto]

Description

This adds the type of json in ResourceType from webRequest.ResourceType and declarativeNetRequest.ResourceType.

Motivation

This reflects the latest changes from Firefox source code. json is pretty broad word to use without details.

Note that it looks like not released yet, so I don't know if this is okay to go now.

Additional details

refs mozilla/gecko-dev@e6a7800
refs https://searchfox.org/mozilla-central/rev/fcfb558f8946f3648d962576125af46bf6e2910a/toolkit/components/extensions/schemas/web_request.json
refs https://searchfox.org/mozilla-central/rev/fcfb558f8946f3648d962576125af46bf6e2910a/toolkit/components/extensions/schemas/declarative_net_request.json
refs https://bugzilla.mozilla.org/show_bug.cgi?id=1858078

Related issues and pull requests

[github-actions]

Preview URLs

• /en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/ResourceType
• /en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/ResourceType

(comment last updated: 2025-02-28 22:04:34)

[rebloor]

@seia-soto thanks for picking up this change. This should also have an entry in the release notes and an update made to the BCD.

[seia-soto]

@rebloor Thanks for picking up the places.

For browser compatibility data, I already put the issue here: mdn/browser-compat-data#26016.

However, I couldn't verify the request type existence so far on Firefox. I tried to trigger JSON module import by using both static and dynamic form, but both of webRequest.onHeaderReceived and webRequest.onBeforeRequest handler showed me a value of script on Firefox v136.

I expect this will be settled with import attribution (and here's a direct URL to the corresponding Firefox meta issue) by looking at this test code.

For Chromium, they also don't ship it yet and it looks like nothing decided in this Chromium issue.

I'll update this pull as the situation changes.

[rebloor]

@dotproto know anything about this?

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[dotproto]

@dotproto know anything about this?

Sorry for the late reply. The "json" resource type is new to me, but happy to help chase down info.

I haven't tried myself, but I think this feature should now work as expected in Firefox Nightly.

Seems mdn/browser-compat-data#26016 was closed as the feature behind the introduction of the "json" value wasn't supported. It seems the flag is being default enabled in Firefox 138, so we should be able to revisit that shortly. Also, I've added a question to the BCD ticket to clarify my understanding of the availability requirement for future reference.

[github-actions]

Preview URLs

• /en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/ResourceType
• /en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/ResourceType
• /en-US/docs/Mozilla/Firefox/Releases/138

Flaws (1)

Note! 2 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Mozilla/Firefox/Releases/138
Title: Firefox 138 for developers
Flaw count: 1

• broken_links:
  • Can't resolve /en-US/docs/Web/API/HTML_Sanitizer_API

External URLs (2)

URL: /en-US/docs/Mozilla/Firefox/Releases/138
Title: Firefox 138 for developers

• https://bugzil.la/1858078 (1 time) (Note! This may be a new URL 👀)
• https://bugzil.la/1950836 (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2025-05-05 08:11:35)

[rebloor]

@seia-soto we also need release notes, which are made on source/firefox/138

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[seia-soto]

@rebloor release note updated.

• Accidentally rebased to seia-soto:main which is outdated not mdn:main.

[rebloor]

Thanks @seia-soto