Looking at Content -> Comments and selecting one (e.g. in order to reply to it) does some jumping but one never lands at the comment one clicked. Rather, one needs to focus the URL bar and hit return to finish the jump to the comment in question.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Hm, that still does not work for me in all cases. For instance I logged in and looked at the comment queue, scrolled down until I found https://blog.torproject.org/comment/270924#comment-270924 and clicked on it. The blog seems to try jumping to it but fails.
Trac: Resolution: fixed toN/A Status: closed to reopened
Is this a browser issue or some system issue? I have tested this on firefox nightly and 55 on linux. In both cases it works ok for me. Same on Tor browser.
Is this a browser issue or some system issue? I have tested this on firefox nightly and 55 on linux. In both cases it works ok for me. Same on Tor browser.
This happens with a Tor Browser alpha on a XFCE Debian testing system with a 1000x600 browser window.
Is this a browser issue or some system issue? I have tested this on firefox nightly and 55 on linux. In both cases it works ok for me. Same on Tor browser.
This happens with a Tor Browser alpha on a XFCE Debian testing system with a 1000x600 browser window.
Let me do a bit more testing, I might be able to track this better down...
Is this a browser issue or some system issue? I have tested this on firefox nightly and 55 on linux. In both cases it works ok for me. Same on Tor browser.
This happens with a Tor Browser alpha on a XFCE Debian testing system with a 1000x600 browser window.
Let me do a bit more testing, I might be able to track this better down...
Yeah, here are the steps that reproduce this issue for me (I tried several times):
Take a new 7.5a4 en-US Linux 64 bit bundle
Go to this bug
Load the URL in comment:4 in a new tab
Switch to the tab and you'll see that the comment is almost jumped to. In my case I and at the previous one or so
Focusing the URL bar and hitting Enter jumps finally to the intended comment.
Ok, but this might not be a trac or blog bug as rather a browser bug? I'd like to make the following test, I create a page with some text and some anchors links. If the behaviour is the same this can be considered a browser bug rather than an issue w/ the html of the blog or trac.
Ok, but this might not be a trac or blog bug as rather a browser bug? I'd like to make the following test, I create a page with some text and some anchors links. If the behaviour is the same this can be considered a browser bug rather than an issue w/ the html of the blog or trac.
Will follow up w/ the page.
I did some more testing. This seems to me intermittent. So, as you indicated, it might actually be not a blog bug. Maybe it's just my machine. Until I've got better steps to reproduce let's close this as WORKSFORME. Sorry for the additional work.
Trac: Resolution: N/Ato worksforme Status: reopened to closed
It is just plain html and doesn't load any JS. Can you observe the same behaviour? If this is not related to the blog but rather the browser/system maybe we should give a heads up to the firefox people.
Another data point: I can't reproduce the problem with JavaScript disabled. I tried pretty hard. But with JavaScript enabled it is easy for me to hit it.
No, I was not logged in. Here is what I did: I reloaded the blog comment in comment:4 ten times over a different Tor circuit with JavaScript enabled and ten times without (I flipped javascript.enabled) and restarted between both tests.
Without JavaScript enabled I did not see a single instance of this issue. With JavaScript enabled I saw it in 8 cases.
No. But I can't reproduce it for that particular comment on the live blog either. So, not a good test case. :) (But I can with the comment mentioned in comment:4 on the live blog)
JS is disabled everywhere on the dev blog at the moment. So if you have the time to surf around a bit that would be nice. There isn't the same comment on the prod and dev blogs, but certainly we use the same template.
Okay, after quite some testing I found a comment on the dev blog that even shows the issue (or a similar one) with a clean, new vanilla Firefox on my Linux system: https://dev-tor-blog-8.pantheonsite.io/comment/258307#comment-258307. However, I have to be logged in to trigger the problem in this case. For Firefox I need to press "Ctrl + Shift + R" to reload the page and then after that's done hitting Enter will jump down to the comment.
Doing the daily comment approval thing makes me believe that this issue is even more easily reproducible with being logged in (but it might be slightly different one, see comment:24).
Gk I have disabled JS in the dev blog for the normal template. However if you are logged in, the drupal toolbar loads some javascript libraries, and so does the admin template.
This means it might be an issue w/ how firefox loads some function of underscorejs.org (and other libraries loaded by trac.tpo and other websites) or w/ firefox itself.
Also could it be something that is solved in newer versions of firefox?
Also please let me know what we should do regarding this ticket. I do not think we should track this as a blog issue, but I'd be happy to debug it more if we really think it could be useful.
Gk I have disabled JS in the dev blog for the normal template. However if you are logged in, the drupal toolbar loads some javascript libraries, and so does the admin template.
This means it might be an issue w/ how firefox loads some function of underscorejs.org (and other libraries loaded by trac.tpo and other websites) or w/ firefox itself.
Also could it be something that is solved in newer versions of firefox?
That's still an issue in the latest Firefox nightly.
Also please let me know what we should do regarding this ticket. I do not think we should track this as a blog issue, but I'd be happy to debug it more if we really think it could be useful.
If you feel that's not blog business but Tor Browser/Firefox one I am fine setting the component accordingly. In fact let me do that right away.
Hi gk, I am not sure it is a blog issue, but I am not sure it's a firefox issue either. Might be something to do with some function in that library.
Maybe, before investigating this as a browser bug, I can try replace that w/ standard jquery, or remove it completely (better option) as JS is only used to submit comments. What do you think?
Hi gk, I am not sure it is a blog issue, but I am not sure it's a firefox issue either. Might be something to do with some function in that library.
Maybe, before investigating this as a browser bug, I can try replace that w/ standard jquery, or remove it completely (better option) as JS is only used to submit comments. What do you think?
Well, I have the same problem with Trac (see comment:27). Once I disable JS the jumping works but with it on there are issues as well. That said, I am happy to have less JS on the blog (and/or on Trac), so go for that if you can. :)