Clarification on step 4 of Headers delete method

[jeenalee]

Step 4 of delete states:

1. Otherwise, if guard is "request-no-cors" and name/invalid is not a CORS-safelisted request-header, return.

I'm a little confused what invalid in this case is.

Step 5 of append is similar to step 4 of delete, and it states:

1. Otherwise, if guard is "request-no-cors" and name/value is not a CORS-safelisted request-header, return.

Is invalid in delete's step 4 a place holder for a headers value?

[annevk]

Yeah, that's the intention. I guess I can rename it placeholder and maybe add a note that it basically disqualifies Content-Type from being deleted.

[annevk]

Although I guess there's more headers these days than just Content-Type that need a "valid value".

[annevk]

Oh, doh, the reason is because delete() is not passed a value argument, so we need to make something up.

[jeenalee]

I see! It makes sense why it is phrased the way it is. Thank you for clarifying.

[annevk]

A note should probably be added to avoid confusing others.