@alikon Hey Nicola, works fine, but there are some small issues i found so far:

The tooltip text: Type in the textbox what you see in the image is not really matching for Recaptcha version 2 (where you don't fill out text boxes, but click images).

Some code style issues (see comments).

Thank you!

A couple of issues:
1. If I fail the captcha the page reloads but all the form field entries are lost.
2. Perhaps move the captcha field to the end of the form?

@yvesh

The tooltip text: Type in the textbox what you see in the image is not really matching for Recaptcha version

is like com_contact what should be the correct STRING ?

@chrisdavenport

1. Perhaps move the captcha field to the end of the form?

not sure should be better near the submit button ?

1. If I fail the captcha the page reloads but all the form field entries are lost.

any help ?

@alikon Not sure on the text. Something more generic maybe, which fits both.

For example: Please answer the security question. But i am not a native speaker. @chrisdavenport What do you think?

If I fail the captcha the page reloads but all the form field entries are lost.

any help ?

This is not going to be implemented easily. For com_users the data the user entered during registration is saved in the session and then loaded again.

See this code as an example.

I checked with the en-GB team and because "I'm not a robot" is not a question, the suggested text is "Please complete the security check." There is a PR in the CMS repo for the same text: joomla/joomla-cms#10931

Good point about the submit buttons. Actually, I think the buttons should be moved to the end too. See, for example, the contact form.

Should be fairly simple to save the form data in the session as per com_users and also com_contact.

• session form data
• captcha & buttons moved down ....

I have tested this item ✅ successfully on d6a18f8

Works perfectly and looks good. Thanks Nicola. ?

there is the need to add the lang string to the joomla-cms repo too ?
joomla/joomla-cms#10895 (comment)

@alikon There is a slight css issue for me:

Imo it's not completely related to your PR, even the

Everything else works as expected, great work Nicola!

@yvesh css is not my "comfort zone"

any help to fix CSS issue ?

...it happens only when editor is CodeMirror...

@alikon it also happens without an editor. But you are right with TinyMCE it's fine.. Probably something which should be fixed in core (the row with buttons need to have width: 100% for the editor line, so there is no free space right of it).

We could fix it for weblinks with the following css:

#editor-xtd-buttons {
   width: 100%
}

@chrisdavenport What do you think? Core problem or weblinks?

@alikon @yvesh how about: joomla/joomla-cms#10970

maybe @dgt41 can evaluate my dirty fix on https://github.com/joomla/joomla-cms/blob/staging/templates/protostar/css/template.css#L2609
from

.btn-toolbar {
    font-size: 0;
    margin-top: 9px;
    margin-bottom: 9px;
}

to

.btn-toolbar {
    font-size: 0;
    margin-top: 9px;
    margin-bottom: 9px;
        width: 100%;
}

results is clean now, i think...

but i don't know if it is a goog fix .....

@alikon looks fine for me, but not sure if that would cause other issues though. You could also just remove the pull-left class the editor-xtd-buttons div has. Not sure why that is there at all?

Is there a case were there is something located right to it on the same line?

// cc @dgt41

Any objections to merging this now?

For my knowledge of CSS the issue we have should be fixed on the CMS CSS side
We are waiting for some CSS expert answer which should be the right fix mine or Yves or ...
Evoking @dgt41

@alikon The branch now has conflicts (Probably due to Tobias changes related to code style).

I think we can merge this PR. The CSS layout problem is a minor one and only occurs when you have no editor or CodeMirror. We should open an issue at core for that. The css code from Nicola looks fine, but i am not sure if it has side effects.

yes please merge this PR

p.s.
cause i'm unable to find the latest damned branch conflicts ?

This PR has received new commits.

CC: @chrisdavenport

@alikon i sent you an PR against your one, merging current master changes into it. (Test please)

Okay conflicts resolved. @chrisdavenport you can merge now.

thanks 1000 @yvesh

This PR has received new commits.

CC: @chrisdavenport

Merging. Good work everyone. :-)