-
Notifications
You must be signed in to change notification settings - Fork 56
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
Publish minutes of 2022-07-21 meeting #245
Conversation
4c68326
to
21611bd
Compare
21611bd
to
39e7619
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nits aside, LGTM
* [jack] I don't believe we can do this (breaking change). | ||
* [rob] The issue filer is asking to stop firing event listeners in content scripts in response to scripted actions from the web page. This is not a good idea in my opinion; extensions should be prepared to deal with events fired by web pages. | ||
* [rob] [event.isTrusted](https://developer.mozilla.org/en-US/docs/Web/API/Event/isTrusted) can already be used if the extension really cares that the event was triggered by the user. | ||
* [someone] event.isTrusted is only available to events such as click, but not to CustomEvent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zombie, did you mention this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, someone else did. I don't recall who.
39e7619
to
aa0f913
Compare
Generated from https://docs.google.com/document/d/1QkwhEMtMS67JBUkl_WVPZ4lRSKoWcQNlLJSf_GwSXg8/edit using the tool and process from #105.
During this meeting we discussed or mentioned #227, #238, #240, #241, #242, #244, #12, #162, #170, #57, #76, #77, #78, #205, #233.