On 14. Nov 2017, at 19:26, teor teor2345@gmail.com wrote:
On 15 Nov 2017, at 05:05, Sebastian Hahn mail@sebastianhahn.net wrote:
Hey,
On 14. Nov 2017, at 19:00, teor teor2345@gmail.com wrote: On 15 Nov 2017, at 02:41, Iain R. Learmonth irl@torproject.org wrote:
On 14/11/17 15:35, Ralph Seichter wrote: On 14.11.17 13:52, Iain R. Learmonth wrote: I also notice that the "new look" does not work in Safari 11 on macOS 10.13.1 (High Sierra). For shame! Has nobody tested this?
Problem detail: When accessing https://atlas.torproject.org/ , the query box and explanatory text are missing in Safari. See screenshot at https://imgur.com/a/XnA9f . Searching works fine in Chrome and Firefox on macOS.
This would seem suboptimal.
Atlas never loads in Safari on iOS 11.1.1 on my iPad Mini. I just see a spinning grey and black wheel for 30+ seconds.
Given Apple's iOS app WebKit rules, this likely means that *all* iOS browsers and embedded web views are broken.
I have confirmed the same issue in the Twitter apps web view, and it seems to also affect OnionBrowser, with slightly different symptoms.
If you've broken the second-largest mobile platform, want to revert until it's fixed?
I will look into it, unfortunately I have not tested on all the platforms as I just don't have them available.
Maybe we need a beta site and a call for testing for changes like this?
I believe this is the caching issue again. A beta site likely would not have revealed this issue. You really need to break caches for updates to web apps, hopefully those can be implemented without too much pain.
No, it isn't: one of the new resources appears to be blocked by AdBlock Plus for iOS. So it only works with content blockers turned off. You probably want to fix this eventually, because these blocklists are popular. And the issue likely affects multiple platforms. But it's not an all iOS devices bug.
Interestingly, it works in the Facebook app web view. Somehow it doesn't surprise me that Facebook is allowed to break the iOS app rules.
Oh wow, interesting. We only load resources from *tpo so I wonder what would get blocked. In the meantime, I've written a cache busting patch that'll hopefully improve the situation for desktop browsers. Careful review necessary, I don't do much web stuff these days...