Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
  • Feb 01 00:27
    @bjorno43 banned @Ndoua
  • Jan 07 03:10
    @bjorno43 banned @doctor-sam
  • Aug 17 2019 09:32
    User @bjorno43 unbanned @linkin-park
  • Jun 20 2019 21:19
    @bjorno43 banned @shenerd140
  • Apr 25 2019 17:13
    @mstellaluna banned @cmal
  • Jan 08 2019 22:05
    @mstellaluna banned @dertiuss323
  • Nov 07 2018 04:42
    User @texas2010 unbanned @ows-ali
  • Nov 02 2018 16:25
    @texas2010 banned @ows-ali
  • Oct 12 2018 05:50
    @bjorno43 banned @NACH74
  • Oct 05 2018 23:02
    @mstellaluna banned @JomoPipi
  • Sep 16 2018 12:21
    @bjorno43 banned @yash-kedia
  • Sep 16 2018 12:16
    @bjorno43 banned @vnikifirov
  • Sep 05 2018 08:12
    User @bjorno43 unbanned @androuino
  • Sep 05 2018 07:38
    @bjorno43 banned @androuino
  • Aug 23 2018 16:57
    User @bjorno43 unbanned @rahuldkjain
  • Aug 23 2018 16:23
    @bjorno43 banned @rahuldkjain
  • Jul 29 2018 14:13
    User @bjorno43 unbanned @jkyereh
  • Jul 29 2018 01:00
    @bjorno43 banned @jkyereh
  • Jul 10 2018 22:09
    @bjorno43 banned @manafn
  • Jul 06 2018 15:20
    @texas2010 banned @imlegend19
AJ Brommy
I feel we could both learn something here. If we could solve it. However there could be a temporary solution. If you did use another media query for min-wdht 600 and maxiwdth 725px you could shrink the left hand menu a bit. But that's not a real solution.
No worries mate. Sorry I couldn't help more, I'll tag @newmoon as is usually pretty good, quick, and helpful. Maybe @newmoon will read this and find the problem for you when the one finds time :)
AJ Brommy
@bradley1492 just so you know, I just did a shrink of the web browser on FCC version and it changed to mobile view about 815px. Which changes yours to do the same does defeat the problem. Not that it helps us understand the real problem. But it could a solution.
hm I think another media queri is a bit too hacky for me,
oh you mean set media query to 815px?
I'll try
I already did that sort of thing once
Originally the media query was 480px and I already bumped it up because of that Issue ^^
AJ Brommy
by the way
There is only supposed to be one <header>
<h1>to<h6> should be used
i think
I think in theory there should be only one but if I switch I think the test will fail
I'll look into the example
yes they also use a bunch of headers
AJ Brommy
ah ok - yeah i was just looking, i could be wrong again. lead to believe one thing, but not got the whole truth. i am now unclear.
https://www.w3schools.com/html/html5_semantic_elements.asp says <header> Specifies a header for a document or section. you have 1 per section, so by that definition it is fine
ah ok
AJ Brommy
sorry i should have checked theirs to lol
I think the whole sectioning thing is fairly new
AJ Brommy
yeah html5
alright I'll be gone for now thanks for your help!! :)
@br3ntor The functionality is part of emmet, with VS Code by default. Go to preferences -> keyboard shortcuts and search for increment and decrement to map the commands to ctrl+ :arrow_up: / :arrow_down: https://github.com/Microsoft/vscode/issues/3776#issuecomment-372664006
If it's the issue with the scroll bar appearing, it's because of your <code> content not wrapping.
The word-break property on your <code> elements will fix it: https://www.w3schools.com/cssref/css3_pr_word-break.asp
@bradley1492 @AJ-Brommy :arrow_up: :arrow_up: :arrow_up:
To debug overflow issues, I do:
* {
  border: 1px solid black;
AJ Brommy
lol - I literally just found it!! I saw newmoon talking and stayed away as I wanted to solve it. Gutted we didn't solve it first haha. Well done newmoon I knew you would have the answer. I did check for such a thing earlier but must have missed it. I literally took out all the content putting it back in one tag at a time and then found it. Feels good that I found it tho.
Uncanny I do the same, but i use a red border #f00; :D
how do you include a pic like that?
you have to upload it somewhere first?
yeah i see now that because there is no spaces it makes it one long word and the default doesn't break words so it breaks out the box so to speak
I still haven't finished my tribute page lol.. I should finish up!
@AJ-Brommy I think :point_up: this comment got lost yesterday :)
To add the image, I use a screen clip tool - select a portion of your screen and it goes to your clipboard. Paste in chat after that
AJ Brommy
Just paste :O wow
Opera Snapshot_2018-08-23_003725_codepen.io.png
I tried drag and drop instead - worked! coolness
Hahahahaha oh dear... you already solved yesterday!! Oh well - all good fun. I definitely learned!
I now need to go back and find the help you gave me!! lol
By the way @newmoon on the FCC version of that project they did <a><li></li></a> and apparently throws the test out if its <li><a></a></li>!!!!
@AJ-Brommy That should be bug in their HTML :) but the tests seem to pass for me with <li> as the direct child: https://codepen.io/anon/pen/rZVGWj?editors=1010
That's a fork of https://codepen.io/freeCodeCamp/pen/NdrKKL?editors=1000 with the <a><li> switched around
AJ Brommy
Seems you are right :D
So going back to my Tribute issue with the padding/margin thing. Should I use *{}?

I used to do that and default things to 0. But when I read:

"// PLEASE NOTE: Adding global style rules using the selector, or by adding rules to body {..} or html {..}, or to all elements within body or html, i.e. h1 {..}, has the potential to pollute the test suite's CSS. Try adding: { color: red }, for a quick example!"

I avoided doing so. However, reading it again, I think I miss read and panic'd lol, it's just a warning to be careful with the testing.

I don't think that will help out with the collapsing margins
AJ Brommy
no? oh