- @nornagon
- @jkleinsc
- @codebytere
- @MarshallOfSound
- @itsananderson
- @deepak1556
- @zcbenz to [docs: views API: child views and layout engine] (#271) with "plan B"
- not updated yet; followup again next meeting
-
docs: add print API consistency proposal
- Verdict: Approved
- It's been approved, promisification backwards compat will be removed in v12
-
docs: clipboard.getNativeFormat() and clipboard.writeBuffers()
- Related - Raw Clipboard Access API (Fugu)
- if we rely on the fugu api, we'd be restricted to fugu's restrictions (e.g. only accessible in renderer process, only while view is active)
- native node module is an option, but chromium already has high quality apis for this
- if/when we do our own clipboard apis, we should aim to match fugu apis as close as possible
- is there urgency on this? the current spec is close to landable, should we land it without the fugu changes and treat that as a separate thing?
- No, not urgent, it's ok to refactor.
- [ACTION] @jkleinsc to play with the fugu api and report back
-
- [WIP] feat: route frame based permission checks through our permission check handler
- Verdict: No objections, let's go ahead.
- Kind of a bugfix
- feat: add APIs for accessing NSUserDefaults in the given domain
- inactive
- feat: add desktopCapturer.getWebContentsStream() to get media stream id from web contents
- discussion ongoing
- feat: add support for optimizing simple objects and functions over the context bridge
- pending perf tests
- feat: add new render-process-gone event
- Should update doc to reflect it could be thrown from multiple WebContents
- can we get the process id of the crashed process to detect dupes? => chromium doesn't give us that info, though maybe we could collect it somehow? for future work.
- Verdict: Go ahead.
- [WIP] feat: route frame based permission checks through our permission check handler
-
crashReporterAPI changes: #23265- some docs-parser issues
- Verdict: Go ahead.