| 06:59 | <annevk> | FYI: we're considering using "flatten" as a term-of-art for replace a node with its children in the Sanitizer API (and potentially more widely in the DOM at some future point). |
| 07:44 | <rkirsling> | I guess it makes sense if you think of it from the perspective of that node's parent? |
| 07:45 | <Domenic> | Hmm I would prefer replaceWithChildren, to mirror the existing replaceWith and replaceChildren |
| 07:48 | <rkirsling> | right. I guess what I'm saying is that I'd expect flatten to turn grandchildren into children |
| 07:52 | <annevk> | Domenic: that's a bit too long for a Sanitizer API configuration option, needs to be somethingElements |
| 07:53 | <annevk> | With the sanitizer the perspective is that of the parent I think, hmm |
| 08:36 | <rkirsling> | I want to suggest disintegrate but I think it's a bit too playful :p |
| 09:27 | <Domenic> | Domenic: that's a bit too long for a Sanitizer API configuration option, needs to be |
| 09:48 | <annevk> | Domenic: I'm not sure what you mean |
| 09:50 | <annevk> | Domenic: currently the top-level entries of the configuration dictionary are elements, removeElements, attributes (for global attributes), removeAttributes (for global attributes), and flattenElements |
| 11:21 | <jmdyck> | FYI: we're considering using "flatten" as a term-of-art for replace a node with its children in the Sanitizer API (and potentially more widely in the DOM at some future point). dissolving the node. But replaceWithChildren would be clearer if it fits. |
| 12:56 | <Domenic> | annevk: I mean you could use replaceWithChildren as a name instead of replaceWithChildrenElements. It's unambiguous because replaceWithChildrenAttributes makes no sense. |
| 13:04 | <annevk> | I see, I like the symmetry of the existing names better, but worth seeing what others think I suppose |