-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
Fix #48 Footer position #550
Conversation
Screens, please. |
source/js/src/utils.js
Outdated
$div.remove(); | ||
|
||
return scrollbarWidth; | ||
}, | ||
|
||
getContentVisibilityHeight: function() { | ||
var docHeight = $('#content').height(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For what needed this changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$('#content').height()
doesn't contain the height of #comments
, and it will lead to a wrong calculation of the page's height
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, go see examples with getContentVisibilityHeight
function. Because i remember, it was work fine (but mb not with all comments systems) and mb not now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. I have thought about it, and seems it would be better to change it back... maybe it's just designed like this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, this function for rightly back2top percentage ratio. When comments systems exists, horizontal height changed dynamically when page will scrolled, so, b2t percent was counting not rightly.
This all i remember when add this function. For now some comment systems have dynamic loading (like lazy
option for Disqus), so, i suggest to retest it in future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is changes for this function & b2t:
- iissnan/hexo-theme-next@4bd315d (PR #1574)
- iissnan/hexo-theme-next@028fe60
and addition iissnan/hexo-theme-next@61086aa
(PR #1898)
So, you can review this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$('#content').height()
doesn't contain the height of#comments
, and it will lead to a wrong calculation of the page's height
As we can see, b2t percent not contain comments div to counting to around wrong percentage ratio. And #content
– meaning content of div > post-block
, not content of comments block. That's why this function exists.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, need to discuss
$('#content').height()
and$('.container').height()
in the future
Here is 2 problems:
- Comment system can be loaded with
lazy
(viewport height will more only when user scrolled down). - Comment system loaded from 3rd-party side. So, JS on our server don't know which height we need to count.
But you can try to play around with this. Maybe you got success decision and make this coll feature (or bugfux).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about adding this to NexT v7.x Roadmap(#67)? I have reviewed the previous changes, but have no idea how to solve this...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add it, of course. Anyway, I think NexT have more important things to improvment.
P.S. From next year we will start to work for v7.x and all bugfixes / features will pushed there. We also will resume maintenance for v6.x, but will be pushed only bugfixes. I want to create gantt roadmap something like in nodejs (https://github.com/nodejs/Release). Need to think about it better in details, any suggestions are welcome. In ideal need any chat with you to talk about this.
Wait a minute @ivan-nginx Screenshots added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, need to test on all possible resolutions all 4 schemes.
Here is good service for this: http://www.responsinator.com (or you can do it with browser if you want)
Screens or links, if it's possible.
@ivan-nginx Fixed now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done!
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number(s): #48
https://galaxymimi.com/before/mist/
https://galaxymimi.com/before/muse/
https://galaxymimi.com/before/pisces/
https://galaxymimi.com/before/gemini/
What is the new behavior?
Description about this pull, in several words...
https://galaxymimi.com/after/mist/
https://galaxymimi.com/after/muse/
https://galaxymimi.com/after/pisces/
https://galaxymimi.com/after/gemini/
Before & After
Muse:
Mist:
Pisces:
Gemini:
How to use?
In NexT
_config.yml
:Does this PR introduce a breaking change?