When using split/story mode, most articles from vox.com do not load

problem
#1

When using split/story mode most but not all articles from vox.com will not load. The story pane will be blank.

Chrome console gives the following error: 
Refused to display ‘http://www.vox.com/2015/6/24/8838383/working-mothers-impact-on-kids’ in a frame because it set ‘X-Frame-Options’ to ‘SAMEORIGIN’.common.js:129 Uncaught SecurityError: Failed to read the ‘contentDocument’ property from ‘HTMLIFrameElement’: Sandbox access violation: Blocked a frame at "http://www.newsblur.com"; from accessing a frame at “null”.  The frame being accessed is sandboxed and lacks the “allow-same-origin” flag.

Example that does not load:
http://www.vox.com/2015/6/24/8838383/working-mothers-impact-on-kids

Example the DOES load:

http://www.vox.com/2015/6/24/8838839/smoking-age-drinking-age-works

2 Likes
#2

It’s just the publisher’s intention that we’ll have to respect. If they don’t want you in Story mode, Text mode is the best we can do.

#3

Huh, that’s bizarre. You’d think they would want me to view the actual site instead of a text grab. Why do think it does work for some articles?

#4

Good question. That content-origin policy is an HTTP header, which isn’t trivial to setup. It’s possible that only stories that go through a particular content management branch get that header while some custom stories do not. That’s my guess without diving in deep.