Publish minutes of 2025-09-25 meeting #874
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotproto
requested changes
Oct 1, 2025
| * [oliver] Out of curiosity, does Safari support externally_connectable? | ||
| * [kiara] We support externally_connectable, but not the ids key yet. | ||
| * [timothy] One of the complications is the ID passed on the website differs between Chrome and Safari. That has to be documented differently, but that can be part of the sendMessage spec. | ||
| * [tomislav] Is the value of the ID in Safari an object? String?. |
There was a problem hiding this comment.
Suggested change
| * [tomislav] Is the value of the ID in Safari an object? String?. | |
| * [tomislav] Is the value of the ID in Safari an object? String? |
| * [rob] Most overhead is in having to send the manifest to all processes; after that there is little gain between returning the full manifest vs just the version. | ||
| * [timothy] Yes. I suppose that it would only make a difference if we ever consider deprecating getManifest(). | ||
| * [rob] Which I don't see happening. | ||
| * [rob] If the use case is to return specific values, why wouldn't we expand `runtime.getManifest()` with a parameter that specifies the key the developer is interested in? |
There was a problem hiding this comment.
I remember that someone said the the intent here was to pave the cow paths on common patterns, but I don't recall who. @xeenon, maybe?
There was a problem hiding this comment.
I'm not sure when, but I definitely said something along those lines at one point. Feel free to drop it in if that helps the flow of the conversation :)
a0bd5da to
b626a23
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 issues #871, #531, #872, #400, #843 and PRs #873, #837.
Reminder: TPAC 2025 is happening soon; If you are interested in participating or have topics, please see #843.