I do not see any hacking on the client side, which does not turn into a full-blown design. You might be able to hack it, but reporting it to WebKit seems to be best.
WebKit error 170640 is what prevented largeImageAsyncDecodingEnabled from turning on. It also caused flickering. Once this was fixed, they turned it on by default. However, this suggests that the problem still remains.
HTTP headers extracted from github
This can be useful if someone decides to submit a bug report to WebKit.
The standard title is as follows.
MJPG braid / MJPG braid-experimental / plugins / output_http / httpd.h
#define STD_HEADER "Connection: close\r\n" \ "Server: MJPG-Streamer/0.2\r\n" \ "Cache-Control: no-store, no-cache, must-revalidate, pre-check=0, post-check=0, max-age=0\r\n" \ "Pragma: no-cache\r\n" \ "Expires: Mon, 3 Jan 2000 12:34:56 GMT\r\n"
Then for the actual image stream:
MJPG braid-experimental / plugins / output_http / httpd.C # L466
sprintf(buffer, "HTTP/1.0 200 OK\r\n" \ "Access-Control-Allow-Origin: *\r\n" \ STD_HEADER \ "Content-Type: multipart/x-mixed-replace;boundary=" BOUNDARY "\r\n" \ "\r\n" \ "--" BOUNDARY "\r\n");
A small note already has settings / switches in WebKit to enable and / or disable largeImageAsyncDecodingEnabled, check here . I doubt that this is available through Safari UI tho and does not solve the problem without user interaction.
Penquin
source share