Chrome and humax web portal
- Thread starter annonimouse
- Start date
Thanks for the pointer!
For completeness, here's a link to the open bug with Chrome: https://code.google.com/p/chromium/issues/detail?id=246875
In my opinion, Chrome is doing the wrong thing. The web server shouldn't really send any content-type header along with a not-modified response but the standard only says SHOULD NOT. Sending one should not break the web browser's rendering.
In my opinion, Chrome is doing the wrong thing. The web server shouldn't really send any content-type header along with a not-modified response but the standard only says SHOULD NOT. Sending one should not break the web browser's rendering.
Rogerh
New Member
I have noticed one difference between Chrome and Safari.
At the bottom of the "Browse" screen is the box "Save Last Streamed Content" etc. Using Safari the size of the file is indicated "xxxMiB", but the line is missing from "Chrome". Also when the file is being recorded Chrome does not show "5MiB, growing at 6.60MiB", but Safari does
Roger
At the bottom of the "Browse" screen is the box "Save Last Streamed Content" etc. Using Safari the size of the file is indicated "xxxMiB", but the line is missing from "Chrome". Also when the file is being recorded Chrome does not show "5MiB, growing at 6.60MiB", but Safari does
Roger
mole_hill
Member
I have also noticed this recently. However this has been happening for several days before the recent Mongoose upgrade so I don't think they are necessarily related.
Just wanted to publicly say thanks to af123 for kindly providing me with details of his mongoose patch which I have since used to fix the same problem experienced by users of the custom firmware on the Foxsat HDR, when accessing the webif via the Chrome browser.
Much appreciated af123 !
Much appreciated af123 !