Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)

@sorvell 

> Perhaps the behavior here can be revisited based on developer feedback from testing of initial implementations.

that's a well known slippery slope ... once stuff lands as standard it's already too late to change it because at that point they will tell us "*it's too late, we have already these frameworks using this API as it is*".

It happened before, it will happen again ... what I think it's missing in here, is some consistency with newly proposed APIs ... `remove`, `append`, `before`, `after` felt like fresh air and great ergonomics to deal with, we're back with "*users requested X, we're providing Y because Y is better*" ... maybe those days where everyone flocked to jQuery because everything never literally threw out of the box are forgotten and I'd rather see a state duplicated than a broken highly dynamic page in the wild, especially in these days.

I guess that's just my opinion though.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1255#issuecomment-2493879435
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1255/2493879435@github.com>