W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [webcomponents]: Making Shadow DOM Subtrees Traversable

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 25 Feb 2013 14:30:32 -0500
Message-ID: <512BBBD8.5050306@mit.edu>
To: public-webapps@w3.org
On 2/25/13 1:52 PM, Scott Miles wrote:
> Given Boris' arguments, Big Marketshare can simply always mess up his
> project and blame me and it's my fault.


That's how it often works in the court of public opinion, yes.

Your employer is not immune to this behavior.

> I don't accept it.

That's nice.  So what?

> Btw, If Big Marketshare is so powerful, why haven't we already fixed
> whatever thing he is monkey patching?

Because he hasn't bothered to tell us about it; just monkeypatched and 
shipped (not least because he didn't want to wait for us to fix it). 
Again, your employer is not immune to this behavior.

> Also, Optimizely, et al, doesn't simply appear at random.

Sure.  They get included by the page, but the page may not realize what 
all they then go and mess with.

> Again, seems
> like your argument is that some developer or user may take wanton stet X
> to break my stuff, and I must prevent it or it's my fault.

I think you're trying to paint this black-or-white in a way that seems 
more about arguing strawmen than addressing the problem.

When something breaks in app A due to a change in component B, the 
problem could be fixed in B, in A, neither, or both.

What happens in practice typically depends on the specifics of the 
change an the specifics of who A and B are, what contracts they have 
signed, and how much market power they have.

You may not like this.  _I_ don't like it.  But it's reality.

> re: "forced depend on where they got their tomatoes from" and "You
> cannot accidentally stumble into ShadowDOM"
> The reason the latter keeps being mentioned is because of statements
> like the former. Nobody is forcing anybody to break encapsulation. Seems
> to me the demarcation is very clear.

My point is that people will break encapsulation without being forced 
to.  A lot.  At least that's what my implementation experience with XBL 
leads me to believe.

> Lastly, my point about upgrade statistics is only that the intersection
> of the two sets is generally going to be smaller than the union of them.


Received on Monday, 25 February 2013 19:31:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:58 UTC