- From: Daniel Vogelheim <notifications@github.com>
- Date: Mon, 15 Apr 2024 10:14:26 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/pull/1268/review/2001747052@github.com>
@otherdaniel commented on this pull request. > @@ -6484,8 +6514,19 @@ string <var>namespace</var> (default null):</p> <li><p>If <var>oldAttr</var> is <var>attr</var>, return <var>attr</var>. - <li><p>If <var>oldAttr</var> is non-null, then <a lt="replace an attribute">replace</a> - <var>oldAttr</var> with <var>attr</var>. + <li> + <p>If <var>oldAttr</var> is non-null, then:</p> + + <ul> + <li><p><a>Validate and set attribute value</a> <var>attr</var>'s <a for="Attr">value</a> for + <var>attr</var> with <var>element</var>. + + <li><p>If <var>element</var> <a lt="has an attribute">has</a> an <a>attribute</a> I still find it difficult to wrap my head around this logic. I think conceptually, we want to have the old value -- from before the call, and thus before a default policy might have mucked with it. That's what should go into the change attribute logic. But once we have that, I'm not sure why we'd need to throw an exception here. I'm not sure why we'd have to care whether the default policy does anything funny with the attribute in the mean time. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1268#pullrequestreview-2001747052 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1268/review/2001747052@github.com>
Received on Monday, 15 April 2024 17:14:30 UTC