Do we really need the alias on this view. To me it is unnecessary clutter

This is another question ;) I don't need the alias and it is a point for a "backend light". But maybe SEO lovers have sophisticated aliases

The more Ithink about, the more Ilike the Idea of removing the alias, but really don't know when it is used. Maybe a condition: show the alias only if it is != default?

Yes, another use case for configurable list views. Personally for me the alias is important so I like to see it here.

@chmst Aliases are used for SEO friendly URLs, routing.

Alias on this view I think is essential.

• The ability to find if an alias is clean and matching a problematic URL is a key troubleshooting measure if there's been a copied article for example and that process has been missed.
• Identifying it as Alias I think is helpful for users.

Agree with new line, BUT the main problem is:

Same window size
3.x

in 4.x we have to reduce to ~80% to have a full reading.

I have tested this item ✅ successfully on dbc2aaa

With menu toggled it looks fine. In any case, we might hide the "alias" text?

In any case, we might hide the "alias" text?

I wrote the code for that but the code was not "clever" enough for some people to be accepted so I closed the Pr

I have tested this item ✅ successfully on dbc2aaa

by reducing Chrome, I have the result

Just because you talk about removing (the new culture) further informations. Why don't we give all these SPANs and DIVs individual CSS classes. Then you need 5, 6 lines of CSS to hide/show them and users can use a custom.css to override your decision; instead of PHP overrides, JS or whatever.

.

And we wouldn't need a ugly <br> for a new line but could use a display:block; or similiar whereever wanted.

@ReLater the div is a good idea, thank you for that, I will commit again.

Additionally - Joomla allows overrides, in backend as in frontend. So everyone can remove or add elements.

Additionally - Joomla allows overrides, in backend as in frontend. So everyone can remove or add elements.

Thats uglier that my suggestion ;)

@adj9 @carcam it woud be great if you could repeat the test. On the screen nothing has changed.

@ReLater @infograf768 @brianteeman in this PR I just wanted to improve the view. The other issues are real but out of scope here.

Isn't it better to remove the word in the Status section, leaving only the icon?
Or even like joomla 3, impoverish the Status and Featured section.

@chmst

it woud be great if you could repeat the test. On the screen nothing has changed.

the div is a good idea, thank you for that, I will commit again.

Should we retest or close this per and wait for the new one with the div? Latest seem better to me ;)

@carcam The change to div has been included into this PR here with the latest commit.

Great!! Will retest!! Thank you!!

I have tested this item ✅ successfully on a045a43

Tested successfully in Nightly Build of 24 May.

I have tested this item ✅ successfully on a045a43

I have retested and this PR address correctly the problem it tries to solve. It might be worthed to note that this issue is better experienced in big screens and solution works better for them.

In smaller screens the Title column is too narrow and it doesn't look that nice.

Before the patch

After the patch:

RTC

Thanks!