Re: [w3c/webcomponents] A way to detect if a custom element was constructed during customElements.define call? (#790)

I just noticed my comment was posted twice due to network disconnection. Nothing I tried to post here was repetitive from my perspective, but fault of GitHub's erroneous way of handling internet connectivity.

Sorry if you thought I posted anything twice.

My point stands: posting to SO will make any sort of discussion on the topic difficult, and will not help the standards process.

The standards process should involve user-centric analysis of what users can/want to do, and SO is obviously not the best place for that. 

The things I'm trying to discuss are about wants/desires that are otherwise difficult, unintuitive, and error-prone to achieve, and telling people to go to Stack Overflow is similar to saying "shoo fly" without caring about the end user as much as they can be cared for.

This is _**same reason**_, IMO, why the private fields proposal has such an [**_incredibly high ratio of dislike to like_**](https://github.com/tc39/proposal-class-fields/issues/100) yet "standards implementers" ignore it.

At least, that's how I see it when I'm told to move along to Stack Overflow. Maybe it's something you could consider.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/790#issuecomment-461118179