Ahhh, that's what you meant.

Thanks for the hint, I'll change.

i was addressing the hard-coded link associated with your button, not the button.

Proceed through the following workflow...
Step 1 starting at the newsfeed page:

Step 2 being forwarded to the message box of Botox:

That is, your "Back" button won't take you back where you've been before in this case, but to a different page. Thus 'Back' is irritating here and 'Close' a better label to my opinion,

What do you mean?

The name is not hard-coded, it's translatable?

I'm confused what do you mean?

No doubt, this feature makes sense. I'm just a little unhappy with naming the button 'Back' and hard-coding it to messages/all. Because that's not necessarily the location where you've been before. That why my idea would be to use a 'Close' icon instead next to the trash can.

I mean, when you get a message and you click on it then you get directly to the chat, but if you want to go back to your message overview (where you can see all your chats) then you have to click on the message icon and then on "see all"

With this component you can go directly to the overview without a second more click

You wrote 'there's no way back', thus you must have been there before, so how did you get there?

What do you mean with ?

Just wondering which way you were able to initially enter Test123?

And thanks

Ah yes. ;)
Just wondering which way you were able to initially enter Test123?

And: Inside of javascripts you may simply use
Ossn.Print('some:key:to:translate', [arg1, arg2, argn]);
no need to call PHP
see system/plugins/default/javascripts/libraries/ossn.lib.languages.php