Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of missing devtools details #20403

Open
wants to merge 19 commits into
base: main
Choose a base branch
from

Conversation

rebloor
Copy link
Contributor

@rebloor rebloor commented Jul 23, 2023

Summary

Add details, previously missing for devtools features not supported in Firefox

Related issues

Fixes #16859

@rebloor rebloor added the data:webext Compat data for Browser Extensions. https://developer.mozilla.org/Add-ons/WebExtensions label Jul 23, 2023
@rebloor rebloor requested a review from Rob--W July 23, 2023 10:58
@rebloor rebloor self-assigned this Jul 23, 2023
Copy link
Member

@Rob--W Rob--W left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: why are some features of edge not a mirror of Chrome?

@rebloor
Copy link
Contributor Author

rebloor commented Jul 27, 2023

@Rob--W

Question: why are some features of edge not a mirror of Chrome?

Because I missed updating them from the copied content. I will fix that.

@rebloor rebloor marked this pull request as ready for review August 9, 2023 02:09
@rebloor rebloor requested a review from Rob--W August 9, 2023 02:09
@github-actions github-actions bot added the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Oct 27, 2023
@github-actions
Copy link

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

@github-actions github-actions bot removed the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Oct 27, 2023
@queengooborg
Copy link
Contributor

Hey @Rob--W, looks like this has been waiting on your review for a while!

@Rob--W
Copy link
Member

Rob--W commented Nov 7, 2023

While I'm not against adding explicit entries for API support statuses in the BCD, the BCD also link to MDN documentation that haven't been merged yet.

I am reluctant to merge these MDN articles, because they document Chrome-only behavior. It's my intent to revisit these PRs eventually, but it's a low priority for me.

@Elchi3
Copy link
Member

Elchi3 commented Nov 10, 2023

Should we try to get a Chrome reviewer for this one?

@Rob--W
Copy link
Member

Rob--W commented Nov 10, 2023

That's not necessary. I am familiar with this API in both Firefox and Chrome.

The difficulty here is presenting the content in a way such that it is obvious which parts are cross-browser and which ones are Chrome-only. The current documentation lists the least common denominator, so anyone who relies on that can build an extension that works across browsers.

If we add the Chrome-specific bits here as well, then I'm concerned that an extension dev would try out the documentation and then become disappointed when they discovered that the documented features don't actually work in Firefox.

@queengooborg
Copy link
Contributor

I think that so long as the browser compatibility data is up to date, then we should be fine on that front. Web extensions don't have a standard specification that we can refer to, so since browsers are free to implement what they want to, I wouldn't expect much cross-browser support anyways.

@rebloor
Copy link
Contributor Author

rebloor commented Nov 13, 2023

Also addresses #16859

@github-actions github-actions bot added the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Mar 8, 2024
Copy link

github-actions bot commented Mar 8, 2024

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

@queengooborg
Copy link
Contributor

This PR has been sitting around in need of a review for a while, and is the second oldest PR open. We should get this reviewed and landed, or close it!

@Rob--W
Copy link
Member

Rob--W commented May 12, 2024

I think that it is okay for BCD notes to be added, even without mdn documentation. @rebloor could you update the PR and tag dotproto for review? If there is anything that requires my attention, please pm me.

@github-actions github-actions bot removed the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label May 15, 2024
@rebloor rebloor requested a review from dotproto May 15, 2024 02:01
Copy link
Collaborator

@dotproto dotproto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

"mdn_url": "https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/devtools/inspectedWindow/resource",
"support": {
"chrome": {
"version_added": true
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to figure out when this and the other compact entries were added in Chromium, but unfortunately I ran out of history to inspect. The most concrete thing I can say is that this is the earliest commit I see where onResourceAdded and other such properties are exposed in third_party/closure_compiler/externs/chrome_extensions.js. That commit landed in m68. Based on some testing of old Chromium versions, it seem to be older than that, but I can't determine how much older because I haven't been able to get a Chromium build older than 68 to run locally.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Closure compiler is not the right reference for when it was introduced. It merely added typing.

Considering that Resource specifies the type of getResources, it is safe to use the same version as getResources.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dotproto @Rob--W It looks like it was added in chromium/chromium@e975d11, i.e. 22.0.1223.0, before Chrome 22 (22.0.1229). Or is this only when the docs landed? 🤔

"chrome": {
"version_added": true
},
"edge": "mirror",
Copy link
Collaborator

@dotproto dotproto Jul 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rebloor, does "mirror" automatically indicate that this only came in after Edge adopted Chromium?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dotproto That is my understanding

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can confirm this.

webextensions/api/devtools.json Outdated Show resolved Hide resolved
webextensions/api/devtools.json Outdated Show resolved Hide resolved
"mdn_url": "https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/devtools/panels/SourcesPanel/onSelectionChanged",
"support": {
"chrome": {
"version_added": true
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This appears to be from before Chrome 21 as the reference to this file existed before the oldest historical entry on chrome/common/extensions/api/devtools/panels.json.

@github-actions github-actions bot added the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Aug 4, 2024
Copy link

github-actions bot commented Aug 4, 2024

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

@github-actions github-actions bot removed the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Aug 8, 2024
@github-actions github-actions bot added the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Aug 9, 2024
Copy link

github-actions bot commented Aug 9, 2024

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

@github-actions github-actions bot removed the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Aug 9, 2024
@queengooborg queengooborg marked this pull request as draft August 28, 2024 13:44
@rebloor rebloor marked this pull request as ready for review September 13, 2024 18:47
@github-actions github-actions bot added the size:l [PR only] 101-1000 LoC changed label Nov 22, 2024
@caugner
Copy link
Contributor

caugner commented Dec 3, 2024

@rebloor Since this PR updates support data for Chromium, Firefox, and Safari, and we seem to be differently certain about each of the browsers, how about we split this up and extract Chromium/Safari changes into two separate PRs? I think it'll be easier to land it that way.

PS: Meanwhile eef1292 has added some Chromium data for the devtools API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:webext Compat data for Browser Extensions. https://developer.mozilla.org/Add-ons/WebExtensions size:l [PR only] 101-1000 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Content suggestion: chrome.devtools.panels.SourcesPanel
6 participants