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

Attributes potentially incorrectly set to introduced in Chrome 44 #7755

Closed
foolip opened this issue Dec 14, 2020 · 12 comments
Closed

Attributes potentially incorrectly set to introduced in Chrome 44 #7755

foolip opened this issue Dec 14, 2020 · 12 comments
Assignees
Labels
data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API

Comments

@foolip
Copy link
Contributor

foolip commented Dec 14, 2020

The kind of issue with attributes, and in particular length attributes, mentioned in #7749 (review) appears to already have happened in BCD.

These are attributes claimed to be introduced in Chrome 44 that need double checking:

  • api.AudioBufferSourceNode.detune
  • api.CSSKeyframesRule.cssRules
  • api.CSSKeyframesRule.name
  • api.CSSStyleDeclaration.length
  • api.Document.scrollingElement
  • api.HTMLAllCollection.length
  • api.TextTrackList.length
@foolip foolip added the data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API label Dec 14, 2020
@foolip
Copy link
Contributor Author

foolip commented Dec 14, 2020

#7843 is similar, but for Chrome 43.

@ddbeck
Copy link
Collaborator

ddbeck commented Dec 17, 2020

I don't follow the problem for length here. Can you elaborate on what we're talking about here? The linked review wasn't particularly illuminating (just "suspicious").

@foolip
Copy link
Contributor Author

foolip commented Dec 17, 2020

I haven't looked into the details, but length properties seem to often be different from other attributes, appearing on instances rather than on the prototype even after the point where attributes in general moved from the instances to prototypes in various engines.

But in addressing this issue there's no need to handle length properties differently, like for all attributes we just need to check if they're on an instance rather than just looking at the prototype.

@queengooborg
Copy link
Contributor

I researched this and found the following info:

I'll submit PRs for these!

@queengooborg
Copy link
Contributor

PRs have been submitted for the two I'm able to update at this point -- I plan to follow up with CSSKeyframesRule in the future, once the test is fixed!

@foolip
Copy link
Contributor Author

foolip commented Apr 18, 2022

@queengooborg did you mean to close this even though the fixes aren't landed yet?

@queengooborg
Copy link
Contributor

I did, with the thought that we will follow up with collector results as it is. If you'd prefer, we can keep it open until the collector's fixed and the data has all been fixed!

@foolip
Copy link
Contributor Author

foolip commented May 5, 2022

I ran npm run traverse chrome api 44 again and this isn't totally fixed yet, I've confirmed the following are wrong because they're in Chrome 43 per the collector:

@foolip foolip reopened this May 5, 2022
@foolip
Copy link
Contributor Author

foolip commented May 13, 2022

With #15864 merged only CSSKeyframesRule remains from the original list.

@foolip
Copy link
Contributor Author

foolip commented May 16, 2022

Two more that will need to be checked, added since I filed this issue:

  • api.Notification.data
  • api.Response.redirect

foolip added a commit to foolip/browser-compat-data that referenced this issue May 16, 2022
This was wrong due to testing for attributes in prototypes.

This has been in WebKit since the very beginning of the feature:
WebKit/WebKit@63f0b70

Copy the earliest versions of the parent feature. Also test
http://mdn-bcd-collector.appspot.com/tests/api/CSSKeyframesRule to
confirm support in the following browsers:

 - Chrome 15
 - IE 10
 - Opera 12.16
 - Safari 5

Part of mdn#7755.
@foolip
Copy link
Contributor Author

foolip commented May 16, 2022

https://mdn-bcd-collector.appspot.com/tests/api/Notification/data confirmed with Chrome 43/44, and that test doesn't use prototype testing.

@foolip
Copy link
Contributor Author

foolip commented May 16, 2022

api.Response.redirect is a method, so can't have this problem. Closing.

@foolip foolip closed this as completed May 16, 2022
queengooborg pushed a commit that referenced this issue May 17, 2022
This was wrong due to testing for attributes in prototypes.

This has been in WebKit since the very beginning of the feature:
WebKit/WebKit@63f0b70

Copy the earliest versions of the parent feature. Also test
http://mdn-bcd-collector.appspot.com/tests/api/CSSKeyframesRule to
confirm support in the following browsers:

 - Chrome 15
 - IE 10
 - Opera 12.16
 - Safari 5

Part of #7755.
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

No branches or pull requests

3 participants