Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Height of blog cover is smaller on page 2 vs. on the homepage #99

Closed
hwdsl2 opened this issue Apr 21, 2014 · 1 comment
Closed

Height of blog cover is smaller on page 2 vs. on the homepage #99

hwdsl2 opened this issue Apr 21, 2014 · 1 comment

Comments

@hwdsl2
Copy link

hwdsl2 commented Apr 21, 2014

The height of blog cover is smaller on page 2, etc. compared to the homepage.

Screenshot of blog cover on homepage (in the latest Firefox):

bqxk3jj

Screenshot of blog cover on page 2:

hqeiujf

You can see a "live" version of this bug on my blog here. Please note that I tweaked the capser theme so that the blog cover height is 38% instead of 60%, but I checked and this does not affect the bug in any way.

Upon further investigation, I have found that on blog homepage, the html source contains:

<body class="home-template">

But on page 2, page 3, etc., the html source contains this instead:

<body class="archive-template">

If you look in "content/themes/casper/assets/css/screen.css", search for "archive-template" yields the following:

.archive-template .site-head {
    height: auto; 
    padding-bottom: 5rem;
}

Note that the height is "auto". If you look at the main theme section, however, you will see:

.site-head {
    position: relative;
    display: table;
    width: 100%;
    height: 60%; 
    ... ...
}

And you see the height is "60%" here. This explains why the blog cover is much less in height on page 2. Is this "by design"? Or is the "archive-template" incorrectly used on page 2, etc.?

Thank you for looking into this.
@JohnONolan
Copy link
Member

This was resolved in 8a2edd6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohnONolan @hwdsl2