search

hypothesis / product-backlog

Where new feature ideas and current bugs for the Hypothesis product live
118 stars 7 forks source link

PDF annotations fail to anchor on page load #970

Open xolotl opened 5 years ago

xolotl commented 5 years ago

Steps to reproduce

  1. Visit https://library.educause.edu/~/media/files/library/2019/2/2019horizonreportpreview.pdf
  2. Note how annotations load as orphans.
  3. Visit another group and then switch back to Public and note the annotations now anchored.
  4. Or try logging out of the client and note the public annotations now anchored.

Expected behavior

Annotations should be anchored without taking other actions.

Actual behavior

See steps to reproduce.

Browser/system information

Additional details

See Slack chat with @klemay.

klemay commented 5 years ago

I should note that I've seen this come up in support quite a bit lately, in the LMS app and in LMS contexts. Originally I thought this was related to the slowness Via was experiencing last week, but Nate experienced this in a non-Via context.

Switching groups or logging in/out does appear to re-anchor orphans; refreshing the whole page leads to mixed results (sometimes annotations re-anchor, sometimes they appear as orphans again).

Recent support inbox requests:

dwhly commented 5 years ago

I am seeing this a lot myself personally. It happened again yesterday on a PDF at congress.gov. I just checked again this morning. No problems.

When it fails, it doesn't matter whether you're in chrome, FF or the extension or via-- it fails across the board. I have not tried switching groups or logging in/out, but I will next time I see it.

robertknight commented 5 years ago

@klemay - Have you been able to reproduce this at all in LMS contexts?

klemay commented 5 years ago

@robertknight Personally, no. But a lot of LMS users report it. I always ask them to send me the PDF, and when I create an assignment in our LMSes + add annotations, they anchor just fine. Even the example Nate points to above works perfectly for me. But we know it happens, because I get reports + screenshots from users.