Proposal: <more> element about html HOT 3 CLOSED

Question from the sideline, how would “more” enhance semantics, or be clear(er)? It seems to be applicable to anything, which is typical for something that can represent everything, like a div or span.

For the problem itself, as element semantics have something permanent (a paragraph, heading, image, or other element doesn’t usually change form), and this seems to be about solving something temporary (what was “more” at time A doesn’t seem to be “more” anymore at time B), an element may not be a suitable choice, either. But that’s also a humble sideline read.

from html.

Please use the "New feature" template for this instead and address the various questions it raises.

from html.

Question from the sideline, how would “more” enhance semantics, or be clear(er)? It seems to be applicable to anything, which is typical for something that can represent everything, like a div or span.

For the problem itself, as element semantics have something permanent (a paragraph, heading, image, or other element doesn’t usually change form), and this seems to be about solving something temporary (what was “more” at time A doesn’t seem to be “more” anymore at time B), an element may not be a suitable choice, either. But that’s also a humble sideline read.

more is typically intended to be used in more specific elements like <ul>, <menu>, <article>. div and span is not primary concern.
Why is this? Because the content model limitation:
Consider in some cases, if we don't have <more> in <li>, since <li> can only be used inside <ul>, <ol> and <menu>. If we want to express the <ul> collapses some more items. We have to end up writing some code like this:

<ul>
    <li>...</li>
    <li>...</li>
    <li>...</li>
    <li class="clickable">more</li>
</ul>

You can see that semantically the last item is not of the same conceptual level as the others.

from html.