Bug in the answers checking algorithms?

Question

Ok that’s very irritating. I lost all my hearts on it.

HTML course, forms lesson.

The question is, which value of the type attribute is used for a password field?

I tried:
password
“password”
type=“password”

But in the result it always says “not quite” and takes my heart.

I don’t have a possibility to check it with AI, that’s why I am asking it here.

What is the correct answer???!

Whatever it is, it’s stupid and must be fixed, because ALL of the above mentioned variants ARE acceptable!!!

Answer 1

Danylo Dots did you by chance try

text

Or

"text" if the quotes are not available as ___

Yes, typically use
type= "password"
but by default
type= "text"
could be used.

Without being able to see the actual question and structure of the question

Answer 2

It’s not even fair, because in the lesson itself they say and give a code example where it is specifically stated that the password field has type of a “password”. Why on Earth should I answer “text” after that?

Answer 3

I agree.

I now had an opportunity to check what is the correct answer with a built-in AI.

And… What do you think?
The correct answer is:
<input type=“password”>

But it has no sense with the given question: what is THE VALUE OF THE ATTRIBUTE. The answer cannot contain the whole thing including the input tag itself, but the value only.

Even if this is the correct answer… They nevertheless should have included a “password” as a second correct answer as well.

Otherwise I lost my hearts “illegally”.

Answer 4

I just need the devs to see this and fix it.

Answer 5

It seems that there is a mismatch between the expected input and the checking system. It can be case sensitive validation or strict format. If all variants are technically correct but still rejected, it means that there is a bug or UX issue in the system. There should be debugging or clarification of the expected answer so that there is no misleading.