Change:
The instruction starts with: If you look closely, the heart emoji is slightly different. I can see the purple heart has become slightly bigger in Firefox. However, I can't see the difference in Chrome or Edge. We can change the first sentence to: In some browsers, the heart emoji may look slightly larger. (I changed "different" to "larger", so that campers don't have to spend too much time looking for the difference) And the last sentence to: To make it consistent on different browsers, target the div with the heart emoji, and set its font-weight to its original value. https://user- Device: Laptop OS: Windows 10 Browser: Chrome (ver. 107.0.5304.106), Edge(ver. 107.0.1418.35), Firefox (ver. 106.0.5) No response
The difference is not always the size, though. I am unable to reproduce a change in Chrome, but when I was making this, the heart would get a hashed pattern inside. There is a chance Google has changed something. As such, I suggest we keep the use of "different", and go with:
when I was making this, the heart would get a hashed pattern inside. Actually, this information was what I would have wanted as a learner. When I learn coding, I always check what kind of change the code I wrote makes to deepen my understanding. So if my browser doesn't show the difference, I would want to know what kind of difference it is. How about: The heart emoji may look slightly different. The size, color, or nothing changes, depending on your browser.
I think that is too much useless information. We specifically removed information here:
Personally, I don't think so. For example, if you see a forum post saying "The emoji on my page looks different. How can I fix it?" then I guess you would want to ask how different it is. That's what I'm feeling here. However, it seems like losing color was a Chrome's bug: So I think it's okay to forget about colors. I even think it's okay to remove this step if we can allow that slight change in size.
I played with this for a bit and I really don't have a preference here. Most of instructional suggestions sound good to me - removing the step sounds good as well.
I believe both the browser and operating system determine how emotes are rendered.
OK, how about: In some browsers, the heart emoji may look slightly different from the previous step. This way campers can at least know that the "difference" is something caused by what they have done in the previous step, and not that something like they have used wrong emoji (that was my first guess).
Is this up for contribution ?
The "a hashed pattern inside" of heart that mentioned (and I also noticed this a few months ago when translating this step) can be reproduced using the , as shown below. ! We can also think that the STEP 75 imparted knowledge to the learner to control emoji colors (albeit in a different way). Therefore, how about adding the following steps: to add (this may be step 75) font-family: 'Noto Emoji' to the to see the emoji color change (this may be step 76) the lines in the above two steps, then resume the current step 76 procedure (this may be step 77)
I don't see the need to add steps that import and remove a font for this. I'd much rather stick with adding the note "In some browsers, the heart emoji may look slightly different from the previous step." so that we can focus on the concepts this project is actually trying to teach.

Discussion:
# --description-- <del> If you look closely, the _heart_ emoji is slightly different. This is because some of the character's properties were overridden by the `font-weight` style of `bold`. </del> <ins> In some browsers, the _heart_ emoji may look slightly different from the previous step. This is because some of the character's properties were overridden by the `font-weight` style of `bold`. </ins> Fix this, by targeting the `div` with the heart emoji, and setting its `font-weight` to its original value.