[Ubuntu-webapps-bugs] [Bug 1301650] Re: Setting WebContext.sessionCookieMode without specifying a path causes a crash
** Changed in: oxide
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1301650
Title:
Setting WebContext.sessionCookieMode without specifying a path causes
a crash
Status in Oxide Webview:
Fix Released
Bug description:
Doing this:
WebView {
context: WebContext {
sessionCookieMode: WebContext.SessionCookieModePersistent
}
}
...is enough to trigger a debug-mode assertion failure inside
Chromium:
[0402/224320:FATAL:sqlite_persistent_cookie_store.cc(1271)] Check failed:
!path.empty() || session_cookie_mode == EPHEMERAL_SESSION_COOKIES.
#0 0x2b880d9ca26b base::debug::StackTrace::StackTrace()
#1 0x2b880da41a27 logging::LogMessage::~LogMessage()
#2 0x2b8812297a2d content::CookieStoreConfig::CookieStoreConfig()
#3 0x2b880d90c516 oxide::BrowserContextIOData::CreateMainRequestContext()
#4 0x2b880d90b7d0 oxide::(anonymous
namespace)::MainURLRequestContextGetter::GetURLRequestContext()
#5 0x2b8811ec4ba9 content::ChromeAppCacheService::InitializeOnIOThread()
#6 0x2b881253c2e6 base::internal::RunnableAdapter::Run()
#7 0x2b881253b3dc base::internal::InvokeHelper::MakeItSo()
#8 0x2b8812539d18 base::internal::Invoker::Run()
#9 0x2b880d9b8646 base::Callback::Run()
#10 0x2b880da62372 base::MessageLoop::RunTask()
#11 0x2b880da624a0 base::MessageLoop::DeferOrRunPendingTask()
#12 0x2b880da629f0 base::MessageLoop::DoWork()
#13 0x2b880d996dcc base::MessagePumpLibevent::Run()
#14 0x2b880da61e66 base::MessageLoop::RunHandler()
#15 0x2b880dac5cca base::RunLoop::Run()
#16 0x2b880da6149c base::MessageLoop::Run()
#17 0x2b880db1dc14 base::Thread::Run()
#18 0x2b8811f08530 content::BrowserThreadImpl::IOThreadRun()
#19 0x2b8811f086f7 content::BrowserThreadImpl::Run()
#20 0x2b880db1de6b base::Thread::ThreadMain()
#21 0x2b880db0c2a4 base::(anonymous namespace)::ThreadFunc()
#22 0x2b87f6c9b182 start_thread
#23 0x2b87f69c830d clone
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1301650/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1300891] Re: Refine WebView.navigationRequested and WebView.newViewRequested
I ended up fixing this without adding a third signal in the end. Instead, it now dispatches WebView.navigationRequested for *all* requests to open a new window, regardless of the origin of these. This is dispatched before any resources are created and should be used if the application wants to block a window from opening. WebView.newViewRequested is now always dispatched when the underlying WebContents is ready to display. If an application implements this, it is expected that it creates a new WebView. It shouldn't be used for policy decisions (use navigationRequested for that), so I've removed NewViewRequest.url and NewViewRequest.userGesture to discourage this. I'll probably make it output a console warning if an application implements this but doesn't create a WebView. ** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1300891 Title: Refine WebView.navigationRequested and WebView.newViewRequested Status in Oxide Webview: Fix Released Bug description: I initially thought that all top-level navigations would result in WebView.navigationRequested firing, and that this could be used to block all navigations whether they are going to happen in the current webview or not (accepting a navigation with disposition != CurrentTab would then result in WebView.newViewRequest firing, and the application creating a new WebView). Using WebView.newViewRequest to block a navigation in a new view doesn't really work correctly at the moment due to bug 1300884. However, there are some exceptions which make the current API a bit confusing: - window.open() only results in WebView.newViewRequested (although I knew about this one) - Clicking on an anchor with target=_blank only results in WebView.newViewRequested - Clicking with modifiers on an anchor that has no target results in both WebView.navigationRequested and WebView.newViewRequested. - Subframe navigations that have a disposition of CurrentTab don't result in any signal, but this one is expected. - Browser-initiated navigations don't result in either signal, but this is deliberate too. I think this should probably be cleaned up by: - Removing NavigationRequest.disposition and only dispatching WebView.navigationRequest for top-level renderer-intiated navigations for the current view. - Dispatch only WebView.newViewRequested for all navigations that are not destined for the current WebView, which requires fixing bug 1300884 so that this can be used to reject requests. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1300891/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1302740] [NEW] WebView.navigationRequested isn't emitted for new-window navigations when WebView.newViewRequested isn't implemented
Public bug reported: When WebView.newViewRequested isn't implemented, all navigations and window open requests are done in the current view. However, sites can navigate the current view with window.open() or a link with target=_blank without WebView.navigationRequested being emitted ** Affects: oxide Importance: Medium Status: Triaged ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1302740 Title: WebView.navigationRequested isn't emitted for new-window navigations when WebView.newViewRequested isn't implemented Status in Oxide Webview: Triaged Bug description: When WebView.newViewRequested isn't implemented, all navigations and window open requests are done in the current view. However, sites can navigate the current view with window.open() or a link with target=_blank without WebView.navigationRequested being emitted To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1302740/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1302743] [NEW] NavigationRequest and NewViewRequest emitted with different dispositions when opening popup windows
Public bug reported: When calling window.open() with a non zero-length window features parameter that doesn't enable the menubar, toolbar, location, status, and scrollbars features, we get a NavigationRequest with the disposition set to NewForegroundTab, and then a NewViewRequest with the disposition set to NewPopup. The NavigationRequest is wrong in this case ** Affects: oxide Importance: Low Status: Triaged ** Changed in: oxide Importance: Undecided = Low ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1302743 Title: NavigationRequest and NewViewRequest emitted with different dispositions when opening popup windows Status in Oxide Webview: Triaged Bug description: When calling window.open() with a non zero-length window features parameter that doesn't enable the menubar, toolbar, location, status, and scrollbars features, we get a NavigationRequest with the disposition set to NewForegroundTab, and then a NewViewRequest with the disposition set to NewPopup. The NavigationRequest is wrong in this case To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1302743/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1301678] Re: scrollbars incorrect in Facebook (and other) webapps
** Changed in: oxide Status: Fix Committed = Fix Released ** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1301678 Title: scrollbars incorrect in Facebook (and other) webapps Status in Oxide Webview: Fix Released Status in The Webapps-core project: Confirmed Status in Web Browser App: Confirmed Status in “oxide-qt” package in Ubuntu: New Bug description: Using latest oxide and webapps, some of the webapps, notably Facebook display think vertical scroll bars. This only occurs in the webapp version. If you run Facebook in the browser the scrollbars appear correct (very small and thin) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1301678/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1300382] Re: input events not being flushed in browser until pressing hardware keys
** Changed in: oxide Status: Fix Committed = Fix Released ** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1300382 Title: input events not being flushed in browser until pressing hardware keys Status in Oxide Webview: Fix Released Status in Ubuntu Keyboard: Fix Released Status in The Webapps-core project: New Status in “oxide-qt” package in Ubuntu: New Status in “ubuntu-keyboard” package in Ubuntu: Fix Released Bug description: using webbrowser-app from Silo 9 and oxide in universe Log in to Facebook on the phone Click comment in someone's post Start typing Expected results: The comment button should become enabled so you can submit comment Actual results: The comment button always stays disabled. Tested this on webbrowser-app on desktop with oxide (explicilty loading m.facebook.com) and becomes enabled as it should after typing. Seems specific to device. Guessing it's a UA String issue. Is there a way to see the JS console to see if a JS error is occuring? To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1300382/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1291389] Re: Deliver console messages to embedder
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1291389 Title: Deliver console messages to embedder Status in Oxide Webview: Fix Released Bug description: Currently, we don't implement WebContentsDelegate::AddMessageToConsole(), which means all console messages from JS in the renderer get logged to the current terminal. We should implement this and route these to a signal on the WebView To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1291389/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1301341] Re: grooveshark playback has stopped functioning
** Changed in: oxide Status: New = Fix Released ** Changed in: oxide-qt (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1301341 Title: grooveshark playback has stopped functioning Status in Oxide Webview: Fix Released Status in Web Browser App: Confirmed Status in “oxide-qt” package in Ubuntu: Fix Committed Bug description: STEPS: 1. Move to the music scope 2. Select an online track from grooveshark 3. Select play in grooveshark 4. Once grooveshark opens in the browser select the track to play EXPECTED: Musc starts to play ACTUAL: The player looks like it is stating up but then actually plays nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1301341/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1260008] Re: Expose a 'filePicker' property on OxideQQuickWebView
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1260008 Title: Expose a 'filePicker' property on OxideQQuickWebView Status in Oxide Webview: Fix Released Bug description: For feature parity with QtWebKit, we need to expose a 'filePicker' property (or similar, in QtWebKit it’s 'experimental.filePicker') on the QML WebView, to allow applications to provide a custom component to select files. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1260008/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1257662] Re: Implement cursor support
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1257662 Title: Implement cursor support Status in Oxide Webview: Fix Released Bug description: Chromium tells us which cursor to display via content::RenderWidgetHostView::UpdateCursor(). We should implement this and hook it in to Qt To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1257662/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1304648] [NEW] Forks browser process to run sandbox IPC helper
Public bug reported: Chromium forks the browser process to run a sandbox IPC helper process, which provides a mechanism for sandboxed renderers to access things like the font cache. However, it does this without execing a new process image in the child. Whilst this is fine for Chromium (because it forks at startup and before any threads are created), it is bad for us for a few reasons: By the time we start Chromium: - We already have a QML app and Qt gunk running in the browser process - I suspect that a lot of the memory used by the app will get copied eventually, which is a waste. - We already have many threads running. As threads don't get forked, the child process will deadlock if any thread held a lock it requires at some point. ** Affects: oxide Importance: Critical Status: Fix Committed ** Changed in: oxide Importance: Undecided = Critical ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1304648 Title: Forks browser process to run sandbox IPC helper Status in Oxide Webview: Fix Committed Bug description: Chromium forks the browser process to run a sandbox IPC helper process, which provides a mechanism for sandboxed renderers to access things like the font cache. However, it does this without execing a new process image in the child. Whilst this is fine for Chromium (because it forks at startup and before any threads are created), it is bad for us for a few reasons: By the time we start Chromium: - We already have a QML app and Qt gunk running in the browser process - I suspect that a lot of the memory used by the app will get copied eventually, which is a waste. - We already have many threads running. As threads don't get forked, the child process will deadlock if any thread held a lock it requires at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1304648/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1304648] Re: Forks browser process to run sandbox IPC helper
** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1304648 Title: Forks browser process to run sandbox IPC helper Status in Oxide Webview: Fix Committed Status in “oxide-qt” package in Ubuntu: New Bug description: Chromium forks the browser process to run a sandbox IPC helper process, which provides a mechanism for sandboxed renderers to access things like the font cache. However, it does this without execing a new process image in the child. Whilst this is fine for Chromium (because it forks at startup and before any threads are created), it is bad for us for a few reasons: By the time we start Chromium: - We already have a QML app and Qt gunk running in the browser process - I suspect that a lot of the memory used by the app will get copied eventually, which is a waste. - We already have many threads running. As threads don't get forked, the child process will deadlock if any thread held a lock it requires at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1304648/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1307709] Re: webbrowser-app does not start in Unity 8 preview session
** Also affects: oxide Importance: Undecided Status: New ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide Webview: Triaged Status in Web Browser App: New Status in “unity8-desktop-session” package in Ubuntu: New Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1308397] [NEW] Support Google Talk PPAPI plugin
Public bug reported: For Google Hangouts to work, we need to be able to use the Google Talk PPAPI plugin. On the browser side, some of the Pepper API is implemented in Chrome, so there is a bit of work to do to support this properly ** Affects: oxide Importance: High Status: Fix Released ** Affects: oxide-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Fix Released ** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1308397 Title: Support Google Talk PPAPI plugin Status in Oxide Webview: Fix Released Status in “oxide-qt” package in Ubuntu: New Bug description: For Google Hangouts to work, we need to be able to use the Google Talk PPAPI plugin. On the browser side, some of the Pepper API is implemented in Chrome, so there is a bit of work to do to support this properly To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1308397/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1308412] [NEW] Various issues in GPU code
Public bug reported: There are various issues in the code that communicates with Chromium's GPU thread. At least one of these causes an application crash under some conditions - We're accessing members of the GpuChildThread singleton off the GPU thread in order to dispatch tasks to it. GpuChildThread is not thread safe, so we should store the singleton pointer in TLS to make it unavailable to other threads and provide a function to access the thread-safe MessageLoopProxy to dispatch tasks to the GPU thread - We use the wrong MailboxManager instance to consume textures from Chromium's compositor - We don't ensure we have a current GL context when deleting textures, which results in us hitting a runtime abort inside Chromium ** Affects: oxide Importance: Undecided Status: Fix Released ** Affects: oxide-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: oxide Status: New = Fix Released ** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1308412 Title: Various issues in GPU code Status in Oxide Webview: Fix Released Status in “oxide-qt” package in Ubuntu: New Bug description: There are various issues in the code that communicates with Chromium's GPU thread. At least one of these causes an application crash under some conditions - We're accessing members of the GpuChildThread singleton off the GPU thread in order to dispatch tasks to it. GpuChildThread is not thread safe, so we should store the singleton pointer in TLS to make it unavailable to other threads and provide a function to access the thread-safe MessageLoopProxy to dispatch tasks to the GPU thread - We use the wrong MailboxManager instance to consume textures from Chromium's compositor - We don't ensure we have a current GL context when deleting textures, which results in us hitting a runtime abort inside Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1308412/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1308373] Re: Need HiDPI support
We use the DPR returned by QScreen::devicePixelRatio. If this returns the correct value for the screen, then we scale correctly. The issue is that the xcb backend always returns 1 ** Project changed: oxide = qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1308373 Title: Need HiDPI support Status in “qtbase-opensource-src” package in Ubuntu: Confirmed Bug description: Oxide doesn't attempt to detect and automatically adapt to HiDPI screens. Also, users can't manually increase the zoom level either (at least Ctrl + '+' doesn't work). Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1308373/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1309117] Re: Ebay and Amazon webapps default to .com in the uk
Oxide shouldn't be applying any special casing or modifications for URL's - that sort of thing belongs in the application. We should be sending a localized Accept-Language header (bug 1224707) which might improve things. But if sites depend on location specific URL's, then the application should load these instead ** Project changed: oxide = webbrowser-app -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1309117 Title: Ebay and Amazon webapps default to .com in the uk Status in Web Browser App: New Bug description: Both of these apps have .co.uk on the old desktop app utilised via Firefox the webapps would update by location on oxide this is not the case. Oxide needs to pull in data on location at a guess and update the url accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1309117/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1313727] Re: Deliver input events that aren't consumed by a renderer back to the webview
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1313727 Title: Deliver input events that aren't consumed by a renderer back to the webview Status in Oxide Webview: Fix Released Bug description: RenderViewItem currently consumes all input events (with the exception of some special mouse buttons). However, we need to ensure that events which aren't consumed by the renderer propagate up to parent widgets. I think this can be achieved by still consuming all events in RenderViewItem, implementing content::WebContentsDelegate::HandleKeyboardEvent (and related functions) and then converting these back to QEvent's. This will be required for application keyboard shortcuts to work To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1313727/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1307709] Re: webbrowser-app does not start in Unity 8 preview session
** Changed in: oxide Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: unity8-desktop-session (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide Webview: Triaged Status in Web Browser App: Invalid Status in “unity8-desktop-session” package in Ubuntu: Invalid Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1322348] Re: Debug mode abort on key events
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1322348 Title: Debug mode abort on key events Status in Oxide Webview: Fix Released Status in Oxide 1.0 series: Triaged Bug description: DEbug builds see this on keypress: [0522/213847:FATAL:oxide_qt_web_view.cc(350)] Check failed: !qevent-isAccepted(). #0 0x7fe561a6b39e base::debug::StackTrace::StackTrace() #1 0x7fe561ab5c69 logging::LogMessage::~LogMessage() #2 0x7fe5619c3027 oxide::qt::WebView::HandleKeyboardEvent() #3 0x7fe5651f19ce content::InputRouterImpl::ProcessKeyboardAck() #4 0x7fe5651f3cfd content::InputRouterImpl::ProcessInputEventAck() #5 0x7fe5651f4b52 content::InputRouterImpl::OnInputEventAck() #6 0x7fe5651f0e24 content::InputRouterImpl::OnMessageReceived() #7 0x7fe5652c414d content::RenderWidgetHostImpl::OnMessageReceived() #8 0x7fe5652af82d content::RenderViewHostImpl::OnMessageReceived() #9 0x7fe5652984d5 content::RenderProcessHostImpl::OnMessageReceived() #10 0x7fe561d0ee22 IPC::ChannelProxy::Context::OnDispatchMessage() #11 0x7fe561aca4f3 base::MessageLoop::RunTask() #12 0x7fe561acdd28 base::MessageLoop::DeferOrRunPendingTask() #13 0x7fe561ace137 base::MessageLoop::DoWork() #14 0x7fe5619bc9e0 oxide::qt::MessagePump::customEvent() #15 0x7fe58fd7e2ad QObject::event() #16 0x7fe58fd55efd QCoreApplication::notify() #17 0x7fe58fd55c2d QCoreApplication::notifyInternal() #18 0x7fe58fd57e07 QCoreApplicationPrivate::sendPostedEvents() #19 0x7fe58fda2cd3 unknown #20 0x7fe58cfb4e04 g_main_context_dispatch #21 0x7fe58cfb5048 unknown #22 0x7fe58cfb50ec g_main_context_iteration #23 0x7fe58fda298c QEventDispatcherGlib::processEvents() #24 0x7fe58fd5496b QEventLoop::exec() #25 0x7fe58fd5b0e1 QCoreApplication::exec() #26 0x00402b59 main #27 0x7fe58e051ec5 __libc_start_main #28 0x004034ae unknown To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1322348/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1324909] [NEW] User agent string is incorrect in newly opened webview
Public bug reported: When a new webview is opened via window.open() and the new webview is in the same render process as the opener, the user agent string is incorrect until the first browser-initiated navigation ** Affects: oxide Importance: High Status: Triaged ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1324909 Title: User agent string is incorrect in newly opened webview Status in Oxide Webview: Triaged Bug description: When a new webview is opened via window.open() and the new webview is in the same render process as the opener, the user agent string is incorrect until the first browser-initiated navigation To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1324909/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1259216] Re: Expose an 'icon' property on OxideQQuickWebView
** Also affects: webbrowser-app Importance: Undecided Status: New ** Changed in: webbrowser-app Importance: Undecided = Medium ** Changed in: webbrowser-app Assignee: (unassigned) = Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1259216 Title: Expose an 'icon' property on OxideQQuickWebView Status in Oxide Webview: Fix Committed Status in Web Browser App: New Bug description: For feature parity with QtWebKit, we need to expose an 'icon' property on the QML WebView, to access the favicon of the current page, if any. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1259216/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1309117] Re: Ebay and Amazon webapps default to .com in the uk
*** This bug is a duplicate of bug 1224707 *** https://bugs.launchpad.net/bugs/1224707 ** This bug is no longer a duplicate of bug 1311229 Should override Accept-Language header based on local settings ** This bug has been marked a duplicate of bug 1224707 Use a localized Accept-Language header -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1309117 Title: Ebay and Amazon webapps default to .com in the uk Status in Web Browser App: New Bug description: Both of these apps have .co.uk on the old desktop app utilised via Firefox the webapps would update by location on oxide this is not the case. Oxide needs to pull in data on location at a guess and update the url accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1309117/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1322622] Re: No rendering happens on a dynamically instantiated webview if its 'visible' property was changed
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1322622 Title: No rendering happens on a dynamically instantiated webview if its 'visible' property was changed Status in Oxide Webview: Fix Released Bug description: Dynamically instantiating a webview in QML (using component.createObject(…)) without initially loading a URL, and ensuring it’s initially invisible then shown, and later loading a URL, results in no rendering. This can be worked around by then changing the 'visible' property to false and then true again. I’m attaching a small example that reproduces the issue. Note that it replicates webbrowser-app’s behaviour to deal with tabs, so it’s a pretty critical issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1322622/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1326070] [NEW] Add support for context menus
Public bug reported: There is currently a user-script based hack in the browser to add context menus - we should really add this support natively to Oxide. I believe that the Flash PPAPI plugin requires it anyway ** Affects: oxide Importance: High Status: Triaged ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1326070 Title: Add support for context menus Status in Oxide Webview: Triaged Bug description: There is currently a user-script based hack in the browser to add context menus - we should really add this support natively to Oxide. I believe that the Flash PPAPI plugin requires it anyway To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1326070/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1300694] Re: Middle click to paste text from clipboard into form crashes the renderer
Would be nice to see if we could come up with something low risk for the first proper release as well, even if it doesn't have clipboard support ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Triaged ** Also affects: oxide/1.0 Importance: Undecided Status: New ** Changed in: oxide/1.0 Importance: Undecided = High ** Changed in: oxide/1.0 Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1300694 Title: Middle click to paste text from clipboard into form crashes the renderer Status in Oxide Webview: Triaged Status in Oxide 1.0 series: Triaged Bug description: On desktop, instantiate a WebView and point it to e.g. http://google.com, select some text in another application, then middle-click in the search box in the webview to paste the selected text. This crashes the renderer process with the following stack trace: [0401/120700:FATAL:webclipboard_impl.cc(217)] Check failed: false. #0 0x7f1b9a1d2803 base::debug::StackTrace::StackTrace() #1 0x7f1b9a24a011 logging::LogMessage::~LogMessage() #2 0x7f1b9f4d0340 content::WebClipboardImpl::ConvertBufferType() #3 0x7f1b9f4cf72e content::WebClipboardImpl::sequenceNumber() #4 0x7f1b9d1e8125 WebCore::DataObject::createFromPasteboard() #5 0x7f1b9d397ea1 WebCore::Editor::dispatchCPPEvent() #6 0x7f1b9d39760a WebCore::Editor::tryDHTMLPaste() #7 0x7f1b9d39a26e WebCore::Editor::paste() #8 0x7f1b9d3a1216 WebCore::executePasteGlobalSelection() #9 0x7f1b9d3a2f62 WebCore::Editor::Command::execute() #10 0x7f1b9d5d929a WebCore::EventHandler::handlePasteGlobalSelection() #11 0x7f1b9d5d58d3 WebCore::EventHandler::handleMouseReleaseEvent() #12 0x7f1b9d5d90f4 WebCore::EventHandler::handleMouseReleaseEvent() #13 0x7f1b9cb4f7df blink::PageWidgetEventHandler::handleMouseUp() #14 0x7f1b9cbe70b1 blink::WebViewImpl::handleMouseUp() #15 0x7f1b9cb4f54d blink::PageWidgetDelegate::handleInputEvent() #16 0x7f1b9cbecd9a blink::WebViewImpl::handleInputEvent() #17 0x7f1b9f487469 content::RenderWidget::OnHandleInputEvent() #18 0x7f1b9f492b1a DispatchToMethod() #19 0x7f1b9f490755 InputMsg_HandleInputEvent::Dispatch() #20 0x7f1b9f483411 content::RenderWidget::OnMessageReceived() #21 0x7f1b9f454fbe content::RenderViewImpl::OnMessageReceived() #22 0x7f1b9a5c1a54 content::MessageRouter::RouteMessage() #23 0x7f1b9a5c19f8 content::MessageRouter::OnMessageReceived() #24 0x7f1b9f121a3f content::ChildThread::OnMessageReceived() #25 0x7f1b9f2c0a52 content::InputEventFilter::ForwardToMainListener() #26 0x7f1b9f2c1c13 base::internal::RunnableAdapter::Run() #27 0x7f1b9f2c1b84 base::internal::InvokeHelper::MakeItSo() #28 0x7f1b9f2c1b17 base::internal::Invoker::Run() #29 0x7f1b9a1c0ba8 base::Callback::Run() #30 0x7f1b9a26a95c base::MessageLoop::RunTask() #31 0x7f1b9a26aa8a base::MessageLoop::DeferOrRunPendingTask() #32 0x7f1b9a26afda base::MessageLoop::DoWork() #33 0x7f1b9a2798f1 base::MessagePumpDefault::Run() #34 0x7f1b9a26a450 base::MessageLoop::RunHandler() #35 0x7f1b9a2ce212 base::RunLoop::Run() #36 0x7f1b9a269a86 base::MessageLoop::Run() #37 0x7f1b9f4a0a24 content::RendererMain() #38 0x7f1b9a374655 content::RunZygote() #39 0x7f1b9a3748c9 content::RunNamedProcessTypeMain() #40 0x7f1b9a375765 content::ContentMainRunnerImpl::Run() #41 0x7f1b9a373db7 content::ContentMain() #42 0x7f1b9a117513 oxide::OxideMain() #43 0x004006dd main #44 0x7f1b992e8ec5 __libc_start_main #45 0x004005f9 unknown Received signal 6 #0 0x7f1b9a1d2803 base::debug::StackTrace::StackTrace() #1 0x7f1b9a1d20c2 base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x7f1b992fdff0 unknown #3 0x7f1b992fdf79 gsignal #4 0x7f1b99301388 abort #5 0x7f1b9a1cf3c8 base::debug::(anonymous namespace)::DebugBreak() #6 0x7f1b9a1cf3d4 base::debug::BreakDebugger() #7 0x7f1b9a24a361 logging::LogMessage::~LogMessage() #8 0x7f1b9f4d0340 content::WebClipboardImpl::ConvertBufferType() #9 0x7f1b9f4cf72e content::WebClipboardImpl::sequenceNumber() #10 0x7f1b9d1e8125 WebCore::DataObject::createFromPasteboard() #11 0x7f1b9d397ea1 WebCore::Editor::dispatchCPPEvent() #12 0x7f1b9d39760a WebCore::Editor::tryDHTMLPaste() #13 0x7f1b9d39a26e WebCore::Editor::paste() #14 0x7f1b9d3a1216 WebCore::executePasteGlobalSelection() #15 0x7f1b9d3a2f62 WebCore::Editor::Command::execute() #16 0x7f1b9d5d929a WebCore::EventHandler::handlePasteGlobalSelection() #17 0x7f1b9d5d58d3 WebCore::EventHandler::handleMouseReleaseEvent() #18 0x7f1b9d5d90f4 WebCore::EventHandler::handleMouseReleaseEvent() #19 0x7f1b9cb4f7df blink::PageWidgetEventHandler::handleMouseUp() #20 0x7f1b9cbe70b1 blink::WebViewImpl::handleMouseUp() #21 0x7f1b9cb4f54d blink::PageWidgetDelegate::handleInputEvent() #22 0x7f1b9cbecd9a
[Ubuntu-webapps-bugs] [Bug 1322622] Re: No rendering happens on a dynamically instantiated webview if its 'visible' property was changed
** Changed in: oxide/1.0 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1322622 Title: No rendering happens on a dynamically instantiated webview if its 'visible' property was changed Status in Oxide Webview: Fix Released Status in Oxide 1.0 series: Fix Released Bug description: Dynamically instantiating a webview in QML (using component.createObject(…)) without initially loading a URL, and ensuring it’s initially invisible then shown, and later loading a URL, results in no rendering. This can be worked around by then changing the 'visible' property to false and then true again. I’m attaching a small example that reproduces the issue. Note that it replicates webbrowser-app’s behaviour to deal with tabs, so it’s a pretty critical issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1322622/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1320848] Re: Add support for loadHtml()
** Changed in: oxide Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1320848 Title: Add support for loadHtml() Status in Oxide Webview: Fix Released Bug description: In some use cases, loading a website from an URL is not enough but a website needs to be loaded from memory. One example is the reminders app which loads notes in the ENML format and converts them to html just before putting it into the WebView. The upstream Qt WebView supports this use case by providing a loadHtml() method on the WebView. Would be great if Oxide could provide the same. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1320848/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1326697] [NEW] GN (Generate Ninja) is coming
Public bug reported: Google are currently working on a GYP replacement (GN) and are gradually adding support in Chromium for building various targets with the new tool. Eventually, GN will replace GYP entirely although the 2 will coexist in parallel until then. We should see if we can get the Oxide targets building with GN sooner rather than later ** Affects: oxide Importance: Medium Status: Triaged ** Changed in: oxide Importance: Undecided = Medium ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1326697 Title: GN (Generate Ninja) is coming Status in Oxide Webview: Triaged Bug description: Google are currently working on a GYP replacement (GN) and are gradually adding support in Chromium for building various targets with the new tool. Eventually, GN will replace GYP entirely although the 2 will coexist in parallel until then. We should see if we can get the Oxide targets building with GN sooner rather than later To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1326697/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1326852] Re: missing controls on toolbar of youtube videos
Would probably be good to have this in 1.0 as well ** Changed in: oxide Status: Triaged = Fix Released ** Changed in: webbrowser-app Status: New = Invalid ** Also affects: oxide/1.0 Importance: Undecided Status: New ** Changed in: oxide/1.0 Importance: Undecided = Critical ** Changed in: oxide/1.0 Status: New = Triaged ** Changed in: oxide/1.0 Milestone: None = 1.0.2 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1326852 Title: missing controls on toolbar of youtube videos Status in Oxide Webview: Fix Released Status in Oxide 1.0 series: Triaged Status in Web Browser App: Invalid Bug description: playback of youtube videos is now possible with this branch https://code.launchpad.net/~osomon/webbrowser-app/youtube-ua-override/+merge/222015 However the embedded youtube player is missing controls on it's toolbar for play/pause and for fullscreen. See the screenshots of oxide vs. chrome for Android to see what's missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1326852/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1307709] Re: webbrowser-app does not start in Unity 8 preview session
I think the reason this doesn't work is that the Mir EGL backend doesn't support pbuffer surfaces, and Chromium relies on this (although it doesn't actually draw to them - it creates a 1x1 pbuffer surface in order to bind the context) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide Webview: Fix Released Status in Web Browser App: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “unity8-desktop-session” package in Ubuntu: Invalid Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1307709] Re: webbrowser-app does not start in Unity 8 preview session
Oxide now works in Unity 8 desktop with these changes: http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/599 http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/600 http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/601 http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/602 http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/603 ** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide Webview: Fix Released Status in Web Browser App: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “unity8-desktop-session” package in Ubuntu: Invalid Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1327319] [NEW] r599 breaks resizing on Unity 7 desktop
Public bug reported: For some reason with r599, resizing a webview larger results in no rendering in the newly exposed contents on Unity 7 ** Affects: oxide Importance: High Assignee: Chris Coulson (chrisccoulson) Status: Triaged ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Confirmed ** Changed in: oxide Status: Confirmed = Triaged ** Changed in: oxide Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide Milestone: None = branch-1.1 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1327319 Title: r599 breaks resizing on Unity 7 desktop Status in Oxide Webview: Triaged Bug description: For some reason with r599, resizing a webview larger results in no rendering in the newly exposed contents on Unity 7 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1327319/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1331059] [NEW] Add PDF support in Oxide
Public bug reported: Chrome ships a binary PDF plugin, and Firefox has pdf.js which enables native PDF rendering inside both browsers. We should investigate adding native PDF rendering support in to Oxide - pdf.js would be preferred as it doesn't add new binary code ** Affects: oxide Importance: Low Status: Triaged ** Changed in: oxide Importance: Undecided = Low ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1331059 Title: Add PDF support in Oxide Status in Oxide Webview: Triaged Bug description: Chrome ships a binary PDF plugin, and Firefox has pdf.js which enables native PDF rendering inside both browsers. We should investigate adding native PDF rendering support in to Oxide - pdf.js would be preferred as it doesn't add new binary code To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1331059/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1323743] Re: keyboard doesn't display in webapps after some time
** Changed in: oxide Status: In Progress = Fix Released ** Changed in: oxide Milestone: None = branch-1.1 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1323743 Title: keyboard doesn't display in webapps after some time Status in Oxide Webview: Fix Released Status in Ubuntu Keyboard: In Progress Status in Web Browser App: In Progress Status in “ubuntu-keyboard” package in Ubuntu: In Progress Bug description: using build r48 maliit-framework 0.99.0+git20130615+97e8335-0ubuntu8 ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140515-0ubuntu1 webapp-container 0.23+14.10.20140522.1-0ubuntu1 I don't have the exact steps to reproduce the issue, but have run into a lot over the last few days of using the phone. - launch gmail webapp - launch twitter webapp - try and use both, doing things to cause the osk to display (like sending/replying to email, writing a tweet, etc) - click on links in gmail that cause the browser to be open - all works fine for a while - then do other things on phone, like launch other apps, open the browser app, suspend resume, use the carousel spread to switch between open apps (fast right edge swipe) - phone gets into a state where the osk is no longer displayed in the webapps no matter what you do The only way to get osk back in the webapp is to close the webapp and relaunch it. This fixes the webapp you relaunched but not others that are already open. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1323743/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1330511] Re: expose scroll-offset property and others on webview
** Changed in: oxide Status: New = Fix Released ** Changed in: oxide Milestone: None = branch-1.1 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1330511 Title: expose scroll-offset property and others on webview Status in Oxide Webview: Fix Released Bug description: this is needed to implement the newly designed header in the webbrowser-app and container To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1330511/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1252302] Re: Add support for devtools and remote debugging
** Changed in: oxide Status: In Progress = Fix Released ** Changed in: oxide Milestone: branch-1.2 = branch-1.1 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1252302 Title: Add support for devtools and remote debugging Status in Oxide Webview: Fix Released Bug description: A renderer process is always launched as introspectiable, and the devtools IPC channels always opened, so developerExtrasEnabled is not needed per-se, but it would be needed to have a better idea of how things are implemented and come up w/ a flexible mechanism for an equivalent of QTWEBKIT_INSPECTOR_SERVER (if possible) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1252302/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1332754] Re: Evict frames for hidden webviews
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1332754 Title: Evict frames for hidden webviews Status in Oxide Webview: Fix Released Bug description: When a webview is hidden we hold on to the frontbuffer until it is made visible again. Instead of doing this, we should consider evicting all buffers for hidden views in order to free resources. A tradeoff of this would be small delay when making a hidden view visible again. On Android, Chrome evicts frames for all hidden views. On destkop, it doesn't evict all of them but does cap the number based on available memory To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1332754/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1323743] Re: keyboard doesn't display in webapps after some time
Backed this out for now. Michael, would you mind taking a look at that crash please? ** Changed in: oxide Status: Fix Released = In Progress ** Changed in: oxide Assignee: (unassigned) = Michael Sheldon (michael-sheldon) ** Changed in: oxide Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1323743 Title: keyboard doesn't display in webapps after some time Status in Oxide Webview: In Progress Status in Ubuntu Keyboard: In Progress Status in Web Browser App: In Progress Status in “ubuntu-keyboard” package in Ubuntu: In Progress Bug description: using build r48 maliit-framework 0.99.0+git20130615+97e8335-0ubuntu8 ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140515-0ubuntu1 webapp-container 0.23+14.10.20140522.1-0ubuntu1 I don't have the exact steps to reproduce the issue, but have run into a lot over the last few days of using the phone. - launch gmail webapp - launch twitter webapp - try and use both, doing things to cause the osk to display (like sending/replying to email, writing a tweet, etc) - click on links in gmail that cause the browser to be open - all works fine for a while - then do other things on phone, like launch other apps, open the browser app, suspend resume, use the carousel spread to switch between open apps (fast right edge swipe) - phone gets into a state where the osk is no longer displayed in the webapps no matter what you do The only way to get osk back in the webapp is to close the webapp and relaunch it. This fixes the webapp you relaunched but not others that are already open. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1323743/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1323743] Re: keyboard doesn't display in webapps after some time
** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1323743 Title: keyboard doesn't display in webapps after some time Status in Oxide Webview: Fix Released Status in Ubuntu Keyboard: In Progress Status in Web Browser App: In Progress Status in “ubuntu-keyboard” package in Ubuntu: In Progress Bug description: using build r48 maliit-framework 0.99.0+git20130615+97e8335-0ubuntu8 ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140515-0ubuntu1 webapp-container 0.23+14.10.20140522.1-0ubuntu1 I don't have the exact steps to reproduce the issue, but have run into a lot over the last few days of using the phone. - launch gmail webapp - launch twitter webapp - try and use both, doing things to cause the osk to display (like sending/replying to email, writing a tweet, etc) - click on links in gmail that cause the browser to be open - all works fine for a while - then do other things on phone, like launch other apps, open the browser app, suspend resume, use the carousel spread to switch between open apps (fast right edge swipe) - phone gets into a state where the osk is no longer displayed in the webapps no matter what you do The only way to get osk back in the webapp is to close the webapp and relaunch it. This fixes the webapp you relaunched but not others that are already open. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1323743/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1312081] Re: Kill RenderViewItem, and move contents to the WebView instead
** Changed in: oxide Status: Triaged = Fix Released ** Changed in: oxide Milestone: None = branch-1.1 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1312081 Title: Kill RenderViewItem, and move contents to the WebView instead Status in Oxide Webview: Fix Released Bug description: WebView is currently a QQuickItem with no contents and no event handling. Contents and event handling are provided by child QQuickItem's (RenderViewItem), which have a corresponding RenderWidgetHostView. This is analogous to Chromium Aura, where each RenderWidgetHostView has a corresponding aura::Window. However, we should try to get rid of these child QQuickItem's. WebView should provide contents and event handling itself, and we should stop subclassing RenderWidgetHostView in qt/core. This would allow us to have a browser-side compositor for the webview, much like ContentViewCore / ContentViewRenderView on Android To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1312081/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1244373] Re: screen blanks during video playback
** Changed in: oxide Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1244373 Title: screen blanks during video playback Status in Oxide Webview: Fix Released Status in The Webapps-core project: New Status in Web Browser App: Invalid Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: Title says it all. If I play a movie trailer in the rotten tomatoes webapp (for example), after a few seconds the screen blanks. How this is fixed may affect application confinement policy since webapps are confined and currently there is not a policy group that allows inhibiting screen blanking. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1244373/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1336440] [NEW] Stop using mercurial patch queues
Public bug reported: We currently have a fairly gross hack during checkout where we create a mercurial repository of the whole checkout in order to use mq to manage the patches we apply to Chromium. The reason for this is that the interface is a bit better than quilt (you don't have to do quilt add, for example), and mq is available on all distro's and all major platforms (quilt isn't). However, using mercurial in this way has some major downsides: - It's using a lot of disk space - Whilst creating the repository is fast on my machine, it's taking up to an hour in canonistack We should drop this for now and switch to quilt. A consequence of this is that it will only be possible to check the code out on linux. That kind of sucks, although I'm not sure it matters too much at the moment. ** Affects: oxide Importance: High Status: Triaged ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1336440 Title: Stop using mercurial patch queues Status in Oxide Webview: Triaged Bug description: We currently have a fairly gross hack during checkout where we create a mercurial repository of the whole checkout in order to use mq to manage the patches we apply to Chromium. The reason for this is that the interface is a bit better than quilt (you don't have to do quilt add, for example), and mq is available on all distro's and all major platforms (quilt isn't). However, using mercurial in this way has some major downsides: - It's using a lot of disk space - Whilst creating the repository is fast on my machine, it's taking up to an hour in canonistack We should drop this for now and switch to quilt. A consequence of this is that it will only be possible to check the code out on linux. That kind of sucks, although I'm not sure it matters too much at the moment. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1336440/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1327241] Re: Crash on devices when inputing characters with the OSK
** Changed in: oxide/1.0 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1327241 Title: Crash on devices when inputing characters with the OSK Status in Oxide Webview: Fix Released Status in Oxide 1.0 series: Fix Released Bug description: This happens with a recent version of oxide built from lp:oxide. When tested on a device to input text in a text field, the client process crashes with the following backtrace: #0 0xb6dda5c6 in QEvent::QEvent(QEvent const) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #1 0xae4241ba in content::NativeWebKeyboardEvent::NativeWebKeyboardEvent(content::NativeWebKeyboardEvent const) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #2 0xafaca89e in content::InputRouterImpl::SendKeyboardEvent(content::NativeWebKeyboardEvent const, ui::LatencyInfo const, bool) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #3 0xafb17c58 in content::RenderWidgetHostImpl::ForwardKeyboardEvent(content::NativeWebKeyboardEvent const) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #4 0xae425d4c in oxide::qt::sendFakeCompositionKeyEvent(content::RenderWidgetHostImpl*, blink::WebInputEvent::Type) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #5 0xae427678 in oxide::qt::RenderWidgetHostView::HandleInputMethodEvent(QInputMethodEvent*) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #6 0xb661dfde in QQuickItem::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 #7 0xb616d8a0 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 #8 0xb617136e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 The crash is happening in gfx::NativeEvent CopyEvent(gfx::NativeEvent event). Because os_event is 0, we dereference a null pointer in the copy constructor for NativeWebKeyboardEvent. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1327241/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1326852] Re: missing controls on toolbar of youtube videos
** Changed in: oxide/1.0 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1326852 Title: missing controls on toolbar of youtube videos Status in Oxide Webview: Fix Released Status in Oxide 1.0 series: Fix Released Status in Web Browser App: Invalid Bug description: playback of youtube videos is now possible with this branch https://code.launchpad.net/~osomon/webbrowser-app/youtube-ua-override/+merge/222015 However the embedded youtube player is missing controls on it's toolbar for play/pause and for fullscreen. See the screenshots of oxide vs. chrome for Android to see what's missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1326852/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1328000] Re: return key doesn’t validate the active form
** Changed in: oxide/1.0
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1328000
Title:
return key doesn’t validate the active form
Status in Oxide Webview:
Fix Released
Status in Oxide 1.0 series:
Fix Released
Bug description:
This is a regression observed with the latest trunk (the last release,
based on revision 501, doesn’t exhibit this behaviour).
Run the following simple QML scene with qmlscene:
import QtQuick 2.0
import com.canonical.Oxide 1.0
WebView {
width: 800
height: 600
url: http://start.ubuntu.com;
}
Focus the search box, enter any number of characters, then press the
return key.
Expected result: the search is triggered and the results page starts loading
Current result: nothing happens
I can reliably reproduce the issue both on desktop (x86-64) with a
physical keyboard and on a Nexus 7 with the OSK.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1328000/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1284158] Re: http://chrome.angrybirds.com/ doesn't work, but it should
Added a webbrowser-app task for this, as I only get a Get the android version screen when viewing this on the device (I guess it'll need a user agent override). That won't fix the other issues with the game the last time I tried it though, but it would be great to get this working ** Also affects: webbrowser-app Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1284158 Title: http://chrome.angrybirds.com/ doesn't work, but it should Status in Oxide Webview: Triaged Status in Web Browser App: New Bug description: Go to http://chrome.angrybirds.com/. Since this is an HTML5 game for chrome, it should work, but doesn't load. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1284158/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337338] Re: Crash on armhf when starting playback of an embedded video
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337338 Title: Crash on armhf when starting playback of an embedded video Status in Oxide Webview: Fix Released Bug description: Testing webbrowser-app with the latest oxide built from trunk on a N7, going to youtube.com and trying to play back any video triggers the following crash: #0 0xaf890cca in content::RenderWidgetHostImpl::WasHidden() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #1 0xae1c1cca in oxide::RenderWidgetHostView::WasHidden() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #2 0xae1c1ea6 in oxide::RenderWidgetHostView::~RenderWidgetHostView() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #3 0xae1c1fd8 in oxide::RenderWidgetHostView::~RenderWidgetHostView() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #4 0xaf891046 in content::RenderWidgetHostImpl::RendererExited(base::TerminationStatus, int) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #5 0xaf885e18 in content::RenderViewHostImpl::OnRenderProcessGone(int, int) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #6 0xaf88c8be in content::RenderViewHostImpl::OnMessageReceived(IPC::Message const) [clone .part.209] () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #7 0xaf884b96 in content::RenderProcessHostImpl::ProcessDied(bool) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #8 0xae2053de in base::MessageLoop::RunTask(base::PendingTask const) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #9 0xae20596e in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #10 0xae20779c in base::MessageLoop::DoWork() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #11 0xae1a34ec in oxide::qt::MessagePump::customEvent(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #12 0xb6de6064 in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #13 0xb60c79a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 #14 0xb60cb13a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Cannot access memory at address 0x2d4ff0e0 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337506] [NEW] FATAL:texture_manager.cc(76)] Check failed: texture_count_ == 0u (1 vs. 0)
Public bug reported: I'm hitting this runtime abort occasionally on shutdown: [0703/194533:FATAL:texture_manager.cc(76)] Check failed: texture_count_ == 0u (1 vs. 0) ** Affects: oxide Importance: High Status: Triaged ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Importance: Undecided = Medium ** Changed in: oxide Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337506 Title: FATAL:texture_manager.cc(76)] Check failed: texture_count_ == 0u (1 vs. 0) Status in Oxide Webview: Triaged Bug description: I'm hitting this runtime abort occasionally on shutdown: [0703/194533:FATAL:texture_manager.cc(76)] Check failed: texture_count_ == 0u (1 vs. 0) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337506/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337890] Re: Failure to inhibit screen blanking, powerd D-Bus API has changed
** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Milestone: None = branch-1.2 ** Also affects: oxide/1.1 Importance: Undecided Status: New ** Changed in: oxide/1.1 Milestone: None = 1.1.0 ** Changed in: oxide/1.1 Importance: Undecided = High ** Changed in: oxide/1.1 Assignee: (unassigned) = Olivier Tilloy (osomon) ** Changed in: oxide/1.1 Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337890 Title: Failure to inhibit screen blanking, powerd D-Bus API has changed Status in Oxide Webview: In Progress Status in Oxide 1.1 series: Triaged Bug description: Testing oxide 1.1.0 from the phablet-team PPA, while playing back a video screen blanking happens, and I’m seeing the following message in the log: [0704/163250:ERROR:object_proxy.cc(566)] Failed to call method: com.canonical.powerd.requestDisplayState: object_path= /com/canonical/powerd: org.freedesktop.DBus.Error.UnknownMethod: No such method 'requestDisplayState' [0704/163250:ERROR:oxide_power_save_blocker.cc(116)] Failed to inhibit screen blanking It appears the display handling was removed from powerd in version 0.16+14.10.20140620-0ubuntu1, apparently we should now invoke the unity D-Bus API for this: com.canonical.Unity.Screen /com/canonical/Unity/Screen com.canonical.Unity.Screen keepDisplayOn() - int cookie removeDisplayOnRequest(int cookie) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337890/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1286204] Re: Make double-tap-to-zoom work
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1286204 Title: Make double-tap-to-zoom work Status in Oxide Webview: Fix Released Status in Web Browser App: Confirmed Bug description: pinch to zoom: seems to be working pretty well. one thing that is missing is double tapping in a region should zoom in/zoom out. currently double tapping selects the word underneath. For feature parity, we'd need this as it's supported in qtwebkit today To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1286204/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1332996] Re: QtCreator often halts for a minute
This is because qmlplugindump selections the minimal Qt platform, which doesn't implement QPlatformNativeInterface, which we depend on for getting the native display handle ** Also affects: oxide Importance: Undecided Status: New ** Changed in: oxide Importance: Undecided = Medium ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1332996 Title: QtCreator often halts for a minute Status in Oxide Webview: Triaged Status in “oxide-qt” package in Ubuntu: Confirmed Bug description: When QtCreator re-indexes, it halts all input for a minute. So I can't write code, navigate, ... This is every 10 minutes or so and is very anoying. General messages then contains: QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/CordovaUbuntu.2.8 See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/CordovaUbuntu.2.8 QQmlComponent: Component is not ready Warnings while parsing QML type information of /usr/lib/x86_64-linux-gnu/unity8/qml/Dash: Failed to parse '/usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes'. Error: /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:82:19: Expected string literal to contain 'Package/Name major.minor' or 'Name major.minor'. /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:83:36: Expected array literal with only number literal members. QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump crashed. Arguments: -relocatable com.canonical.Oxide 1.0 /usr/lib/x86_64-linux-gnu/qt5/qml [0622/184656:ERROR:gl_implementation_osmesa.cc(22)] Failed to load /usr/lib/x86_64-linux-gnu/oxide-qt/libosmesa.so: /usr/lib/x86_64-linux-gnu/oxide-qt/libosmesa.so: kan gedeeld objectbestand niet openen: Bestand of map bestaat niet So qmlplugindump fails to load /usr/lib/x86_64-linux-gnu/oxide- qt/libosmesa.so as it's not existing. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: liboxideqtcore0 1.0.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 18:58:16 2014 InstallationDate: Installed on 2012-02-02 (870 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: oxide-qt UpgradeStatus: Upgraded to utopic on 2014-05-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1332996/+subscriptions -- Mailing list:
[Ubuntu-webapps-bugs] [Bug 1332996] Re: QtCreator often halts for a minute
** Changed in: oxide Milestone: None = branch-1.2 ** Also affects: oxide/1.1 Importance: Undecided Status: New ** Changed in: oxide/1.1 Milestone: None = 1.1.0 ** Changed in: oxide/1.1 Importance: Undecided = Medium ** Changed in: oxide/1.1 Status: New = Triaged ** Changed in: oxide Status: Triaged = Fix Released ** Changed in: oxide/1.1 Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide-qt (Ubuntu) Assignee: Zoltan Balogh (bzoltan) = (unassigned) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1332996 Title: QtCreator often halts for a minute Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Triaged Status in “oxide-qt” package in Ubuntu: Confirmed Bug description: When QtCreator re-indexes, it halts all input for a minute. So I can't write code, navigate, ... This is every 10 minutes or so and is very anoying. General messages then contains: QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/CordovaUbuntu.2.8 See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/CordovaUbuntu.2.8 QQmlComponent: Component is not ready Warnings while parsing QML type information of /usr/lib/x86_64-linux-gnu/unity8/qml/Dash: Failed to parse '/usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes'. Error: /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:82:19: Expected string literal to contain 'Package/Name major.minor' or 'Name major.minor'. /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:83:36: Expected array literal with only number literal members. QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump crashed. Arguments: -relocatable com.canonical.Oxide 1.0 /usr/lib/x86_64-linux-gnu/qt5/qml [0622/184656:ERROR:gl_implementation_osmesa.cc(22)] Failed to load /usr/lib/x86_64-linux-gnu/oxide-qt/libosmesa.so: /usr/lib/x86_64-linux-gnu/oxide-qt/libosmesa.so: kan gedeeld objectbestand niet openen: Bestand of map bestaat niet So qmlplugindump fails to load /usr/lib/x86_64-linux-gnu/oxide- qt/libosmesa.so as it's not existing. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: liboxideqtcore0 1.0.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 18:58:16 2014 InstallationDate: Installed on 2012-02-02 (870 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage
[Ubuntu-webapps-bugs] [Bug 1338639] Re: Oxide segfault in reminders app
Do you want to merge this in to the 1.1 branch too? ** Also affects: oxide/1.1 Importance: Undecided Status: New ** Changed in: oxide/1.1 Milestone: None = 1.1.0 ** Changed in: oxide/1.1 Importance: Undecided = High ** Changed in: oxide/1.1 Status: New = Triaged ** Changed in: oxide/1.1 Assignee: (unassigned) = Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1338639 Title: Oxide segfault in reminders app Status in Oxide Webview: Fix Committed Status in Oxide 1.1 series: Triaged Bug description: I started to migrare reminders-app to Oxide[1]. It works well in tablet mode, but in phone mode there is a segfault when I try to open a note (Oxide is used to display notes). The difference between tablet mode and phone mode is that in tablet mode the note is loaded in a sideview, in phone mode the note is pushed on top of a pagestack. I'm not able (yet) to reproduce the crash outside the reminders-app, but I don't understand why it crashes so bad. Also, gdb says it's something about loadHtml() function: http://paste.ubuntu.com/7760088/ (sorry, I don't which signals I miss, if necessary I'll install more packages) Please tell me if I could help to give you others informations! [1]https://code.launchpad.net/~rpadovani/reminders- app/upgradeToOxide/+merge/225737 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1338639/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337389] Re: The prototype to ContentBrowserClient::CanCreateWindow() has changed
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337389 Title: The prototype to ContentBrowserClient::CanCreateWindow() has changed Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Triaged Bug description: The is_guest parameter has been removed, so our implementation is never called. This doesn't break popup blocking though because we also set a preferences on the renderer side to reject them. This is really an extra layer of safety. This was picked up with a build against canary, which seems to enable C++11 (so we get final and override keywords) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337389/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1341565] [NEW] Should include plugin typeinfo (plugins.qmltypes)
Public bug reported: Spun off from bug 1332996, we should dump the plugin types to plugins.qmltypes and install that to avoid needless calls to qmlplugindump ** Affects: oxide Importance: Low Status: Triaged ** Changed in: oxide Importance: Undecided = Low ** Changed in: oxide Status: New = Triaged ** Description changed: - Spun off from bug 1332996), we should dump the plugin types to + Spun off from bug 1332996, we should dump the plugin types to plugins.qmltypes and install that to avoid needless calls to qmlplugindump -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1341565 Title: Should include plugin typeinfo (plugins.qmltypes) Status in Oxide Webview: Triaged Bug description: Spun off from bug 1332996, we should dump the plugin types to plugins.qmltypes and install that to avoid needless calls to qmlplugindump To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1341565/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1342685] [NEW] tst_NewViewRequested.qml fails on some multimonitor configurations
Public bug reported: I made a change to my monitor setup this morning which inadvertently changed my primary screen. After this, tst_NewViewRequested.qml began failing: PASS : qml-api-test-noprofile::NewViewRequest::initTestCase() [0716/124936:WARNING:raw_channel_posix.cc(214)] recvmsg: Connection reset by peer [0716/124936:ERROR:renderer_main.cc(227)] Running without renderer sandbox 127.0.0.1 - - [16/Jul/2014 12:49:36] GET /tst_NewViewRequest.html HTTP/1.1 200 - 127.0.0.1 - - [16/Jul/2014 12:49:36] GET /empty.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 0) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:36] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 1) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:36] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 2) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:36] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 3) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:36] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 4) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:37] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 5) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:37] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 6) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:37] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 7) Unexpected position.x Actual (): 1600 Expected (): 100 Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/api/tst_NewViewRequest.qml(93)] 127.0.0.1 - - [16/Jul/2014 12:49:37] GET /tst_NewViewRequest.html HTTP/1.1 200 - PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 8) 127.0.0.1 - - [16/Jul/2014 12:49:37] GET /tst_NewViewRequest.html HTTP/1.1 200 - PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 9) 127.0.0.1 - - [16/Jul/2014 12:49:37] GET /tst_NewViewRequest.html HTTP/1.1 200 - PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 10) 127.0.0.1 - - [16/Jul/2014 12:49:38] GET /tst_NewViewRequest.html HTTP/1.1 200 - PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 11) 127.0.0.1 - - [16/Jul/2014 12:49:38] GET /tst_NewViewRequest.html HTTP/1.1 200 - PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 12) [0716/124938:ERROR:renderer_main.cc(227)] Running without renderer sandbox PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 13) 127.0.0.1 - - [16/Jul/2014 12:49:38] GET /tst_NewViewRequest.html HTTP/1.1 200 - [0716/124938:ERROR:renderer_main.cc(227)] Running without renderer sandbox PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 14) 127.0.0.1 - - [16/Jul/2014 12:49:38] GET /tst_NewViewRequest.html HTTP/1.1 200 - PASS : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest1_from_user_gesture(row 15) [0716/124939:ERROR:renderer_main.cc(227)] Running without renderer sandbox 127.0.0.1 - - [16/Jul/2014 12:49:39] GET /tst_NewViewRequest.html HTTP/1.1 200 - FAIL! : qml-api-test-noprofile::NewViewRequest::test_NewViewRequest2_no_user_gesture(row 0) Unexpected position.x Actual (): 1600 Expected (): 100 Loc:
[Ubuntu-webapps-bugs] [Bug 1347892] [NEW] Consider defaulting WebPreferences.allowFileAccessFromFileUrls to true
Public bug reported: This currently defaults to false, which I'm not sure is that sane. The default means that 2 files are treated as being from a different origin if they don't have exactly the same path ** Affects: oxide Importance: Low Status: Triaged ** Changed in: oxide Importance: Undecided = Low ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1347892 Title: Consider defaulting WebPreferences.allowFileAccessFromFileUrls to true Status in Oxide Webview: Triaged Bug description: This currently defaults to false, which I'm not sure is that sane. The default means that 2 files are treated as being from a different origin if they don't have exactly the same path To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1347892/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337338] Re: Crash on armhf when starting playback of an embedded video
It's the same crash, because the fix hasn't been uploaded in to the distro yet. Adding an Ubuntu task ** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: oxide-qt (Ubuntu) Importance: Undecided = High ** Changed in: oxide-qt (Ubuntu) Status: New = Triaged ** Changed in: oxide Status: Confirmed = Fix Released ** Changed in: oxide Milestone: None = branch-1.1 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337338 Title: Crash on armhf when starting playback of an embedded video Status in Oxide Webview: Fix Released Status in “oxide-qt” package in Ubuntu: Triaged Bug description: Testing webbrowser-app with the latest oxide built from trunk on a N7, going to youtube.com and trying to play back any video triggers the following crash: #0 0xaf890cca in content::RenderWidgetHostImpl::WasHidden() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #1 0xae1c1cca in oxide::RenderWidgetHostView::WasHidden() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #2 0xae1c1ea6 in oxide::RenderWidgetHostView::~RenderWidgetHostView() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #3 0xae1c1fd8 in oxide::RenderWidgetHostView::~RenderWidgetHostView() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #4 0xaf891046 in content::RenderWidgetHostImpl::RendererExited(base::TerminationStatus, int) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #5 0xaf885e18 in content::RenderViewHostImpl::OnRenderProcessGone(int, int) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #6 0xaf88c8be in content::RenderViewHostImpl::OnMessageReceived(IPC::Message const) [clone .part.209] () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #7 0xaf884b96 in content::RenderProcessHostImpl::ProcessDied(bool) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #8 0xae2053de in base::MessageLoop::RunTask(base::PendingTask const) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #9 0xae20596e in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #10 0xae20779c in base::MessageLoop::DoWork() () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #11 0xae1a34ec in oxide::qt::MessagePump::customEvent(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0 #12 0xb6de6064 in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #13 0xb60c79a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 #14 0xb60cb13a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Cannot access memory at address 0x2d4ff0e0 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337338/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1349510] Re: browser crashes when attaching photo in gmail
The browser crash is bug 1337338, but the real problem here is that the renderer is terminated because it sent a message that can't be serialized (from comment 2): [0728/131359:ERROR:render_process_host_impl.cc(1437)] bad message 65594 terminating renderer. Message 65594 is OxideHostMsg_GetUserAgentOverride. My guess is that the renderer is sending a URL that exceeds 2*1024*1024 characters, which is the limit at which the GURL ParamTraits specialization will fail to serialize the url parameter required for determining the navigator.userAgent override for the page ** Changed in: webbrowser-app Status: Confirmed = Invalid ** Changed in: oxide Importance: Undecided = Critical ** Changed in: oxide Status: Confirmed = Triaged ** Changed in: oxide Milestone: None = branch-1.2 ** Changed in: content-hub Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1349510 Title: browser crashes when attaching photo in gmail Status in Content sharing/picking infrastructure and service: Invalid Status in Oxide Webview: Triaged Status in Web Browser App: Invalid Bug description: build 154 - Save the attached photo in the bug into your ~Pictures directory on the phone - Open gmail in the browser (or as a webbapp, doesn't make a different) - Compose a new gmail message - press the attach button - select the photo under test in the gallery - the browser is shown briefly then crashes NOTE: the browser only seems to crash with a bunch of photos that I copied to the device, all of their size is 2.1mb. So it may be size related. Or noticing now the orientation of the photo appears rotated when viewing on the desktop, so maybe something about the orientation? Photos taken with the camera work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/content-hub/+bug/1349510/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1347924] Re: deadlock in oxide after invoking some (unrelated)c++/qt functions
This seems to do the trick: http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/666 ** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1347924 Title: deadlock in oxide after invoking some (unrelated)c++/qt functions Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Triaged Bug description: attachment contains simple reproduction app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1347924/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1338639] Re: Oxide segfault in reminders app
** Changed in: oxide Status: Fix Committed = Fix Released ** Changed in: oxide/1.1 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1338639 Title: Oxide segfault in reminders app Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Fix Released Bug description: I started to migrare reminders-app to Oxide[1]. It works well in tablet mode, but in phone mode there is a segfault when I try to open a note (Oxide is used to display notes). The difference between tablet mode and phone mode is that in tablet mode the note is loaded in a sideview, in phone mode the note is pushed on top of a pagestack. I'm not able (yet) to reproduce the crash outside the reminders-app, but I don't understand why it crashes so bad. Also, gdb says it's something about loadHtml() function: http://paste.ubuntu.com/7760088/ (sorry, I don't which signals I miss, if necessary I'll install more packages) Please tell me if I could help to give you others informations! [1]https://code.launchpad.net/~rpadovani/reminders- app/upgradeToOxide/+merge/225737 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1338639/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337890] Re: Failure to inhibit screen blanking, powerd D-Bus API has changed
** Changed in: oxide/1.1 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337890 Title: Failure to inhibit screen blanking, powerd D-Bus API has changed Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Fix Released Bug description: Testing oxide 1.1.0 from the phablet-team PPA, while playing back a video screen blanking happens, and I’m seeing the following message in the log: [0704/163250:ERROR:object_proxy.cc(566)] Failed to call method: com.canonical.powerd.requestDisplayState: object_path= /com/canonical/powerd: org.freedesktop.DBus.Error.UnknownMethod: No such method 'requestDisplayState' [0704/163250:ERROR:oxide_power_save_blocker.cc(116)] Failed to inhibit screen blanking It appears the display handling was removed from powerd in version 0.16+14.10.20140620-0ubuntu1, apparently we should now invoke the unity D-Bus API for this: com.canonical.Unity.Screen /com/canonical/Unity/Screen com.canonical.Unity.Screen keepDisplayOn() - int cookie removeDisplayOnRequest(int cookie) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337890/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1300694] Re: Middle click to paste text from clipboard into form crashes the renderer
I believe this crash was actually fixed by http://src.chromium.org/viewvc/chrome?view=revisionrevision=263420 ** Changed in: oxide Status: Triaged = Incomplete ** Changed in: oxide Status: Incomplete = Fix Released ** Changed in: oxide/1.0 Status: Triaged = Fix Released ** Changed in: oxide/1.0 Milestone: 1.0.4 = None ** Changed in: oxide/1.1 Status: Triaged = Fix Released ** Changed in: oxide/1.1 Milestone: 1.1.0 = None -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1300694 Title: Middle click to paste text from clipboard into form crashes the renderer Status in Oxide Webview: Fix Released Status in Oxide 1.0 series: Fix Released Status in Oxide 1.1 series: Fix Released Bug description: On desktop, instantiate a WebView and point it to e.g. http://google.com, select some text in another application, then middle-click in the search box in the webview to paste the selected text. This crashes the renderer process with the following stack trace: [0401/120700:FATAL:webclipboard_impl.cc(217)] Check failed: false. #0 0x7f1b9a1d2803 base::debug::StackTrace::StackTrace() #1 0x7f1b9a24a011 logging::LogMessage::~LogMessage() #2 0x7f1b9f4d0340 content::WebClipboardImpl::ConvertBufferType() #3 0x7f1b9f4cf72e content::WebClipboardImpl::sequenceNumber() #4 0x7f1b9d1e8125 WebCore::DataObject::createFromPasteboard() #5 0x7f1b9d397ea1 WebCore::Editor::dispatchCPPEvent() #6 0x7f1b9d39760a WebCore::Editor::tryDHTMLPaste() #7 0x7f1b9d39a26e WebCore::Editor::paste() #8 0x7f1b9d3a1216 WebCore::executePasteGlobalSelection() #9 0x7f1b9d3a2f62 WebCore::Editor::Command::execute() #10 0x7f1b9d5d929a WebCore::EventHandler::handlePasteGlobalSelection() #11 0x7f1b9d5d58d3 WebCore::EventHandler::handleMouseReleaseEvent() #12 0x7f1b9d5d90f4 WebCore::EventHandler::handleMouseReleaseEvent() #13 0x7f1b9cb4f7df blink::PageWidgetEventHandler::handleMouseUp() #14 0x7f1b9cbe70b1 blink::WebViewImpl::handleMouseUp() #15 0x7f1b9cb4f54d blink::PageWidgetDelegate::handleInputEvent() #16 0x7f1b9cbecd9a blink::WebViewImpl::handleInputEvent() #17 0x7f1b9f487469 content::RenderWidget::OnHandleInputEvent() #18 0x7f1b9f492b1a DispatchToMethod() #19 0x7f1b9f490755 InputMsg_HandleInputEvent::Dispatch() #20 0x7f1b9f483411 content::RenderWidget::OnMessageReceived() #21 0x7f1b9f454fbe content::RenderViewImpl::OnMessageReceived() #22 0x7f1b9a5c1a54 content::MessageRouter::RouteMessage() #23 0x7f1b9a5c19f8 content::MessageRouter::OnMessageReceived() #24 0x7f1b9f121a3f content::ChildThread::OnMessageReceived() #25 0x7f1b9f2c0a52 content::InputEventFilter::ForwardToMainListener() #26 0x7f1b9f2c1c13 base::internal::RunnableAdapter::Run() #27 0x7f1b9f2c1b84 base::internal::InvokeHelper::MakeItSo() #28 0x7f1b9f2c1b17 base::internal::Invoker::Run() #29 0x7f1b9a1c0ba8 base::Callback::Run() #30 0x7f1b9a26a95c base::MessageLoop::RunTask() #31 0x7f1b9a26aa8a base::MessageLoop::DeferOrRunPendingTask() #32 0x7f1b9a26afda base::MessageLoop::DoWork() #33 0x7f1b9a2798f1 base::MessagePumpDefault::Run() #34 0x7f1b9a26a450 base::MessageLoop::RunHandler() #35 0x7f1b9a2ce212 base::RunLoop::Run() #36 0x7f1b9a269a86 base::MessageLoop::Run() #37 0x7f1b9f4a0a24 content::RendererMain() #38 0x7f1b9a374655 content::RunZygote() #39 0x7f1b9a3748c9 content::RunNamedProcessTypeMain() #40 0x7f1b9a375765 content::ContentMainRunnerImpl::Run() #41 0x7f1b9a373db7 content::ContentMain() #42 0x7f1b9a117513 oxide::OxideMain() #43 0x004006dd main #44 0x7f1b992e8ec5 __libc_start_main #45 0x004005f9 unknown Received signal 6 #0 0x7f1b9a1d2803 base::debug::StackTrace::StackTrace() #1 0x7f1b9a1d20c2 base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x7f1b992fdff0 unknown #3 0x7f1b992fdf79 gsignal #4 0x7f1b99301388 abort #5 0x7f1b9a1cf3c8 base::debug::(anonymous namespace)::DebugBreak() #6 0x7f1b9a1cf3d4 base::debug::BreakDebugger() #7 0x7f1b9a24a361 logging::LogMessage::~LogMessage() #8 0x7f1b9f4d0340 content::WebClipboardImpl::ConvertBufferType() #9 0x7f1b9f4cf72e content::WebClipboardImpl::sequenceNumber() #10 0x7f1b9d1e8125 WebCore::DataObject::createFromPasteboard() #11 0x7f1b9d397ea1 WebCore::Editor::dispatchCPPEvent() #12 0x7f1b9d39760a WebCore::Editor::tryDHTMLPaste() #13 0x7f1b9d39a26e WebCore::Editor::paste() #14 0x7f1b9d3a1216 WebCore::executePasteGlobalSelection() #15 0x7f1b9d3a2f62 WebCore::Editor::Command::execute() #16 0x7f1b9d5d929a WebCore::EventHandler::handlePasteGlobalSelection() #17 0x7f1b9d5d58d3 WebCore::EventHandler::handleMouseReleaseEvent() #18 0x7f1b9d5d90f4 WebCore::EventHandler::handleMouseReleaseEvent() #19 0x7f1b9cb4f7df blink::PageWidgetEventHandler::handleMouseUp() #20 0x7f1b9cbe70b1 blink::WebViewImpl::handleMouseUp() #21 0x7f1b9cb4f54d
[Ubuntu-webapps-bugs] [Bug 1332996] Re: QtCreator often halts for a minute
** Changed in: oxide/1.1 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1332996 Title: QtCreator often halts for a minute Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Fix Released Status in “oxide-qt” package in Ubuntu: Confirmed Bug description: When QtCreator re-indexes, it halts all input for a minute. So I can't write code, navigate, ... This is every 10 minutes or so and is very anoying. General messages then contains: QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/CordovaUbuntu.2.8 See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/CordovaUbuntu.2.8 QQmlComponent: Component is not ready Warnings while parsing QML type information of /usr/lib/x86_64-linux-gnu/unity8/qml/Dash: Failed to parse '/usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes'. Error: /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:82:19: Expected string literal to contain 'Package/Name major.minor' or 'Name major.minor'. /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:83:36: Expected array literal with only number literal members. QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump returned exit code 3. Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web QQmlComponent: Component is not ready QML module does not contain information about components contained in plugins. Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide See Using QML Modules with Plugins in the documentation. Automatic type dump of QML module failed. Errors: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump crashed. Arguments: -relocatable com.canonical.Oxide 1.0 /usr/lib/x86_64-linux-gnu/qt5/qml [0622/184656:ERROR:gl_implementation_osmesa.cc(22)] Failed to load /usr/lib/x86_64-linux-gnu/oxide-qt/libosmesa.so: /usr/lib/x86_64-linux-gnu/oxide-qt/libosmesa.so: kan gedeeld objectbestand niet openen: Bestand of map bestaat niet So qmlplugindump fails to load /usr/lib/x86_64-linux-gnu/oxide- qt/libosmesa.so as it's not existing. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: liboxideqtcore0 1.0.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 22 18:58:16 2014 InstallationDate: Installed on 2012-02-02 (870 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: oxide-qt UpgradeStatus: Upgraded to utopic on 2014-05-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1332996/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1337389] Re: The prototype to ContentBrowserClient::CanCreateWindow() has changed
** Changed in: oxide/1.1 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1337389 Title: The prototype to ContentBrowserClient::CanCreateWindow() has changed Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Fix Released Bug description: The is_guest parameter has been removed, so our implementation is never called. This doesn't break popup blocking though because we also set a preferences on the renderer side to reject them. This is really an extra layer of safety. This was picked up with a build against canary, which seems to enable C++11 (so we get final and override keywords) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1337389/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1349510] Re: browser crashes when attaching photo in gmail
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1349510 Title: browser crashes when attaching photo in gmail Status in Content sharing/picking infrastructure and service: Invalid Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Triaged Status in Web Browser App: Invalid Bug description: build 154 - Save the attached photo in the bug into your ~Pictures directory on the phone - Open gmail in the browser (or as a webbapp, doesn't make a different) - Compose a new gmail message - press the attach button - select the photo under test in the gallery - the browser is shown briefly then crashes NOTE: the browser only seems to crash with a bunch of photos that I copied to the device, all of their size is 2.1mb. So it may be size related. Or noticing now the orientation of the photo appears rotated when viewing on the desktop, so maybe something about the orientation? Photos taken with the camera work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/content-hub/+bug/1349510/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1347924] Re: deadlock in oxide after invoking some (unrelated)c++/qt functions
As we're switching over to trunk in utopic and this particular issue hasn't yet been reported in trusty, I'm going to wontfix this for the 1.1 branch - the change is quite a risky one ** Changed in: oxide/1.1 Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1347924 Title: deadlock in oxide after invoking some (unrelated)c++/qt functions Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Won't Fix Bug description: attachment contains simple reproduction app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1347924/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1349510] Re: browser crashes when attaching photo in gmail
** Changed in: oxide/1.1 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1349510 Title: browser crashes when attaching photo in gmail Status in Content sharing/picking infrastructure and service: Invalid Status in Oxide Webview: Fix Released Status in Oxide 1.1 series: Fix Released Status in Web Browser App: Invalid Bug description: build 154 - Save the attached photo in the bug into your ~Pictures directory on the phone - Open gmail in the browser (or as a webbapp, doesn't make a different) - Compose a new gmail message - press the attach button - select the photo under test in the gallery - the browser is shown briefly then crashes NOTE: the browser only seems to crash with a bunch of photos that I copied to the device, all of their size is 2.1mb. So it may be size related. Or noticing now the orientation of the photo appears rotated when viewing on the desktop, so maybe something about the orientation? Photos taken with the camera work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/content-hub/+bug/1349510/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1214034] Re: Implement API for querying SSL status and certificate information and signalling SSL errors to the embedder
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1214034 Title: Implement API for querying SSL status and certificate information and signalling SSL errors to the embedder Status in Oxide Webview: Fix Released Status in Web Browser App: Triaged Status in “webbrowser-app” package in Ubuntu: Triaged Bug description: The webview should expose an API for querying SSL status and certificate information and signalling SSL errors to the embedder. This is required in order to present something other than a blank page when we encounter verification issues To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1214034/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1362558] Re: Exported cookies have always a date set, even when they shouldn't
** Changed in: oxide Status: New = Fix Released ** Changed in: oxide Milestone: None = branch-1.2 ** Changed in: oxide Assignee: (unassigned) = Chris Coulson (chrisccoulson) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1362558 Title: Exported cookies have always a date set, even when they shouldn't Status in Oxide Webview: Fix Released Bug description: In qt/quick/api/oxideqquickwebcontext.cc, the CookiesRetrieved method prepares the cookies to be returned to the client. The expirationdate field is always set, even when the date is invalid (meaning that the cookie does not expire); this should be changed so that the field is not set if there is no expiration date. This is not a critical bug, as it's fairly easy to workaround it in the client, but it would be nice to have it fixed, sometime. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1362558/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1285750] Re: Provide a web driver for user acceptance testing
** Changed in: oxide Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1285750 Title: Provide a web driver for user acceptance testing Status in Oxide Webview: Fix Released Bug description: Chromium has a web driver that lets us test web pages using selenium. This tool is really good for user acceptance testing as it has all the necessary functions to introspect the pages, wait for items, check for visibility, etc. We need this Selenium web driver in oxide. We could use it with autopilot in order to test the user stories that involve webapps, online accounts and indicators, for example. We have discussed a lot about this. We don't yet know how much effort and time it will take, but Alex Abreu is going to investigate about integrating the chromium dev tools into oxide, and that should give us an idea. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1285750/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1224707] Re: Use a localized Accept-Language header
** Changed in: oxide Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1224707 Title: Use a localized Accept-Language header Status in Oxide Webview: Fix Released Bug description: The Accept-Language header defaults to en-us,en if it hasn't been overridden by the embedder. But the default should be a string that's appropriate for the current locale To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1224707/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1301681] Re: input fields get obscured by OSK
** Changed in: oxide Milestone: branch-1.2 = branch-1.3 ** Also affects: oxide/1.2 Importance: Undecided Status: New ** Changed in: oxide/1.2 Importance: Undecided = High ** Changed in: oxide/1.2 Status: New = Triaged ** Changed in: oxide/1.2 Assignee: (unassigned) = Chris Coulson (chrisccoulson) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1301681 Title: input fields get obscured by OSK Status in Oxide Webview: Triaged Status in Oxide 1.2 series: Triaged Status in Web Browser App: Invalid Bug description: On some webpages if there is an input field near the bottom, when focusing in the field the OSK is displayed but it covers the input field. The input field should scroll into view when the OSK becomes visible. A good site to test is Facebook. Press the comment button on a thread that has a few comments. Click in the comment field and the field becomes obscured when the OSK is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1301681/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1260048] Re: oxide should use an application specific location for pki/nss files
** Changed in: oxide
Milestone: None = branch-1.3
** Changed in: oxide
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1260048
Title:
oxide should use an application specific location for pki/nss files
Status in Oxide Webview:
Fix Released
Bug description:
Running oxide under confinement, I see the following denial:
Dec 11 13:32:58 localhost kernel: [224656.316855] type=1400
audit(1386790378.642:1642): apparmor=DENIED operation=open
parent=3635 profile=com.ubuntu.developer.jdstrand.test-oxide_test-
oxide_0.1 name=/home/jamie/.pki/nssdb/cert9.db pid=21725
comm=Chrome_IOThread requested_mask=rwc denied_mask=rwc
fsuid=1000 ouid=1000
This requires the following rule:
owner @{HOME}/.pki/nssdb/ rw,
owner @{HOME}/.pki/nssdb/** rwk,
But these rules are too lenient because this could disclose data to a
malicious app and a malicious app could poison the databases.
Therefore, these paths need to be made application specific.
Specifically oxide should be adjusted to use
$XDG_DATA_HOME/app_pkgname, where 'app_pkgname' is the name
field in the Click manifest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1260048/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1260048] Re: oxide should use an application specific location for pki/nss files
** Also affects: oxide/1.2
Importance: Undecided
Status: New
** Changed in: oxide/1.2
Milestone: None = 1.2.1
** Changed in: oxide/1.2
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
** Changed in: oxide/1.2
Importance: Undecided = Critical
** Changed in: oxide/1.2
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1260048
Title:
oxide should use an application specific location for pki/nss files
Status in Oxide Webview:
Fix Released
Status in Oxide 1.2 series:
Triaged
Bug description:
Running oxide under confinement, I see the following denial:
Dec 11 13:32:58 localhost kernel: [224656.316855] type=1400
audit(1386790378.642:1642): apparmor=DENIED operation=open
parent=3635 profile=com.ubuntu.developer.jdstrand.test-oxide_test-
oxide_0.1 name=/home/jamie/.pki/nssdb/cert9.db pid=21725
comm=Chrome_IOThread requested_mask=rwc denied_mask=rwc
fsuid=1000 ouid=1000
This requires the following rule:
owner @{HOME}/.pki/nssdb/ rw,
owner @{HOME}/.pki/nssdb/** rwk,
But these rules are too lenient because this could disclose data to a
malicious app and a malicious app could poison the databases.
Therefore, these paths need to be made application specific.
Specifically oxide should be adjusted to use
$XDG_DATA_HOME/app_pkgname, where 'app_pkgname' is the name
field in the Click manifest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1260048/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1278315] Re: Cookie sqlite error 5, errno 0: database is locked when running unit tests
** Changed in: oxide Milestone: None = branch-1.3 ** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1278315 Title: Cookie sqlite error 5, errno 0: database is locked when running unit tests Status in Oxide Webview: Fix Released Bug description: I’ve observed the following error a couple of times (out of hundreds of test runs) when running the unit tests on my laptop: [0202/153311:ERROR:connection.cc(1060)] Cookie sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode = PERSIST [0202/153311:FATAL:connection.cc(747)] SQL compile error database is locked [0x7fd4b70ad886] base::debug::StackTrace::StackTrace() [0x7fd4b7119413] logging::LogMessage::~LogMessage() [0x7fd4bb12acf9] sql::Connection::GetUntrackedStatement() [0x7fd4bb12b125] sql::Connection::DoesTableOrIndexExist() [0x7fd4bb12b0c0] sql::Connection::DoesTableExist() [0x7fd4bb13226f] sql::MetaTable::DoesTableExist() [0x7fd4bb13278d] sql::MetaTable::Init() [0x7fd4bb5d08db] content::SQLitePersistentCookieStore::Backend::EnsureDatabaseVersion() [0x7fd4bb5cef1f] content::SQLitePersistentCookieStore::Backend::InitializeDatabase() [0x7fd4bb5cd7b6] content::SQLitePersistentCookieStore::Backend::LoadAndNotifyInBackground() [0x7fd4bb5db9d7] base::internal::RunnableAdapter::Run() [0x7fd4bb5da205] base::internal::InvokeHelper::MakeItSo() [0x7fd4bb5d8d21] base::internal::Invoker::Run() [0x7fd4b709c572] base::Callback::Run() [0x7fd4b71df56e] base::SequencedWorkerPool::Inner::ThreadLoop() [0x7fd4b71ddb99] base::SequencedWorkerPool::Worker::Run() [0x7fd4b71e9784] base::SimpleThread::ThreadMain() [0x7fd4b71dc320] base::(anonymous namespace)::ThreadFunc() [0x7fd4e6db7182] start_thread [0x7fd4e70c7b5d] clone This looks like a race condition of some sort. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1278315/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1367446] [NEW] WebView.securityStatus.certificate isn't cleared when navigating away from a https URL
Public bug reported:
I found this when writing the unit test for this API. It's fixed by
http://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/revision/725, in particular:
--- shared/browser/oxide_security_status.cc 2014-08-27 07:38:17 +
+++ shared/browser/oxide_security_status.cc 2014-09-09 20:48:07 +
@@ -147,6 +147,7 @@
SecurityStatus::~SecurityStatus() {}
void SecurityStatus::Update(const content::SSLStatus ssl_status) {
+ cert_ = NULL;
content::CertStore::GetInstance()-RetrieveCert(ssl_status.cert_id,
cert_);
** Affects: oxide
Importance: Medium
Assignee: Chris Coulson (chrisccoulson)
Status: Fix Released
** Affects: oxide/1.2
Importance: Medium
Assignee: Chris Coulson (chrisccoulson)
Status: Triaged
** Changed in: oxide
Milestone: None = branch-1.3
** Changed in: oxide
Importance: Undecided = Medium
** Changed in: oxide
Status: New = Fix Released
** Also affects: oxide/1.2
Importance: Undecided
Status: New
** Changed in: oxide/1.2
Importance: Undecided = Medium
** Changed in: oxide/1.2
Status: New = Triaged
** Changed in: oxide/1.2
Milestone: None = 1.2.1
** Changed in: oxide/1.2
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
** Changed in: oxide
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1367446
Title:
WebView.securityStatus.certificate isn't cleared when navigating away
from a https URL
Status in Oxide Webview:
Fix Released
Status in Oxide 1.2 series:
Triaged
Bug description:
I found this when writing the unit test for this API. It's fixed by
http://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/revision/725, in particular:
--- shared/browser/oxide_security_status.cc 2014-08-27 07:38:17 +
+++ shared/browser/oxide_security_status.cc 2014-09-09 20:48:07 +
@@ -147,6 +147,7 @@
SecurityStatus::~SecurityStatus() {}
void SecurityStatus::Update(const content::SSLStatus ssl_status) {
+ cert_ = NULL;
content::CertStore::GetInstance()-RetrieveCert(ssl_status.cert_id,
cert_);
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1367446/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1368117] [NEW] WebView.blockedContent indicates the wrong state in some circumstances
Public bug reported: Whilst writing the test for this, I noticed that if you do the following: - set WebPreferences.canDisplayInsecureContent to false - load a page over SSL that contains an insecure script and an insecure image (at this point, the ContentTypeMixedDisplay and ContentTypeMixedScript bits of WebView.blockedContent are set, correctly) - call WebView.setCanTemporarilyDisplayInsecureContent(true) (which causes the page to reload). At this point, WebView.blockedContent should still have the ContentTypeMixedScript bit set, but it is now clear ** Affects: oxide Importance: Medium Assignee: Chris Coulson (chrisccoulson) Status: Triaged ** Affects: oxide/1.2 Importance: Medium Assignee: Chris Coulson (chrisccoulson) Status: Triaged ** Changed in: oxide Importance: Undecided = Medium ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Milestone: None = branch-1.3 ** Changed in: oxide Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Also affects: oxide/1.2 Importance: Undecided Status: New ** Changed in: oxide/1.2 Milestone: None = 1.2.1 ** Changed in: oxide/1.2 Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide/1.2 Importance: Undecided = Medium ** Changed in: oxide/1.2 Status: New = Triaged ** Description changed: Whilst writing the test for this, I noticed that if you do the following: - set WebPreferences.canDisplayInsecureContent to false - - load a page over SSL that contains an insecure script and insecure content (at this point, WebView.blockedContent is correct) + - load a page over SSL that contains an insecure script and an insecure image (at this point, the ContentTypeMixedDisplay and ContentTypeMixedScript bits of WebView.blockedContent are set, correctly) - call WebView.setCanTemporarilyDisplayInsecureContent(true) (which causes the page to reload). At this point, WebView.blockedContent should still have the ContentTypeMixedScript bit set, but it is now clear -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1368117 Title: WebView.blockedContent indicates the wrong state in some circumstances Status in Oxide Webview: Triaged Status in Oxide 1.2 series: Triaged Bug description: Whilst writing the test for this, I noticed that if you do the following: - set WebPreferences.canDisplayInsecureContent to false - load a page over SSL that contains an insecure script and an insecure image (at this point, the ContentTypeMixedDisplay and ContentTypeMixedScript bits of WebView.blockedContent are set, correctly) - call WebView.setCanTemporarilyDisplayInsecureContent(true) (which causes the page to reload). At this point, WebView.blockedContent should still have the ContentTypeMixedScript bit set, but it is now clear To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1368117/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1368117] Re: WebView.blockedContent indicates the wrong state in some circumstances
** Changed in: oxide Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1368117 Title: WebView.blockedContent indicates the wrong state in some circumstances Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Triaged Bug description: Whilst writing the test for this, I noticed that if you do the following: - set WebPreferences.canDisplayInsecureContent to false - load a page over SSL that contains an insecure script and an insecure image (at this point, the ContentTypeMixedDisplay and ContentTypeMixedScript bits of WebView.blockedContent are set, correctly) - call WebView.setCanTemporarilyDisplayInsecureContent(true) (which causes the page to reload). At this point, WebView.blockedContent should still have the ContentTypeMixedScript bit set, but it is now clear To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1368117/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1368385] [NEW] WebView.securityStatus.securityLevel indicates everything is normal if a subresource certificate error is allowed for a resource from a different domain from
Public bug reported: I caught this whilst writing unit tests. If a secure site loads a resource from a different domain but that resource load comes with an invalid certificate, WebView.onCertificateError will fire with the isSubresource property set to true. If the application then allow's this, WebView.securityStatus.securityLevel does not indicate a degraded security level as expected. It *does* work if the subresource is from the same domain as the main document, as that host is marked as having ran insecure content. ** Affects: oxide Importance: Critical Assignee: Chris Coulson (chrisccoulson) Status: Triaged ** Affects: oxide/1.2 Importance: Critical Assignee: Chris Coulson (chrisccoulson) Status: Triaged ** Changed in: oxide Importance: Undecided = Critical ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Milestone: None = branch-1.3 ** Changed in: oxide Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Also affects: oxide/1.2 Importance: Undecided Status: New ** Changed in: oxide/1.2 Importance: Undecided = Critical ** Changed in: oxide/1.2 Status: New = Triaged ** Changed in: oxide/1.2 Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide/1.2 Milestone: None = 1.2.1 ** Description changed: - If a secure site loads a resource from a different domain but that - resource load comes with a broken certificate, - WebView.onCertificateError will fire with the isSubresource property set - to true. If the application then allow's this, - WebView.securityStatus.securityLevel does not indicate a degraded to - security level. + I caught this whilst writing unit tests. If a secure site loads a + resource from a different domain but that resource load comes with an + invalid certificate, WebView.onCertificateError will fire with the + isSubresource property set to true. If the application then allow's + this, WebView.securityStatus.securityLevel does not indicate a degraded + security level as expected. It *does* work if the subresource is from the same domain as the main document, as that host is marked as having ran insecure content. -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1368385 Title: WebView.securityStatus.securityLevel indicates everything is normal if a subresource certificate error is allowed for a resource from a different domain from the main document Status in Oxide Webview: Triaged Status in Oxide 1.2 series: Triaged Bug description: I caught this whilst writing unit tests. If a secure site loads a resource from a different domain but that resource load comes with an invalid certificate, WebView.onCertificateError will fire with the isSubresource property set to true. If the application then allow's this, WebView.securityStatus.securityLevel does not indicate a degraded security level as expected. It *does* work if the subresource is from the same domain as the main document, as that host is marked as having ran insecure content. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1368385/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1368385] Re: WebView.securityStatus.securityLevel indicates everything is normal if a subresource certificate error is allowed for a resource from a different domain from th
Fixed with http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/740 http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/739 is also needed for backporting to 1.2. ** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1368385 Title: WebView.securityStatus.securityLevel indicates everything is normal if a subresource certificate error is allowed for a resource from a different domain from the main document Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Triaged Bug description: I caught this whilst writing unit tests. If a secure site loads a resource from a different domain but that resource load comes with an invalid certificate, WebView.onCertificateError will fire with the isSubresource property set to true. If the application then allow's this, WebView.securityStatus.securityLevel does not indicate a degraded security level as expected. It *does* work if the subresource is from the same domain as the main document, as that host is marked as having ran insecure content. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1368385/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1354382] Re: [Browser] White line at the bottom of the viewport
** Changed in: oxide Status: In Progress = Fix Released ** Changed in: webbrowser-app Status: Triaged = Invalid ** Also affects: oxide-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: oxide-qt (Ubuntu) Status: New = Triaged ** Changed in: oxide-qt (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1354382 Title: [Browser] White line at the bottom of the viewport Status in Oxide Webview: Fix Released Status in Ubuntu UX bugs: Triaged Status in Web Browser App: Invalid Status in “oxide-qt” package in Ubuntu: Triaged Bug description: There's a white line at the bottom of the viewport (test on theverge.com Blinkbox.com) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1354382/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1368850] Re: Add .mo files to language-packs
** Changed in: oxide Status: In Progress = Invalid -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1368850 Title: Add .mo files to language-packs Status in Oxide Webview: Invalid Bug description: The .mo files are not added to the language-packs right now, because we just miss a line in the debian/control file: X-Ubuntu-Use-Langpack: yes To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1368850/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1301681] Re: input fields get obscured by OSK
Fixed with http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/757 ** Changed in: oxide Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1301681 Title: input fields get obscured by OSK Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Triaged Status in Web Browser App: Invalid Bug description: On some webpages if there is an input field near the bottom, when focusing in the field the OSK is displayed but it covers the input field. The input field should scroll into view when the OSK becomes visible. A good site to test is Facebook. Press the comment button on a thread that has a few comments. Click in the comment field and the field becomes obscured when the OSK is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1301681/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1372414] Re: SSL certificates report incorrect years
Thanks, that's fixed with http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/764 ** Changed in: oxide Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1372414 Title: SSL certificates report incorrect years Status in Oxide Webview: Fix Released Bug description: The effectiveDate and expiryDate properties on SSL certificates are currently returning incorrect year components (usually something like 2381). To reproduce: 1. Use webbrowser-app with SSL warning support: https://code.launchpad.net/~michael-sheldon/webbrowser-app/ssl- status/+merge/235309 2. Visit page with bad SSL certificate, e.g. https://testssl- expire.disig.sk/ 3. Click Learn more on the SSL error page. The valid from and valid to fields will display an incorrect year in their date. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1372414/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1372414] Re: SSL certificates report incorrect years
** Also affects: oxide/1.2 Importance: Undecided Status: New ** Changed in: oxide/1.2 Importance: Undecided = Medium ** Changed in: oxide/1.2 Status: New = Triaged ** Changed in: oxide/1.2 Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide/1.2 Milestone: None = 1.2.2 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1372414 Title: SSL certificates report incorrect years Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Fix Committed Bug description: The effectiveDate and expiryDate properties on SSL certificates are currently returning incorrect year components (usually something like 2381). To reproduce: 1. Use webbrowser-app with SSL warning support: https://code.launchpad.net/~michael-sheldon/webbrowser-app/ssl- status/+merge/235309 2. Visit page with bad SSL certificate, e.g. https://testssl- expire.disig.sk/ 3. Click Learn more on the SSL error page. The valid from and valid to fields will display an incorrect year in their date. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1372414/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1368385] Re: WebView.securityStatus.securityLevel indicates everything is normal if a subresource certificate error is allowed for a resource from a different domain from th
** Changed in: oxide/1.2 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1368385 Title: WebView.securityStatus.securityLevel indicates everything is normal if a subresource certificate error is allowed for a resource from a different domain from the main document Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Fix Released Bug description: I caught this whilst writing unit tests. If a secure site loads a resource from a different domain but that resource load comes with an invalid certificate, WebView.onCertificateError will fire with the isSubresource property set to true. If the application then allow's this, WebView.securityStatus.securityLevel does not indicate a degraded security level as expected. It *does* work if the subresource is from the same domain as the main document, as that host is marked as having ran insecure content. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1368385/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1260048] Re: oxide should use an application specific location for pki/nss files
** Changed in: oxide/1.2
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1260048
Title:
oxide should use an application specific location for pki/nss files
Status in Oxide Webview:
Fix Released
Status in Oxide 1.2 series:
Fix Released
Bug description:
Running oxide under confinement, I see the following denial:
Dec 11 13:32:58 localhost kernel: [224656.316855] type=1400
audit(1386790378.642:1642): apparmor=DENIED operation=open
parent=3635 profile=com.ubuntu.developer.jdstrand.test-oxide_test-
oxide_0.1 name=/home/jamie/.pki/nssdb/cert9.db pid=21725
comm=Chrome_IOThread requested_mask=rwc denied_mask=rwc
fsuid=1000 ouid=1000
This requires the following rule:
owner @{HOME}/.pki/nssdb/ rw,
owner @{HOME}/.pki/nssdb/** rwk,
But these rules are too lenient because this could disclose data to a
malicious app and a malicious app could poison the databases.
Therefore, these paths need to be made application specific.
Specifically oxide should be adjusted to use
$XDG_DATA_HOME/app_pkgname, where 'app_pkgname' is the name
field in the Click manifest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1260048/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1352631] Re: support accelerated_2d_canvas
** Changed in: oxide Milestone: None = branch-1.3 ** Changed in: oxide Status: In Progress = Fix Released ** Changed in: oxide Assignee: (unassigned) = Justin McPherson (justinmcp) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1352631 Title: support accelerated_2d_canvas Status in Oxide Webview: Fix Released Bug description: this option enabled by default on android. It will be useful for html5 games. I test few games with google-chrome with accelerated_2d_canvas enabled, they works fine. canvas render trash on oxide (with accelerated_2d_canvas enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1352631/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1324292] Re: re-add support for selecting text for copying
** Changed in: oxide Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1324292 Title: re-add support for selecting text for copying Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Fix Committed Status in Web Browser App: Fix Committed Status in “webbrowser-app” package in Ubuntu: Fix Committed Bug description: in the qtwebkit browser we had the ability to create a selection region with handles for resizing. needs to bring this back for oxide based browser. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1324292/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1362543] Re: Web Application fail to load properly every other time is launched
Fixed with http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/769 ** Changed in: oxide Status: Confirmed = Fix Released ** Changed in: oxide Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide Milestone: None = branch-1.3 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1362543 Title: Web Application fail to load properly every other time is launched Status in Oxide Webview: Fix Released Status in The Webapps-core project: Invalid Status in Web Browser App: Invalid Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: I am testing a game called ninjaflips. Works fine the first time you launch it , but the second time wont load correctly. If you close it and try again it will launch fine and so on.. Attached logs for working and not working plus click package To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1362543/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1352631] Re: support accelerated_2d_canvas
** Also affects: oxide/1.2 Importance: Undecided Status: New ** Changed in: oxide/1.2 Milestone: None = 1.2.3 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1352631 Title: support accelerated_2d_canvas Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: New Bug description: this option enabled by default on android. It will be useful for html5 games. I test few games with google-chrome with accelerated_2d_canvas enabled, they works fine. canvas render trash on oxide (with accelerated_2d_canvas enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1352631/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1374494] [NEW] Warnings when processing GPU blacklist
Public bug reported: I get these warnings every time I start an app that loads Oxide, since bug 1352631 landed: 1: [0926/145212:WARNING:gpu_control_list.cc(760)] Entry with unknown fields 0 1: [0926/145212:WARNING:gpu_control_list.cc(746)] Malformed exceptions entry 24 ** Affects: oxide Importance: Low Assignee: Justin McPherson (justinmcp) Status: Triaged ** Changed in: oxide Importance: Undecided = Low ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Assignee: (unassigned) = Justin McPherson (justinmcp) -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1374494 Title: Warnings when processing GPU blacklist Status in Oxide Webview: Triaged Bug description: I get these warnings every time I start an app that loads Oxide, since bug 1352631 landed: 1: [0926/145212:WARNING:gpu_control_list.cc(760)] Entry with unknown fields 0 1: [0926/145212:WARNING:gpu_control_list.cc(746)] Malformed exceptions entry 24 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1374494/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1376268] [NEW] Implement a touch editing UI
Public bug reported: For copy / paste support on the device, we need to implement a touch editing UI in Oxide (the touch editing UI is basically the handles that you can drag around to select blocks of text) ** Affects: oxide Importance: High Status: Triaged ** Changed in: oxide Milestone: None = branch-1.4 ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1376268 Title: Implement a touch editing UI Status in Oxide Webview: Triaged Bug description: For copy / paste support on the device, we need to implement a touch editing UI in Oxide (the touch editing UI is basically the handles that you can drag around to select blocks of text) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1376268/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1362543] Re: Web Application fail to load properly every other time is launched
** Changed in: oxide/1.2 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1362543 Title: Web Application fail to load properly every other time is launched Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Fix Released Status in The Webapps-core project: Invalid Status in Web Browser App: Invalid Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: I am testing a game called ninjaflips. Works fine the first time you launch it , but the second time wont load correctly. If you close it and try again it will launch fine and so on.. Attached logs for working and not working plus click package To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1362543/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1376896] [NEW] Accelerometer events don't work
Public bug reported: Accelerometer events currently don't work in the browser. Steps to reproduce: - Navigate to http://shakeherbooty.com/ - Observe that shaking the device doesn't have the expected effect ** Affects: oxide Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1376896 Title: Accelerometer events don't work Status in Oxide Webview: New Bug description: Accelerometer events currently don't work in the browser. Steps to reproduce: - Navigate to http://shakeherbooty.com/ - Observe that shaking the device doesn't have the expected effect To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1376896/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1377194] [NEW] Various issues with security UI's
Public bug reported: I've not done a proper review on this yet, but there are a few issues I've noticed just from using the browser: - The certificate error UI is displayed for all errors, but it should only be displayed for main frame document errors (CertificateError.isMainFrame !CertificateError.isSubresource). You can't override other errors anyway, and for subframes and subresources it is fine to just block the content (this is how Chrome and Firefox behave). - When accepting an error, the certificate fingerprint seems to be whitelisted by the browser. This is not safe - what happens if the user navigates to a genuinely malicious site that happens to use the same certificate? If you want to whitelist them, you must also record the domain that the error originated from and the error code, and only automatically allow the error if the domain + error code + fingerprints match - When accepting an error, there is no visual cue in the header bar that you're on a site with security errors. - If you press the stop icon in the addressbar whilst the certificate error UI is displayed, the pending navigation is cancelled (returning to the previous committed navigation), but the certificate error UI is not removed. There is a CertificateError.cancelled signal for this purpose - I'm not sure if you're using it or not - There doesn't seem to be any indicator when you go to a site that has an EV certificate ** Affects: webbrowser-app Importance: Undecided Status: New ** Description changed: I've not done a proper review on this yet, but there are a few issues I've noticed just from using the browser: - The certificate error UI is displayed for all errors, but it should only be displayed for main frame document errors (CertificateError.isMainFrame !CertificateError.isSubresource). You - can't override these errors anyway, and for subframes and subresources + can't override other errors anyway, and for subframes and subresources it is fine to just block the content (this is how Chrome and Firefox behave). - When accepting an error, the certificate fingerprint seems to be whitelisted by the browser. This is not safe - what happens if the user navigates to a genuinely malicious site that happens to use the same certificate? If you want to whitelist them, you must also record the domain that the error originated from and the error code, and only automatically allow the error if the domain + error code + fingerprints match - When accepting an error, there is no visual cue in the header bar that you're on a site with security errors. - If you press the stop icon in the addressbar whilst the certificate error UI is displayed, the pending navigation is cancelled (returning to the previous committed navigation), but the certificate error UI is not removed. There is a CertificateError.cancelled signal for this purpose - I'm not sure if you're using it or not ** Description changed: I've not done a proper review on this yet, but there are a few issues I've noticed just from using the browser: - The certificate error UI is displayed for all errors, but it should only be displayed for main frame document errors (CertificateError.isMainFrame !CertificateError.isSubresource). You can't override other errors anyway, and for subframes and subresources it is fine to just block the content (this is how Chrome and Firefox behave). - When accepting an error, the certificate fingerprint seems to be whitelisted by the browser. This is not safe - what happens if the user navigates to a genuinely malicious site that happens to use the same certificate? If you want to whitelist them, you must also record the domain that the error originated from and the error code, and only automatically allow the error if the domain + error code + fingerprints match - When accepting an error, there is no visual cue in the header bar that you're on a site with security errors. - If you press the stop icon in the addressbar whilst the certificate error UI is displayed, the pending navigation is cancelled (returning to the previous committed navigation), but the certificate error UI is not removed. There is a CertificateError.cancelled signal for this purpose - I'm not sure if you're using it or not + + - There doesn't seem to be any indicator when you go to a site that has + an EV certificate -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1377194 Title: Various issues with security UI's Status in Web Browser App: New Bug description: I've not done a proper review on this yet, but there are a few issues I've noticed just from using the browser: - The certificate error UI is displayed for all errors, but it should only be displayed for main frame document errors
[Ubuntu-webapps-bugs] [Bug 1377198] [NEW] CertificateError is not cancelled if you stop the pending navigation
Public bug reported: Active CertificateErrors are not cancelled if the pending navigation is stopped. We currently only cancel active errors when a navigation is committed. This needs a rethink ** Affects: oxide Importance: High Status: Triaged ** Changed in: oxide Importance: Undecided = High ** Changed in: oxide Status: New = Triaged ** Changed in: oxide Milestone: None = branch-1.3 -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1377198 Title: CertificateError is not cancelled if you stop the pending navigation Status in Oxide Webview: Triaged Bug description: Active CertificateErrors are not cancelled if the pending navigation is stopped. We currently only cancel active errors when a navigation is committed. This needs a rethink To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1377198/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1301681] Re: input fields get obscured by OSK
As the next upload to utopic will be from a 1.3 branch, marking this as wontfix for 1.2 ** Changed in: oxide/1.2 Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to webbrowser-app. https://bugs.launchpad.net/bugs/1301681 Title: input fields get obscured by OSK Status in Oxide Webview: Fix Released Status in Oxide 1.2 series: Won't Fix Status in Web Browser App: Invalid Bug description: On some webpages if there is an input field near the bottom, when focusing in the field the OSK is displayed but it covers the input field. The input field should scroll into view when the OSK becomes visible. A good site to test is Facebook. Press the comment button on a thread that has a few comments. Click in the comment field and the field becomes obscured when the OSK is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1301681/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
