Am I missing something here. If the site owner sets password criteria then surely they will no longer be part of the strength meter

This is for the installation setup only.

Updated test instructions to clarify.

Yes but the javascript is the same javascript used for all password fields

Updating the minimum length value that was missed in PR #29859. The javascript will work fine as before.

This implements nicely the meter in installation.
We can't expect preventing going to the next page as, alas, this is a unique page, contrary to 3.x...

One small drawback is that the meter does not show a result when the field is automatically filled by the browser.

If that can be solved in the js, would be great, otherwise I will mark my test OK.

Note:

Independent from this PR
Frontend registration needs a lot of care as the meter is not present (if added needs also the meter class) and strings are not even translated.

If meter added

Can be done after this is merged.

Hello everyone, I am testing # 30424. The graph is displayed correctly, but it is in green from 9 characters. While one has an instruction of 12?

Confirmed. I starts getting green at 8 characters

I think this comes from

const meter = document.createElement('meter');
      meter.setAttribute('id', `progress-${index}`);
      meter.setAttribute('min', 0);
      meter.setAttribute('max', 100);
      meter.setAttribute('low', 40);
      meter.setAttribute('high', 60);
      meter.setAttribute('optimum', 80);
      meter.value = initialVal;

I tried to add attributes to the setup.xml password field as it would work if we had
optimum="100" low="100" high="0"

but it looks like the js does not include fetching such attributes from the field.

This is why I commented about the removal of certain lines in the javascript

Not sure the lines deleted deal with the bar itself. They deal with the message below.

One small drawback is that the meter does not show a result when the field is automatically filled by the browser.

The password field has autocomplete="new-password" attribute which should prevent auto filling by the browser. If it is fixable in the js, then let's do it in a separate PR.

The password field has autocomplete="new-password" attribute which should prevent auto filling by the browser. If it is fixable in the js, then let's do it in a separate PR.

Sure. To describe better: Firefox stores passwords and when clicking in the field, it displays a dropdown with possible passwords, letting the user choose among them. if one is clicked then it is entered in the field and we have the result above. To really use the meter, one has to enter character per character in the field.
Not a very big deal imho.

@C-Lodder Can you please confirm that the meter is a strength meter and not a progress meter so it is ok to be green 3/4 of the way? Thanks.

@Quy can you test this:
change

   meter.setAttribute('optimum', 80);

to

   meter.setAttribute('optimum', 100);

Does it solve the green appearing before 100? (it should)

@dgrammatiko Same result.

@Quy The colour of the meter will is determined by the low, high and optimum attribute values.

If:

• min is 0
• max is 100
• optimum is 15

Then the meter will become green at 15

Changing high and optimum values yield the desired result. Thank you both.

I have tested this item ✅ successfully on d2b1f3a

Also tested backend and it looks like working fine.

Everything is working fine. During the installation as during the creation of a user in the backend. But shouldn't this also be the case when registering in the frontend?

@Magnytu2
see
#30424 (comment)

We will make patch as soon as this is merged

If this PR works for you (it is limited to installation and solves the js generally speaking), please test it OK here:
https://issues.joomla.org/tracker/joomla-cms/30424

I have tested this item ✅ successfully on d2b1f3a

Everything is working fine. During the installation as during the creation of a user in the backend.

RTC

Cassiopea implementation is here to test
#30437