Another Hypothes.is test. This time let’s throw a via.hypothes.is-based link (which seems to be the only way to and shove it all in) into an iframe! What will be orphaned? What will be native? Will annotating the iframed version push the annotations back to the original, will they show up as orphaned, or will they show up on the parent page of the iframe, or all of the above?

#D5CC5A; overflow: hidden; margin: 5px auto; max-width: 1000px;">

I also wonder if we could use fragments to target specific portions of pages like this for blockquoting/highlighting and still manage to get the full frame and Hypothes.is interface? Let’s give that a go too shall we? Would it be apropos to do a fragment quote from Fragmentions for Better Highlighting and Direct References on the Web?

#D5CC5A; overflow: hidden; margin: 5px auto; max-width: 1000px;">

Shazam!! That worked rather well didn’t it? And we can customize the size of the iframe container to catch all of the quote rather well on desktop at least. Sadly, most people’s sites don’t support fragmentions or have fragmentioner code running. It might also look like our fragment is causing my main page to scroll down to the portion of the highlighted text in the iframe. Wonder how to get around that bit of silliness?

And now our test is done.

2 thoughts on “”

  1. On multiple reloads, I’m noticing I get terrifically different results in terms of what Hypothes.is is doing with this page. Sometimes everything links to my embedded page and others to Cassie’s variously orphaning or not what appears. Curious and curiouser. I have a feeling things would work out better if I were only iframing one page at a time.

  2. I suspect the issue with multiple reloads is caused by the question of which iframe hypothesis is loading into first… and both are getting the same subpage instead of each one getting its own?

Leave a Reply

Your email address will not be published. Required fields are marked *