Closed Bug 1083274 Opened 10 years ago Closed 10 years ago

Clicking on articles in sidebar does nothing

Categories

(Websites :: The Open Standard, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pmac, Assigned: rex)

References

Details

STR: 1. Be on an article page. 2. Open sidebar by clicking hamburger menu in top left corner. 3. Click an article in the sidebar. Expected: To go to clicked article. Actual: Nothing happens. I tested in Fx Nightly and latest Safari. It appears that the overlay is blocking access to the sidebar content on article pages. The sidebar works from the home page.
Assignee: nobody → rex
Blocks: 1046397
On Fx 33 when I click an article in the sidebar it collapses the sidebar.
Additional info. This looks to be caused by the comments template > single.php line 85: <?php comments_template(); ?> Commenting that out and the nav works.
OK i think i found the cause. comments.php line 56. there is what appears to be an errant </div>
This looks to be fixed on many posts however I can still find a couple where this is occuring: https://openstandard.mozilla.org/what-the-hell-facebook-probe-reveals-news-feed-surprises/ The odd thing is.. if i am logged in as an admin it works, log out does not work.
Flags: needinfo?(rex)
I think it has something to do with the LEFT arrow that appears on some posts.
(In reply to Ben (:bensternthal) from comment #5) > This looks to be fixed on many posts however I can still find a couple where > this is occuring: > > https://openstandard.mozilla.org/what-the-hell-facebook-probe-reveals-news- > feed-surprises/ > > The odd thing is.. if i am logged in as an admin it works, log out does not > work. That page works just fine for me. (not logged in).
Hmmm Ill try and debug more and see if i can find something reproducible.
Im gonna call this one resolved for now. I think this may have been a cache issue (Wordpress cache). If it creeps up again I shall re-open.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(rex)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.