Joey Arhar

> I think without fully understanding (and specifying) #808 it's hard to reason about how moving-within-a-parent should work. I.e., what side effects we need and do not need. Moving within...

> @josepharhar Why shouldn't it fire a mutation event of a new type? If a new method is added specifically for moving elements around, they can't possibly fire that mutation...

> I would really like to better understand what the use cases are. Could someone provide a concrete scenario (not just framework X does Y so they need it) in...

> I don't think that discussion was really settled though. Those arguments would apply to moving within a parent as well as you have to contend with subtrees and multiple...

> an atomic DOM child node move operation would be extremely valuable Are you suggesting that the reordering idea proposed here isn't good enough, and that we need to be...

Thanks for the response @domenic, I can see how this is just a part of making all the DOM APIs accept more characters. I saw another crbug about a similar...

Sounds great! I'd \*imagine\* that it wouldn't be that hard to implement either. Perhaps we should start by listing all of the particular APIs that we would need to change?

Thanks, that makes sense. Should we just change the spec and implement it? Should we ask for support from firefox and safari?

I am currently implementing https://bugs.chromium.org/p/chromium/issues/detail?id=1052152 and it looks like in the process of doing so I am also implementing the desired behavior of this issue as a side effect. I...

I was working on color-contrast() in chromium and I'm wondering what the status is to change/ship it. It seems like there was some feedback about color-contrast earlier in this issue...