Rename selectedcontent "disabled" to "in valid tree position", inverting the value#12369
Conversation
annevk
left a comment
There was a problem hiding this comment.
But also, it's maybe better if @josepharhar makes this change as part of his PR so he doesn't have to deal with a conflict?
I'm happy to deal with the merge conflict, I'd like to get this done now so it doesn't look like we have as many open select issues. I don't know when that PR will actually get merged. |
|
|
||
| <p>Every <code>selectedcontent</code> element has a boolean <dfn | ||
| data-x="selectedcontent-disabled">disabled</dfn>, which is initially false.</p> | ||
| data-x="selectedcontent-in-valid-tree-position">in valid tree position</dfn>, which is initially |
There was a problem hiding this comment.
This is still changing an ID. I'm also not entirely sure about defaulting to true. I guess it's only an anti-pattern for arguments, but it feels kinda wrong here too.
There was a problem hiding this comment.
I've added a <span id=selectedcontent-disabled></span> here, which should work as an effective alias and no longer break links. Looks like this has been done in other places e.g. <h5 id="rel-alternate"><span id="link-type-alternate"></span> or <p id="structuredclone"><span id="structured-clone"></span>.
There was a problem hiding this comment.
I'd prefer not adding more markup.
I guess having read this diff a few times now I'm also kinda neutral on this change, towards the negative side. I find it more verbose and less clear.
69df3fc to
d0ad514
Compare
This fixes #12367 by renaming selectedcontent's
disabledboolean tois in valid tree position. The value now becomestruewhen selectedcontent is in a valid tree position, otherwise false. This is flipped from thedisabledboolean earlier, so all callsites have been flipped.This also renames the
select's enabled selectedcontenttoselect's selectedcontent in valid tree position, to better align that naming also./form-elements.html ( diff )