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
** Changed in: oxide
Importance: Undecided => Medium
** Changed in: oxide
Status: New => Tr
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 buil
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser
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
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?
--
You received this bug notification because you are a memb
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 :/
** Summary changed:
- iframe with a 404 status doesn't displa
6 matches
Mail list logo
