If I could upload a .zip file I would provide this fix for you, since I can't you can locate the issue here

Try a pull request! So, anybody is able to test your code changes.
Here's a description:
https://docs.joomla.org/Using_the_Github_UI_to_Make_Pull_Requests

Thanks Bertmert. Thinking about it, this change may require a change to the standard Joomla! template too. I will test that and do two pull requests if need be.

@uglyeoin Any progress on this issue?

I agree on the issue. But indeed this would require an override for Protostar and may change some templates display which do not use an override. Enough to qualify as not B/C, that is the question.

I don't know @infograf768 I'm kind of a noob to this stuff. @wilsonge can you provide information as to whether this is considered breaking b/c? It is more likely to be templates that suffer than extensions (although not completely impossible). I would be happy to submit a pull request for the core as well as any template changes for Protostar. Is it possible to submit both?

I think it's fine to do. I'd just push it into 3.5 to be safe.

@wilsonge Just to avoid additional work, Protostar will remain in J3.5?

Yes

Ok I'll try to understand a pull request and submit one today

ty!

@uglyeoin https://docs.joomla.org/Using_the_Github_UI_to_Make_Pull_Requests - ping me If you need help

@wojsmol Thanks, I assume by ping you mean just @you ??

@uglyeoin yes

@wojsmol many thanks, I'll see how I go (expect me to ask for help lol)

Here are my pull requests:

Joomla! Core (breadcrumbs module)
#8929

Joomla! Core (protostar template)
#8930

@wojsmol I can't believe how easy that was!

@bertmert thanks for the link it was very useful

@wojsmol you might want to check I did everything correctly at my end :)

PR in itself looks fine to me (haven't checked it actually works)

@wilsonge cheers for checking the PR. There goes the PR virginity. Whoop whoop.

For #8930 I am not sure the way to go is modifying the css. I am more in favour of an override.

@infograf768 can you explain why you prefer an override to a less/css change? I don't mind either way it's about the same amount of work and so long as it all works at the end I am happy. I would however, prefer to do things the right way and learn for the future, anything you can do to assist is greatly appreciated.

The way I see it the override uses more files, larger files and therefore, makes the Joomla! core larger, I think adding a few characters to a less/css file is an improvement on this. Granted it is not a huge overhead but if everyone has the same attitude Joomla! will remain as light as possible.

Closed as issue was resolved with PR