Should <selectedcontent> match :disabled?

[emilio]

Right now <selectedcontent> has an internal disabled flag: https://html.spec.whatwg.org/#the-selectedcontent-element:~:text=Every%20selectedcontent%20element%20has%20a%20boolean%20disabled%2C%20which%20is%20initially%20false

That's a bit confusing because there's already a "global" disabled flag for form controls which is :disabled / :enabled. Should it match those? Can we call it something else?

This came from a gecko review where it's very weird that IsDisabled() on a <selectedcontent> element would do something different than on any other element. But I guess it's not a huge deal?

cc @josepharhar @annevk

[josepharhar]

I dont think it should match :enabled or :disabled because this disabled state is just for preventing more issues when the author puts the selectedcontent element in a place that its not supposed to be, unlike form controls which have a disabled attribute which is an actual use case

[emilio]

I can live with that, but maybe we should call it something else then? It makes our code rather confusing. Though I guess we have overloaded terms in other places :)

[josepharhar]

I'm fine with changing the name. Do you have any suggestions?

[emilio]

So it seems a <selectedcontent> is not disabled iff it's in a valid position in the tree right? (I.e., under a <select> element and not under another <selectedcontent> or <option>).

Maybe "in valid tree position", or so?

[annevk]

Betteridge's law of headlines applies.

I suppose I don't mind another renaming, as long as it's clear.

[keithamus]

"in valid tree position" seems to make sense, and conceptually can carry over to other elements without conflict if we need to borrow the concept in future.