Javascript Alert/Confirm don't work with the Webapp container

Bug #1292836 reported by Adnane Belmadiaf
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu HTML5 UI SDK
Triaged
Low
Unassigned
webbrowser-app
Invalid
Undecided
Unassigned

Bug Description

This is because the components that handle those functions are only implemented in the browser-app

Adnane Belmadiaf (daker)
description: updated
David Barth (dbarth)
Changed in ubuntu-html5-theme:
importance: Undecided → Low
status: New → In Progress
status: In Progress → Confirmed
status: Confirmed → Triaged
milestone: none → 14.04
Revision history for this message
Olivier Tilloy (osomon) wrote :

Note: the webapp-container executable does have the dialogs (they are shared between webbrowser-app and webapp-container).

ubuntu-html5-app-launcher uses a plain UbuntuWebView, and as such doesn’t re-use the private components from webapp-container. There are two options to solve this:

 1) ubuntu-html5-app-launcher provides its own set of dialog components (possibly copying the ones from webbrowser-app, which are not shared publicly)

 2) We expose the common dialogs as public components in the Ubuntu.Components.Extras.Browser plugin, but without localized strings, and that means that we also need to expose all potentially translateable strings as top-level properties of those common components.

For the sake of simplicity, I’d rather go for option 1, as option 2 requires some non trivial refactoring, and I’m not very fond of exposing more components on the public API, even more so that they won’t actually be used by UbuntuWebView.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Option #3 would be to get rid of ubuntu-html5-app-launcher and replace it with webapp-container, but I don’t know how doable/desirable that is.

Revision history for this message
Alexandre Abreu (abreu-alexandre) wrote :

I marked this as non related to webapp-container,

For reference, option #3 is not really desirable imo, since the html5-container has a different "security" model and execution environment (loosens the javascript code injection process & access to oxide apis), gives access to extra unity apis, etc. handling all this in the same container might create gaps and higher complexity than necessary imo,

Changed in webbrowser-app:
status: New → Invalid
Changed in ubuntu-html5-theme:
milestone: 14.04 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.