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

Introduce the new WebIDL mixin syntax interfaces/* #8092

Closed
wants to merge 1 commit into from
Closed

Introduce the new WebIDL mixin syntax interfaces/* #8092

wants to merge 1 commit into from

Conversation

romandev
Copy link
Member

@romandev romandev commented Nov 7, 2017

This patch includes the following things:

  • Remove any tests for implements statements.
  • Remove any tests for non-legacy usage of the [NoInterfaceObject]
    extended attribute.
  • Add tests for includes statements and interface mixins.

This fixes some parts of #8054 issue.

Copy link
Contributor

@tobie tobie left a comment

Choose a reason for hiding this comment

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

So what's important is that the IDL in the interfaces/ directory reflects the IDL contained in the specs. It seems that this pull request changes the IDL locally only, and not in the specs upstreams. So that's really where you want to start.

@ghost
Copy link

ghost commented Nov 7, 2017

Build PASSED

Started: 2017-11-29 10:36:04
Finished: 2017-11-29 10:39:24

View more information about this build on:

Copy link
Contributor

@marcoscaceres marcoscaceres left a comment

Choose a reason for hiding this comment

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

Couple of questions....

const registration = service_worker_unregister_and_register(
test, 'resources/sw-payment-handler.js', 'resources/');
await wait_for_state(test, registration.installing, 'installing');
try {
Copy link
Contributor

Choose a reason for hiding this comment

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

Won’t this throw because of the permission check?

enabledMethods: ['test_pay']
});
} catch (e) {
console.log(e);
Copy link
Contributor

Choose a reason for hiding this comment

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

If it throws, we probably want the test to fail, no?

This change covers basic behavior of get/set methods.
@romandev
Copy link
Member Author

Sorry for noise.. This is my mistake.. I'll close this.

@romandev romandev closed this Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants