Error with iframe `allow` attribute when annotating pages on archive.org about client HOT 6 CLOSED

Hypothesis sets a non-writable property on the sidebar iframe specifically to avoid pywb messing with it. See

from client.

I created a PR upstream to avoid the need for any workaround, after agreeing with the maintainer that it made sense, but it has been stale since webrecorder/wombat#134

We could avoid the error here by making the allow property writable, but making the setter a no-op

I think this is very reasonable.

from client.

The PR in wombat has been merged and released. I suppose we'll get the fix when pywb is updated.

from client.

I suppose we'll get the fix when pywb is updated.

I'm not sure how long that will take. We should probably put an interim workaround in our own code, such as giving the sidebar iframe a no-op allow setter.

from client.

I suppose we'll get the fix when pywb is updated.

I'm not sure how long that will take. We should probably put an interim workaround in our own code, such as giving the sidebar iframe a no-op allow setter.

Yep, agree.

from client.

I created #6227 to address this with a noop setter as suggested.

from client.