You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inline disqussions are showing differently between browsers. #8
(The fourth reply in this thread has a more accurate description of the problem.)
Hi there, I'm using this great piece of work on my website here: http://duncan.net.nz .
I tested it a couple of months back and it was working however now it seems that the inline disqussions wont show in Firefox. They work in Safari and Chrome.
Also, some of the paragraphs shows inlineDisqussion bubbles of "0" with no comments, rather than "+" with no comments. Not sure what's going on there and if it is at all related.
Let me try explaining this again. The more I test, the more confusing it is getting.
There are a few things going on here so I've tried to explain what is happening in each state. I don't have IE.
When paragraphs are not mouse-overed and do not have comments, chrome, safari and firefox all show no bubble.
When paragraphs are not mouse-overed and do have comments, chrome and firefox show no bubble...
... and Safari usually shows a dimmed bubble with the number of comments in it. Sometimes the bubble is hidden like in Chrome and Firefox. I cannot see any reason for this. It doesn't seem to be directly related to the previous load of the page or the state the bubble was in last time.... etc. It usually shows, but not always.
When a paragraph is mouse-overed and does not have comments, firefox, chrome and safari will either show a "+" bubble or a "0" bubble. I can't see any reason for the differences that explains the choice of a "+" or a "0".
When a paragraph is mouse-overed and does have comments, safari and chrome will show the number of comments...
... but Firefox will show a "+", both before the comment window is opened, and after it is opened.
Before:
After:
The '0' issue might be simply related to your settings on your disqus app admin page, look for Comment Count > Zero Comments, mine is set to '+'.
Seems like your other problems are around the loadDisqusCounter() function.
I'm simply giving Disqus's count.js a second to load but there should be a better way to know it is ready.
Activity
tsi commentedon Feb 24, 2014
That seems like a CSS issue.
I think a possible fix may be to change the
height: 100%on#pagetomin-height: 100%PaddyPatPat commentedon Feb 24, 2014
Hmmm, I don't think it's a CSS issue. Here's what Firefox shows...
(Sorry, slowly learning more about the issue.)
tsi commentedon Feb 24, 2014
So now it shows?
PaddyPatPat commentedon Feb 24, 2014
Let me try explaining this again. The more I test, the more confusing it is getting.
There are a few things going on here so I've tried to explain what is happening in each state. I don't have IE.
When paragraphs are not mouse-overed and do not have comments, chrome, safari and firefox all show no bubble.
When paragraphs are not mouse-overed and do have comments, chrome and firefox show no bubble...


... and Safari usually shows a dimmed bubble with the number of comments in it. Sometimes the bubble is hidden like in Chrome and Firefox. I cannot see any reason for this. It doesn't seem to be directly related to the previous load of the page or the state the bubble was in last time.... etc. It usually shows, but not always.
When a paragraph is mouse-overed and does not have comments, firefox, chrome and safari will either show a "+" bubble or a "0" bubble. I can't see any reason for the differences that explains the choice of a "+" or a "0".


When a paragraph is mouse-overed and does have comments, safari and chrome will show the number of comments...



... but Firefox will show a "+", both before the comment window is opened, and after it is opened.
Before:
After:
tsi commentedon Feb 25, 2014
The '0' issue might be simply related to your settings on your disqus app admin page, look for Comment Count > Zero Comments, mine is set to '+'.
Seems like your other problems are around the loadDisqusCounter() function.
I'm simply giving Disqus's count.js a second to load but there should be a better way to know it is ready.