All Joomla-Versions after Joomla! 3.8.0-rc1

With PR #14802 in 3.8.0-rc1 come alternative layout parameter to com_content menutypes

Steps to reproduce the issue

Protostar is Default-Template.

1. Create an alternate layout for articles in the Protostar-Template and name it menutypelayout.php - for example add into the headline of this alternate layout for articles "This is the Alternate Article Layout set in Menutype"

2. Setup a Testcategory with at least Testarticle 1 and Testarticle 2

3. Create a Menuitem with Testcategory Blog View, Select menutypelayout as alternate Layout in the Options tab (Choose a Layout). In the Details Tab is Template Style: protostar-Default

4. Go to frontend and click to menuitem you have created at 3.

5. Click in frontend on Testarticle 1 or Testarticle 2

Now the articles Testarticle 1 and 2 are shown correct in the assigned menutypelayout Layout in frontend(single-article-view).

But if you now change in the Menuitem to an other TemplateStyle(for example from Protostar to Beez)
Menuitem with Testcategory Blog View -> Details -> Template Style -> Beez3-Default
and save it with one click on the Save-Button.

Then works the menutypelayout furthermore with the Beez-Template
But you dont see this in the Menuitem at:
Menuitem with Testcategory Blog View -> Options -> Choose a Layout

If you now save it again then is come the displayed result(view without the alternate Layout from the other Template).
Save it twice after change to an other Template Style then you have always the correct "view".

Similar the same problem as in the PR #16755 and #8578
comes from the same bug.

System information (as much as possible)

All Joomla-Versions after:
Joomla! 3.8.0-rc1
also for Example 3.8.3-dev

Additional comments

shamsbd71 in PR#16755 30.Juni:

I have tested as you asked and yes there is an issue but its not related to this xml params. its relate to
filed type componentlayout.

mbabker in PR#16755 30.Juni:

That layout parameter should save with a value like "template_name:layout_name" when saved to the database, and when used in the PHP API, that template name segment gets parsed by the view class to figure out that it needs to change the active template.

If that logic is broken, it will be a bug that already exists and would need to be addressed separately from adding this field.