Missing h2 element. about freecodecamp HOT 9 CLOSED

@Stephen-254 why are you still using iPhone 6? Its very old device. Is it even still getting updates btw?

from freecodecamp.

@MrSuddenJoy I am not using an iPhone, I forgot to edit the system info section. I am using a Samsung device equipped with the latest updates. My apologies.

from freecodecamp.

Hi @Stephen-254, thank you for reporting the issue.

The correct version should be:

and the output element with the id result and store it in a variable called result.

This change was made in #55022, so we'll just need to wait for the next deployment.

I'm closing the PR as the issue has been resolved.

from freecodecamp.

@Stephen-254 OK OK :) BTW: Im heavy user of iPhones (currently iPhone 12; also updated).

from freecodecamp.

I have only used an iPhone once, the iPhone 4, I did not like the experience at the time. I had to jailbreak it to access some features and applications. But with the current great technological advancement of the iPhone, I am always tempted to switch. Its UX and UI are so good.

from freecodecamp.

I am always tempted to switch

@Stephen-254 than just go for it; you will not regret it 👍🏻

Its UX and UI are so good.

Agreed. In part thats because you have full consistency there. Very well seen if you have multiple Apple devices (say iPhone + MacBook). Switching them, and continuing work on the other, is never seen on, even best (top) devices with Android.

This consistency in UX is main reason of high prices of Apple devices IMO.

from freecodecamp.

At first, I thought that we should only change h2 in the challenge to output.

But, since the output element isn't inside any form element and there isn't any form element either, I think we should change the output element to h2 as mentioned and remove the for attribute then.

from freecodecamp.

At first, I thought that we should only change h2 in the challenge to output.

But, since the output element isn't inside any form element and there isn't any form element either, I think we should change the output element to h2 as mentioned and remove the for attribute then.

What to change will be determined by the next steps, we might change the output to h2 and then find out that the rest of the steps are using an output and vice versa.

from freecodecamp.

Hi @Stephen-254, thank you for reporting the issue.

The correct version should be:

and the output element with the id result and store it in a variable called result.

This change was made in #55022, so we'll just need to wait for the next deployment.

I'm closing the PR as the issue has been resolved.

Thank you, Huyen.

from freecodecamp.