-
Notifications
You must be signed in to change notification settings - Fork 2.6k
chore(link): update link issue for Custom Elements extends #5418
Conversation
I prefer if we keep the link as-is. It has all the historical discussion. |
Oh, I understand. Actually I was thinking could be misunderstanding come up on a closed issue as reference. A new folk can assume is a "closed argument" instead of scrolling down the whole page and find the correct issue. Maybe is worth adding also the new issue within the old one? I don't know. If not, we can close this one then. |
Ok, let's add a link to the new one in addition to the old one. Sound good? |
Yep, sounds good to me. Do you have some specific copy to add to explain that there are two main issues? |
@ebidel - when you're happy with this, feel free to merge. |
"Voice your thoughts on 509 and 662". Include the links of course. |
@ebidel I think I have problems with some languages (like Chinese). Someone can help with this? |
Thanks for the contribution @LasaleFamine |
🎉 This has been pushed live to https://developers.google.com/web/ |
Updating link for the issue related to native elements extension. (WICG/webcomponents#662)