Change Details

I noticed that this commit 9448e815721c882196b8c541560270734574af8e introduced a problem in Phame: {F2925793,size=full} (I've identified the problematic commit using `git bisect` starting with a good old commit `git bisect good e5d7c9aa4e0be14427bac27c079c57f79d3b7ef3` and `git bisect bad 42234d56e5a4bd7d053d85a482b05c5f90b6ef36` that is the last change in origin/master)

I noticed that this commit 9448e815721c882196b8c541560270734574af8e introduced a problem in the homepage of Phame: http://phorge.localhost/phame/ {F2925793,size=full} This happens exactly after `1792` pixel width screen. Does __not__ happen at `1791` pixel width screen. This happens only if you have not any posts. (I've identified the problematic commit using `git bisect` starting with a good old commit `git bisect good e5d7c9aa4e0be14427bac27c079c57f79d3b7ef3` and `git bisect bad 42234d56e5a4bd7d053d85a482b05c5f90b6ef36` that is the last change in origin/master)

I noticed that this commit 9448e815721c882196b8c541560270734574af8e introduced a problem in the homepage of Phame:: http://phorge.localhost/phame/ {F2925793,size=full} This happens exactly after `1792` pixel width screen. Does __not__ happen at `1791` pixel width screen. This happens only if you have not any posts. (I've identified the problematic commit using `git bisect` starting with a good old commit `git bisect good e5d7c9aa4e0be14427bac27c079c57f79d3b7ef3` and `git bisect bad 42234d56e5a4bd7d053d85a482b05c5f90b6ef36` that is the last change in origin/master)