Re: [whatwg/dom] Tie in AbortControllers with CustomElements (Issue #1296)

> Let's say you're using this element in a list that gets reordered.

my thoughts in a nutshell ... this feature would make sense only after the one requiring no  disconnect/connect handlers are invoked on reordering, so that the node never left the live tree.

On the other side, if this feature use case is to abort fetch operations, dare I say we're missing a `destructor` primitive where aborting would make more sense, as the element is clearly not reachable by any mean.

Until it's reachable, hence able to rejoin the live DOM state, I think all proposals are off because:

  * one does not simply interrupt a microtask ... if the node goes live again right before/oafter that microtask, the fetch would start over again for no benefit
  * tables where limited rows are visible but the sorting is "one click away" are still common ... nodes meant to be kept in that order/view eventually would not benefit from aborting previous operations on connect

My 2 cents around this matter, it's a cool idea full of unexplored real-world alternative use cases.

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

Message ID: <whatwg/dom/issues/1296/2237157428@github.com>