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.
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.
I will double check, but does your issue reference the strawman proposal at all (what is linked right below)? I was looking but didn't see it.
I think an issue for this is good, but I think that would be really important to call out the strawman from the description of your issue and declare if you are building off of it, or this proposal is an entirely net new just to help set context, IMO.
I would also second the comment from Justin in that issue that it would probably make sense to have the conversation over in https://github.com/WICG/webcomponents repo, since that is where the current proposal resides.
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.
Also might be good to sync with @EisenbergEffect , who is also making some updates to this section / spec, per #41. 👍
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.
I have not found the strawman link, the communication on what to collect meant to be on inserted proposal issue which has to be referenced in this status doc. Otherwise trace-ability is lost.
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.
@thescientist13 , linked issue #32 is updated with strawman and other links from @EisenbergEffect PR #41
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.
The purpose of the issue is to serve the WCCG tracing around proposal and its status in own format, it does not fit into WICG purpose which is features discussions. I agree that WICG would benefit from summary and progress on particular feature, in slightly different format though. CC-in on Slack.
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.
So I think then we would be good if #41 just includes the link to #32 and then it would be part of our current (2022) report? Then I think we could close this one down since I don't think we're doing any back porting of older reports, but maybe that is something to corroborate with @Westbrook .
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.
Yes, please. We can close this once all relevant info is moved to the new PR.