CSS Penguin Step 75: the change is not visible on some browsers
See original GitHub issueDescribe the Issue
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.
Affected Page
Your code
.shirt {
font: bold 25px Helvetica, sans-serif;
}
.shirt div {
font-weight: initial;
}
Expected behavior
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.
Screenshots
System
- Device: Laptop
- OS: Windows 10
- Browser: Chrome (ver. 107.0.5304.106), Edge(ver. 107.0.1418.35), Firefox (ver. 106.0.5)
Additional context
No response
Issue Analytics
- State:
- Created 10 months ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Step 75 - Building a Penguin - HTML-CSS
Step 75 - Learn CSS Transforms by building a penguin. Having trouble with step 75, it's telling me: " If you look closely,...
Read more >FreeCodeCamp/Help - Gitter
The first argument to the function is the name of the custom property to be substituted. The second argument to the function, if...
Read more >RWD Beta: Transform Penguin: Steps 55, 82, 88 #44830
What the 3 steps have in common is that the editor has focus on the 1st line of the CSS file. All other...
Read more >Using CSS custom properties (variables) - MDN Web Docs
Custom properties (sometimes referred to as CSS variables or cascading variables) are entities defined by CSS authors that contain specific ...
Read more >FreeCodeCamp: Learn CSS Variables by Building a City Skyline
Your browser can't play this video. ... NEW 2022 | FreeCodeCamp: Learn CSS Variables by Building a City Skyline ... Show more. Show...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
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: https://bugs.chromium.org/p/chromium/issues/detail?id=1266022
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.