[Browser] iframe doesn't display anything when a load fails

[Adnane Belmadiaf]

Ex : http://jsfiddle.net/zHR89/

[Chris Coulson (chrisccoulson)]

I've changed the title - if we get a 404 response, the frame will display the response from the server. In this case, the load fails (there is no 404).

I guess this is the downside of having the error page as part of the browser UI :/

[Chris Coulson (chrisccoulson)]

So the only way to fix this is to implement the error page as HTML, and have Oxide render that in the right frame.

Olivier, how easy would it be to implement the error page in HTML if I provide a mechanism to allow Oxide to display it?

[Adnane Belmadiaf (daker)]

i guess it's also a matter of i18n the error page content, handling the size of assets depending on the screen, i think this is how it's done in Chrome/ium

https://chromium.googlesource.com/chromium/src/+/master/chrome/renderer/resources/neterror.html
https://chromium.googlesource.com/chromium/src/+/master/chrome/renderer/resources/neterror.js

[Olivier Tilloy (osomon)]

Chris, the current design only requires the page to have a reload button, so implementing it in HTML would be trivial.
As Adnane points out, we’ll need to internationalize the contents. We can probably generate the page dynamically, or generate static pages for each available translation at build time. What would the API for defining the error page look like?

[Olivier Tilloy (osomon)]

Added an ubuntu-ux task to get input from design: we might want to consider displaying a slightly different error page when in an iframe, as opposed to the main frame.

[Chris Coulson (chrisccoulson)]

I don't know what an API would look like yet, as this lives on the renderer side. Generating content dynamically and handling localizations isn't a problem though - Chrome uses the same mechanism

[Chris Coulson (chrisccoulson)]

So, the fix for this is that the error page will be implemented in HTML and live in the new UbuntuWebView implementation inside Oxide.