Question: I'm trying to build a generic alert element, that changes according to the parent div's height. At first, when I just designed everything, I used specific heights, but now I want to make it all relative, and for some reason those are calculated wrong!

so say this is my html:

```
<div class="alert">
    <span class="divider-vertical"></span>
</div>

```

and my css used to be:

```
.alert {
    height: 80px;
} 

.divider-vertical {
    height: 30px;
    margin: 25px 0; // 25*2 + 30 = 80
}

```

Now I wanted to turn this into relative percentages, so:

```
<div style="height: 80px;">
  <div class="alert">
    <span class="divider-vertical"></span>
  </div>
</div>

```

and my css:

```
.alert {
    height: 100%;
}

.divider-vertical {
    height: 37.5%;
    margin: 25px 0;
}

```

I used that figure based on the calculation: `100 * (30.0 / 80.0) = 37.5`. Now when I opened up chrome and checked to see the `computed` attributes, I found that `.alert` has a height of `80px` (as it should), **but `.divider-vertical` has only `29.25px`**. Why is that? 

There's no other conflicting attribute somewhere else and the chrome dev tools assure me that the elements height is indeed 37.5%. Notice this isn't a case of some infinite decimal number, the calculation returns *exactly* 37.5% so why would there be any trouble here?

Answer: 
No, the availability determines when the app will be available. If the date is in the past, it means that the app will be visible on the AppStore.
With more explanation... There's no need to manage an availability date and it is separate than the review submission process and only is considered once approval is granted for the app to be sold.

If your date is in the future, it will sit and wait to go on sale when that future data arrives.

If your date is in the past, it will go on sale as soon as approval is processed and the store can update the database.