While I have done this myself on my own blog by creating an override I am not sure it is suitable for every site. Plus I would be concerned that by applying this to an existing site you are changing the behaviour of that site.

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/3178.

Hello Brian! This issue is now a duplicate of this one:
http://issues.joomla.org/tracker/joomla-cms/4134 - closed

So apparently it't been changed already? There may be sites where it is not suitable, but I cannot think of one - would you have an example? Anyway, my point is that standard behaviour should be what's good for most cases, so only a minority needs overrides. Some people would even appreciate if the behaviour of their site changed. Others need to be taken into account, of course. Political decision?

Since this is a duplicate issue, I don't mind if you close it without further ado.

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/3178.

You stated my point. Standard behaviour should be what is good for most
cases. I don't believe this is. But more importantly it changes the
behaviour of existing sites and that is something we can not do
On 17 Oct 2014 07:48, "lausianne" notifications@github.com wrote:

Hello Brian! This issue is now a duplicate of this one:
http://issues.joomla.org/tracker/joomla-cms/4134 - closed

So apparently it't been changed already? There may be sites where it is
not suitable, but I cannot think of one - would you have an example?
Anyway, my point is that standard behaviour should be what's good for most
cases, so only a minority needs overrides. Some people would even
appreciate if the behaviour of their site changed. Others need to be taken
into account, of course. Political decision?

Since this is a duplicate issue, I don't mind if you close it without
further ado.

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/3178
http://issues.joomla.org/tracker/joomla-cms/3178.

—
Reply to this email directly or view it on GitHub
#3178 (comment).

Not worth starting a poll to find out, is it.
Changing existing sites: you mean something that has been bad (this or other issue) in the past can never be improved? Ever? Because it might change somebodies existing site? I should read Joomla's code of law someday ...

Consider this a welcome improvement for J4. It is not considered a bug and it would require people to change their site. Too bad, the consequence of a badly chosen default behavior.

If it is fixing an error then of course we can fix it but if the site is
working as intended then we cant change it. People wont like it if their
web site suddenly starts working differently after an update.

On 17 October 2014 09:18, sovainfo notifications@github.com wrote:

Consider this a welcome improvement for J4. It is not considered a bug and
it would require people to change their site. Too bad, the consequence of a
badly chosen default behavior.

—
Reply to this email directly or view it on GitHub
#3178 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Since #4134 is already merged into 3.4-dev. This one can be closed. Images will be linked by default starting with Joomla! 3.4.