TYPO3 Core

I tested CUR for shotcuts (i put the front page into the main menu as a
shortcut) - no effect because this "page" type is just a link to the
actual page. I can however think that shorcut could have these states
as if duplicate related with the actual pages. In my mind Typo3 has a
bug because CUR doesn't work with shortcuts.

Today there are both link states and
document types - instead of speaking link "states" it would be much
better to speak about LINK BEHAVIOURS or MENU ITEM BEHAVIORS - because
all item types, which can be used in menues are not links.

Because external URL is out from site it is even impossible to think
for it ACT or CUR.

Because ACT and CUR are useless as link states for spacers (SPC),
shortcuts (SHORTCUT) and external URLs they need some kind of "pseudo-
states" (like in CSS there is pseudo-classes). The MAIN idea of ACT,
CUR etc. is just to give proper CONTROL for menu items - what means the
DESIRED BEHAVIOR regardless if we think about link states or document
types.

You have added SPC and USR for giving this control => it is FULLY
CONSISTENT to give FULL control by setting also EXTURL and SHORTCUT.

Because there is just partial control the existing system is
inconsitent. Document types, which need control should be listed in
link behaviors SCP
USR
EXTURL
SHORTCUT
MOUNTPOINT - new suggestion because MOUNTPOINT is a folder, which can't
have ACT and CUR states, because it might list the content of an entire
folder.

USERDEF1, USERDEF2 - necessary anything to do with link states - they
just give MORE CONTROL - they have the same task as existing SPC and
USR

IF you want full consistency then my request should be accepted.
Because the link "state" list is mixture of link states and document
types, it is difficult to get full consistency because what really is
the correct priority.

The class.tslib_menu.php have an exclude document type list. ALL which
is NOT in the exclude list, should be in the MENU ITEM BEHAVIOR list.

BTW. Lets speak about link behaviors - it is EXTREMELY confusing of speaking about link states, because the logic doesn't base only on link states.

I added those link states into class.tslib_menu.php
(issue imported from #M1128)