cc @crystalenka @coolcat-creations @angieradtke JXT members

I support option 1, because style=none is useful in some cases. But I agree the default should be one that supports all the options available in the module parameters.

This should be a relatively quick fix, but may break some templates/overrides/sites because the output is different (which is part of the problem). If someone styled a site based on the style=none modules, it may not work if the default style changes.

@bembelimen I can open a PR for this, but would it be a breaking change? If so, how big of a breaking change? Seems silly to wait for J5, but it is a frustration. Would it be possible to set the default for new installations without breaking existing sites, or something?

One of the problems is that when you create a new module show title is set to yes
So if the template is changed from "none" to "html5" then the titles will magically appear on all sites

if I set it to html5 another problem appears: the header tag is nested and twice:

Edit: Sorry :-) LOL it was because I placed it into the header...

I think it would be nice to have "cards" for the different Chrome Styles and display them with a preview of what the user can expect. Something like small wireframes. I could draw them if there is interest in that. But we would need a feature to attach a svg icon to preview the different styles.

My only concerns right now is

1. module options dont work and almost no one knows why

My only concerns right now is

1. module options dont work and almost no one knows why

I agree. Also for example the Bootstrap size does not work for anything as far as I am concerned. Correct me if I am wrong.

Can we check if the chrome is using title or setting at all and if not display a warnung below the setting?

Can we check if the chrome is using title or setting at all and if not display a warnung below the setting?

no. because we dont actually know what chrome is being used. the module only knows it is using "inherited"

But inherited from what is a big question. From the template? then it has to check the template. But I fear thats quite impossible...

Well, It not something new, it expected behavior. Probably since we have "chrome" style. Most of "joomlers" aware about it.
Yes, I understand it looks unintuitive for beginners, and may confuse.

Well, It not something new, it expected behavior. Probably since we have "chrome" style. Most of "joomlers" aware about it.
Yes, I understand it looks unintuitive for beginners, and may confuse.

It is not expected behavior that the default chrome will not actually respect any of the module settings. Also, in Joomla 3, the default was html (I believe) so it worked as expected.

It may not be new, but that doesn't mean we can't make it better.

@Fedik thats not really an argument for leaving it like that if most of the current users (how many?) get along with it. Let's try to find a solution that also onboards not experienced users and new users... :-)

If we know to which menu items the module is assigned to, we can find out which template styles it is using.
It can even be it's using a lot of different template styles.

Through the template style we can find out what chrome is used / what chromes are used.
The settings could then maybe appear depending on which of the chromes are active?

My only concerns right now is

1. module options dont work and almost no one knows why

I agree. Also for example the Bootstrap size does not work for anything as far as I am concerned. Correct me if I am wrong.

I think you are right, as far as Cassiopeia is concerned. But if Cassiopeia will be the Bootstrap template going forward, perhaps the issue is that the template doesn't do anything with them.

I think by default it should be, that all parameters work as desired. So html5 should be default, also in Cassiopeia.

Maybe it needs an additional helptext that this setting is also affected by the used template.

I thinks icons @coolcat-creations are helpful , but if the style is affected by the template, we don't know how the module will be renderd. As a developer I don't want to go without "none". This allows me clean code.

It is not expected behavior that the default chrome will not actually respect any of the module settings. Also, in Joomla 3, the default was html (I believe) so it worked as expected.

This kind of template design flaw, it would need something different than style="none" by default, I not sure we can change it for Cassiopeia.
Joomla 3 also have multiple default positions set to none.

It may not be new, but that doesn't mean we can't make it better.

I did not say we can't do better, I just remind that it not a new, and how whole crome thing works ?
By "chrome" API design it expected behavior.

If we know to which menu items the module is assigned to, we can find out which template styles it is using.
It can even be it's using a lot of different template styles.

And what about "render module" plugin? ?

The icons would be wireframes provided by the chromes. No specific stying but an idea for the user how the structure looks like.

@coolcat-creations yeah, maybe drop "inherit" and use "html5" (as default) not a bad idea, in result it will be more obvious what is going on.
In theory.

I would not drop inherit. Inherit means it uses the template style so if I have 5 Styles I can define which style is used in each of the templates instead creating 5 Modules.
But it would be good to pass the information back to the module which styles are being used.
Normally only one - but sometimes there could be more styles in use.

Well, It not something new, it expected behavior. Probably since we have "chrome" style. Most of "joomlers" aware about it. Yes, I understand it looks unintuitive for beginners, and may confuse.

what is new is that the chrome doesnt support the module options

what is new is that the chrome doesnt support the module options

Try the same test for joomla 3, for position position-0, position-1, position-2.
You will get the same result.
Position with style none does not customisable by design.

A simple solution would be: set a default layout "html5" for some positions in the template index.php where protostar had the default value "xhtml".

I think it make sense to link this issue:

• #20864

I thought they were ported to layouts already?

yes it is, but that not all ?
In linked PR #23570 was discussion about allowing XML for chrome style, so each chrome would have own config fields.

oh, and that already should be possible since 4.1 #23577