TYPO3 Core

This is true, Bjoern. It looks it has always been like that, in 3.8.x, 4.0.x and in content(default) and css_styled_content.

While it seems like a "missing feature", we need to take care to keep the behaviour backwards compatible, if we change this in the core (css_styled_content and content(default) ).

Hm, what does that mean?

I know BC is one of TYPO3's goals but to set a starting point without a corresponding result is IMHO not a behaviour that needs to be saved.

Hopefully this won't lead into another impasse like in http://bugs.typo3.org/view.php?id=2842

Hi Ernesto!

And this one would be nice for 4.1 :-)

Hi Ernesto!

Will you take care that this enhancement will be a part of the upcoming 4.1?

Regards
Bjoern Kraus

have a look to my patch in #8939 (and in core list)
It's much more simple

Steffen: your patch is one line "smaller", but it is not "more simple". It is indeed more complex, because copying all .default settings we have to make sure we are not copying stuff that we don't want to (backwards compatibility), e.g. stdWraps, wraps, etc.

But as far as I could see, this has no different effect, because all wraps are substutited by "correct ones" in the .2 section, so I am ok with that patch.

Correction: sitemap does not display the whole tree, it displays all pages within current web site. In other words, it shows all pages starting from a page with root TS template. I think this behavior is correct. For your purposes you should use "Menu of subpages to these pages". It does exactly what you want.

Sorry to say this but this bug is a false one.

I consider that too, as i was misleaded too. Thx Dmitry for knocking our heads.
I will close this issue and prepare a new patch for the sitemap as discussed here
http://support.typo3.org/teams/core/m/re-typo3-core-rfc-8939-menu-sitemap-doesnt-respect-pages-field-352978/p/98/