Perfecting the Grid Structure

[Paul_Wilkins]

@asasass

I need to catalogue all these different versions now.

Instead of having a catalogued library, I find that it’s more effective to think of it as an iterative process instead.

[asasass]

Code 1

Edit fiddle - JSFiddle - Code Playground

.wrape.inactive .nav {
  display: none;
}

no longer needed:
overflow: hidden;

---

Code 2

Edit fiddle - JSFiddle - Code Playground

.wrape {
  overflow: hidden;
}

.wrape.inactive a {
  display: none;
}

Code 3
https://jsfiddle.net/r8v3m1k1/359/

 function hideInitialOverlay(wrapper) {
    show(wrapper.querySelector(".nav"));
  }


  function initButton(selector) {
    hide(wrapper.querySelector(".nav"));
  }

No longer needed:

.wrape.inactive a {
  display: none;
}

overflow: hidden;

[asasass]

Should I care about Google Canary?
http://testing453453.blogspot.com/

[Mittineague]

@asasass

Should I care about Google Canary?

Nothing personal, but quite frankly for you during this stage of your progress, NO.

That browser is the unstable alpha release. Anyone using it will be used to seeing things broken and not think less of your code if it’s broken.

Canary is for devs that want to experiment with features that are not mature and may never survive. Even for experienced devs keeping up with unstable code can be a challenge and they need to be willing to scrap their work as moot at any time. IMHO better for you to concentrate on writing code that works in the more popular modern browsers and save worrying about edge cases and bleeding edge stuff until later.