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

Remove api/s that has never been supported #10581

Merged
merged 9 commits into from
May 30, 2021

Conversation

saschanaz
Copy link
Contributor

Summary

Splitted from #6854 and covers changes only in api/. @foolip

Test results and supporting details

Related issues

#6809

@github-actions github-actions bot added the data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API label May 22, 2021
@saschanaz
Copy link
Contributor Author

saschanaz commented May 22, 2021

Hmm, probably better to split further? (#10582, probably not worth to split more)

},
"firefox_android": {
"version_added": false,
"notes": "Available only in nightly builds."
Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are several notes here like this, but I guess we can remove them since the interface itself is deprecated and thus we don't expected them to be shipped.

Copy link
Contributor

Choose a reason for hiding this comment

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

@Elchi3 do you have a link to the recent issue about representing preview browsers? I can't find it...

But in any case I agree with removing this one.

Copy link
Member

Choose a reason for hiding this comment

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

Removing sounds good to me, too.
The proposal on "preview" is here: #10334 (and I think it would address this use case)

@foolip
Copy link
Contributor

foolip commented May 23, 2021

I'll review this as-is and if there are tricky bits those could be split further.

Copy link
Contributor

@foolip foolip left a comment

Choose a reason for hiding this comment

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

Thanks! Some of this could be merged now, and some needs to be paired with content updates. If you want to break this PR into smaller bits, I'd be happy to rubberstamp the result if it's just a subset of this.

}
}
},
"isPrimary": {
Copy link
Contributor

Choose a reason for hiding this comment

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

This is also being updated in #10197.

@@ -272,104 +272,6 @@
}
}
},
"getCharacteristics": {
Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -1,53 +0,0 @@
{
"api": {
"ConstrainULong": {
Copy link
Contributor

Choose a reason for hiding this comment

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

This is covered by #9930. The reason this is all-false is probably that Chromium, Gecko and WebKit all have ConstrainLong in its source for MediaTrackConstraintSet and not ConstrainULong.

I guess a spec issue to use ConstrainLong in the spec as well would be best here.

@@ -11217,54 +11217,6 @@
}
}
},
"undoManager": {
Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -11217,54 +11217,6 @@
}
}
},
"undoManager": {
"__compat": {
"mdn_url": "https://developer.mozilla.org/docs/Web/API/Document/undoManager",
Copy link
Contributor

Choose a reason for hiding this comment

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

404, nothing to clean up here 👍

@@ -1,53 +0,0 @@
{
"api": {
"ULongRange": {
Copy link
Contributor

Choose a reason for hiding this comment

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

This is like ConstrainULong, a long vs. unsigned long difference in spec and implementations. I'd break these two out into a separate PR.

@@ -1,200 +0,0 @@
{
"api": {
"XRPermissionDescriptor": {
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a dictionary, which I don't think we should have in BCD but sometimes do. But whatever the rule on that, there's no trace of XRPermissionDescriptor in Chromium, Gecko or WebKit so this removal is fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a dictionary, which I don't think we should have in BCD but sometimes do.

Is there a guideline for the "sometimes do" part?

Copy link
Contributor

Choose a reason for hiding this comment

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

My opinion is that they should never be in BCD, like mixins, but there's no guideline AFAIK. @ddbeck and @Elchi3 might have opinions too.

Copy link
Contributor

Choose a reason for hiding this comment

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

Splitting out this and the following XR thing would unblock this PR I think.

@@ -1,102 +0,0 @@
{
"api": {
"XRPermissionStatus": {
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't find this interface in Chromium, Gecko or WebKit except in tests/comments, so OK to remove.

"api": {
"XRPermissionStatus": {
"__compat": {
"mdn_url": "https://developer.mozilla.org/docs/Web/API/XRPermissionStatus",
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It still exists in the spec and there is a tracking issue https://bugzilla.mozilla.org/show_bug.cgi?id=1582344, so maybe it should remain? 🤔

Copy link
Contributor

Choose a reason for hiding this comment

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

Is it shipped anywhere yet?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nah, but there have been requests to keep things that authors want to eventually ship, #6954 (comment) for example. #10619 is relevant here I guess.

"api": {
"XRPermissionDescriptor": {
"__compat": {
"mdn_url": "https://developer.mozilla.org/docs/Web/API/XRPermissionDescriptor",
Copy link
Contributor

Choose a reason for hiding this comment

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

saschanaz added a commit to saschanaz/browser-compat-data that referenced this pull request May 24, 2021
@foolip
Copy link
Contributor

foolip commented May 24, 2021

@saschanaz will you also send a PR to remove the same bits on MDN, or would you like someone else to take care of it?

foolip added a commit to foolip/content that referenced this pull request May 28, 2021
Element.tabStop is redirected to ShadowRoot.delegatesFocus per the
description in the removed page.

HTMLElement.forceSpellCheck is redirected to the spellcheck attributes,
as the closest / most relevant thing on the platform.

The regionCode entries are redirected to their parent interfaces.

BCD cleanup: mdn/browser-compat-data#10581
@foolip
Copy link
Contributor

foolip commented May 28, 2021

I've sent mdn/content#5434 to go with this PR.

sideshowbarker pushed a commit to foolip/content that referenced this pull request May 29, 2021
Element.tabStop is redirected to ShadowRoot.delegatesFocus per the
description in the removed page.

HTMLElement.forceSpellCheck is redirected to the spellcheck attributes,
as the closest / most relevant thing on the platform.

The regionCode entries are redirected to their parent interfaces.

BCD cleanup: mdn/browser-compat-data#10581
@foolip foolip merged commit b79d65e into mdn:main May 30, 2021
@saschanaz saschanaz deleted the remove-nosupport-api branch May 30, 2021 11:44
ddbeck added a commit to ddbeck/browser-compat-data that referenced this pull request Jun 2, 2021
ddbeck added a commit to ddbeck/browser-compat-data that referenced this pull request Jun 3, 2021
ddbeck added a commit that referenced this pull request Jun 4, 2021
* Bump version to v3.3.6
* Add release note for #10646
* Add release note for #10581
* Add release note for #10685
* Add release note for #10691
* Add release note for #6957
* Add release note for #10721
* Add release note for #10695
* Add release note for #9821
* Add release note for #10681
* Add release note for #10725
* Add stats
* Add release date
* Wordsmith
queengooborg pushed a commit that referenced this pull request Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants