[Ubuntu-webapps-bugs] [Bug 1425550] Re: webbrowser-app still depends on qtdeclarative-abi
** Changed in: webbrowser-app 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/1425550 Title: webbrowser-app still depends on qtdeclarative-abi Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Even though the fix for bug #1387537 is included in https://launchpad.net/ubuntu/+source/webbrowser- app/0.23+15.04.20150224-0ubuntu1 - the webbrowser-app binary package still depends on qtdeclarative-abi-5-4-0, so thus not completely not rid of private header usage. This can be seen by opening https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-025/+build/7008148/+files/webbrowser- app_0.23%2B15.04.20150224-0ubuntu1_amd64.deb in file-roller and checking debian/CONTROL. This should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1425550/+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 1401581] Re: FBO used for webview capture rendered everytime the webview is updated, impacts rendering performance
** Changed in: webbrowser-app 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/1401581 Title: FBO used for webview capture rendered everytime the webview is updated, impacts rendering performance Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The current mechanism to implement tab previews in the browser uses a ShaderEffectSource on the WebView, which basically renders the WebView into a FBO. To ensure that the preview is always up-to-date, the 'live' property is set to true as long as the webview is visible, meaning that every pixel visible on screen is rendered twice. This has a performance impact, which could be minimized if we found a way to have the 'live' property always false, except when a capture is requested. Alternatively, the capture mechanism could be implemented in oxide, thus achieving a better performance, and removing complexity from the browser itself. Note that https://code.launchpad.net/~osomon/webbrowser-app/webview- capture/+merge/243034 doesn’t address this specific issue (it doesn’t make it worse either). To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1401581/+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 1412732] Re: [browser] visuals for multi-select mode in history view need update
This bug was fixed in the package webbrowser-app - 0.23+15.04.20150224-0ubuntu1 --- webbrowser-app (0.23+15.04.20150224-0ubuntu1) vivid; urgency=medium [ Olivier Tilloy ] * Fix a flaky autopilot test. (LP: #1423115) * Use Qt::AA_ShareOpenGLContexts when building with Qt = 5.4. (LP: #1387537) [ Riccardo Padovani ] * Fixed design of multiselection in history view (LP: #1412732) -- CI Train Bot ci-train-...@canonical.com Tue, 24 Feb 2015 10:30:59 + ** Changed in: webbrowser-app (Ubuntu) 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/1412732 Title: [browser] visuals for multi-select mode in history view need update Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: Multi-select mode in the history view was implemented as part of bug #1351167. But the visuals do not match the visual spec exactly. Spec: https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 Screenshot: https://launchpadlibrarian.net/195323251/browser- multiselect.png In particular, padding and spacing need to be adjusted. The buttons at the top should have a label, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1412732/+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 1412732] Re: [browser] visuals for multi-select mode in history view need update
** Changed in: webbrowser-app 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/1412732 Title: [browser] visuals for multi-select mode in history view need update Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: Multi-select mode in the history view was implemented as part of bug #1351167. But the visuals do not match the visual spec exactly. Spec: https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 Screenshot: https://launchpadlibrarian.net/195323251/browser- multiselect.png In particular, padding and spacing need to be adjusted. The buttons at the top should have a label, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1412732/+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 1402994] Re: oxide::qt::LocationProvider should be paused when the application becomes inactive
The fix has been moved to qtsensors that automativally handles application state updates and starts/stops the geolocation source automatically, ** Branch linked: lp:~ricmm/qtubuntu-sensors/browser-location-rtm ** Changed in: oxide Status: Confirmed = Invalid ** Branch linked: lp:~ricmm/qtubuntu-sensors/browser-location-vivid -- 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/1402994 Title: oxide::qt::LocationProvider should be paused when the application becomes inactive Status in the base for Ubuntu mobile products: In Progress Status in Oxide Webview: Invalid Status in qtubuntu-sensors package in Ubuntu: New Bug description: If a WebView is used to browse to a page that requests continuous position updates, the LocationProvider should be paused when the application goes in the background, and resumed when it gets back in the foreground. This could be implemented by making oxide::qt::LocationProvider a BrowserPlatformIntegrationObserver. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1402994/+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 1387537] Re: Use Qt::AA_ShareOpenGLContexts and drop Qt private headers usage
This bug was fixed in the package webbrowser-app - 0.23+15.04.20150224-0ubuntu1 --- webbrowser-app (0.23+15.04.20150224-0ubuntu1) vivid; urgency=medium [ Olivier Tilloy ] * Fix a flaky autopilot test. (LP: #1423115) * Use Qt::AA_ShareOpenGLContexts when building with Qt = 5.4. (LP: #1387537) [ Riccardo Padovani ] * Fixed design of multiselection in history view (LP: #1412732) -- CI Train Bot ci-train-...@canonical.com Tue, 24 Feb 2015 10:30:59 + ** Changed in: webbrowser-app (Ubuntu) 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/1387537 Title: Use Qt::AA_ShareOpenGLContexts and drop Qt private headers usage Status in Oxide Webview: Invalid Status in Ubuntu UI SDK for HTML5 Apps: In Progress Status in Online Accounts setup for Ubuntu Touch: In Progress Status in Web Browser App: In Progress Status in oxide-qt package in Ubuntu: New Status in ubuntu-html5-theme package in Ubuntu: Confirmed Status in ubuntu-system-settings-online-accounts package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Update: Qt 5.4 provides Qt::AA_ShareOpenGLContexts function that should help in dropping the Qt private headers usage in ubuntu- html5-theme, ubuntu-system-settings-online-accounts and webbrowser- app. More information about Qt 5.4 at: https://wiki.ubuntu.com/Touch/QtTesting --- original report --- There's a critical bug that is being fixed with the following MP: https://code.launchpad.net/~abreu-alexandre/ubuntu-system-settings- online-accounts/use-hw-compositiing-oxide-rtm-1409/+merge/23 This bug is about removing the need for that, since using private headers causes extra pain for Qt migrations and we should minimize their usage. Could Oxide provide this somehow else, so that only Oxide would use the private headers (like it already does)? Update: not blocker for Qt 5.4, but simply something that would help Qt transitions in future by removing 5 packages from the transition list To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1387537/+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 1387537] Re: Use Qt::AA_ShareOpenGLContexts and drop Qt private headers usage
** Changed in: webbrowser-app 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/1387537 Title: Use Qt::AA_ShareOpenGLContexts and drop Qt private headers usage Status in Oxide Webview: Invalid Status in Ubuntu UI SDK for HTML5 Apps: In Progress Status in Online Accounts setup for Ubuntu Touch: In Progress Status in Web Browser App: Fix Released Status in oxide-qt package in Ubuntu: New Status in ubuntu-html5-theme package in Ubuntu: Confirmed Status in ubuntu-system-settings-online-accounts package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Update: Qt 5.4 provides Qt::AA_ShareOpenGLContexts function that should help in dropping the Qt private headers usage in ubuntu- html5-theme, ubuntu-system-settings-online-accounts and webbrowser- app. More information about Qt 5.4 at: https://wiki.ubuntu.com/Touch/QtTesting --- original report --- There's a critical bug that is being fixed with the following MP: https://code.launchpad.net/~abreu-alexandre/ubuntu-system-settings- online-accounts/use-hw-compositiing-oxide-rtm-1409/+merge/23 This bug is about removing the need for that, since using private headers causes extra pain for Qt migrations and we should minimize their usage. Could Oxide provide this somehow else, so that only Oxide would use the private headers (like it already does)? Update: not blocker for Qt 5.4, but simply something that would help Qt transitions in future by removing 5 packages from the transition list To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1387537/+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 1423115] Re: Intermittent test failure in test_pattern_with_allowed_targetted_url
** Changed in: webbrowser-app Status: In Progress = Fix Released ** Changed in: webbrowser-app (Ubuntu) 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/1423115 Title: Intermittent test failure in test_pattern_with_allowed_targetted_url Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: When running webapp_container autopilot tests, I’m often (but not always) seeing a failure with the following test: webapp_container.tests.test_url_patterns.WebappContainerUrlPatternsTestCase.test_pattern_with_allowed_targetted_url The problem is obvious when reading the test: it clicks on the webview and then checks the value of the new URL, but the check is done instantly, whereas the property can take a few milliseconds to change. Adding an Eventually() does the trick. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1423115/+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 1423115] Re: Intermittent test failure in test_pattern_with_allowed_targetted_url
This bug was fixed in the package webbrowser-app - 0.23+15.04.20150224-0ubuntu1 --- webbrowser-app (0.23+15.04.20150224-0ubuntu1) vivid; urgency=medium [ Olivier Tilloy ] * Fix a flaky autopilot test. (LP: #1423115) * Use Qt::AA_ShareOpenGLContexts when building with Qt = 5.4. (LP: #1387537) [ Riccardo Padovani ] * Fixed design of multiselection in history view (LP: #1412732) -- CI Train Bot ci-train-...@canonical.com Tue, 24 Feb 2015 10:30:59 + ** Changed in: webbrowser-app (Ubuntu) Status: New = 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/1423115 Title: Intermittent test failure in test_pattern_with_allowed_targetted_url Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: Fix Released Bug description: When running webapp_container autopilot tests, I’m often (but not always) seeing a failure with the following test: webapp_container.tests.test_url_patterns.WebappContainerUrlPatternsTestCase.test_pattern_with_allowed_targetted_url The problem is obvious when reading the test: it clicks on the webview and then checks the value of the new URL, but the check is done instantly, whereas the property can take a few milliseconds to change. Adding an Eventually() does the trick. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1423115/+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 1426156] [NEW] WebView.blockedContent should indicate when storage access (eg, cookies) is blocked
Public bug reported: Cookies are currently blocked silently - we should indicate to the embedder when the current page has been denied access (read or write) to cookies or other storage types. ** Affects: oxide Importance: Low Status: Triaged ** Changed in: oxide Status: New = Triaged ** Changed in: oxide 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/1426156 Title: WebView.blockedContent should indicate when storage access (eg, cookies) is blocked Status in Oxide Webview: Triaged Bug description: Cookies are currently blocked silently - we should indicate to the embedder when the current page has been denied access (read or write) to cookies or other storage types. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1426156/+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 1422909] Re: Scrollbars always displayed on mobile
This is fixed in http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/988 ** Changed in: oxide Milestone: None = branch-1.6 ** 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/1422909 Title: Scrollbars always displayed on mobile Status in Oxide Webview: Fix Released Bug description: On the phone, the webview always displays overlay scrollbars on scrollable axes. However, this should be changed to mimic the Chrome- on-Android case, where the scrollbars fade out after a short delay when scrolling ends To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1422909/+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 1426153] [NEW] Use a single threaded webview compositor
Public bug reported: The webview compositor currently runs on a separate thread - it's like this because at one stage it looked like Google were going to remove the single threaded mode. However, they seem to have settled on a single- threaded browser compositor for now. A threaded webview compositor has always been unnecessary in Oxide for a few reasons: - It doesn't handle any animations, so there are no cases where it needs to remain responsive if the main thread is blocked. - It only contains a single visible layer - the delegated frame layer. Updating this involves the main thread anyway. - Unlike the renderer main thread which runs arbitrary script, what runs on the browser main thread is controlled by the embedder and predictable. The browser main thread should never be busy enough to block the compositor. - It adds unnecessary complexity. - It introduces additional thread hops. ** 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/1426153 Title: Use a single threaded webview compositor Status in Oxide Webview: Triaged Bug description: The webview compositor currently runs on a separate thread - it's like this because at one stage it looked like Google were going to remove the single threaded mode. However, they seem to have settled on a single-threaded browser compositor for now. A threaded webview compositor has always been unnecessary in Oxide for a few reasons: - It doesn't handle any animations, so there are no cases where it needs to remain responsive if the main thread is blocked. - It only contains a single visible layer - the delegated frame layer. Updating this involves the main thread anyway. - Unlike the renderer main thread which runs arbitrary script, what runs on the browser main thread is controlled by the embedder and predictable. The browser main thread should never be busy enough to block the compositor. - It adds unnecessary complexity. - It introduces additional thread hops. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1426153/+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 1425550] Re: webbrowser-app still depends on qtdeclarative-abi
This bug was fixed in the package webbrowser-app - 0.23+15.04.20150226.1-0ubuntu1 --- webbrowser-app (0.23+15.04.20150226.1-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Olivier Tilloy ] * Use the new Item::grabToImage() API (new in Qt 5.4) to replace the custom ItemCapture element. (LP: #1401581, #1425550) [ Robert Bruce Park ] * Launchpad automatic translations update. -- CI Train Bot ci-train-...@canonical.com Thu, 26 Feb 2015 18:10:41 + ** Changed in: webbrowser-app (Ubuntu) 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/1425550 Title: webbrowser-app still depends on qtdeclarative-abi Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Even though the fix for bug #1387537 is included in https://launchpad.net/ubuntu/+source/webbrowser- app/0.23+15.04.20150224-0ubuntu1 - the webbrowser-app binary package still depends on qtdeclarative-abi-5-4-0, so thus not completely not rid of private header usage. This can be seen by opening https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-025/+build/7008148/+files/webbrowser- app_0.23%2B15.04.20150224-0ubuntu1_amd64.deb in file-roller and checking debian/CONTROL. This should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1425550/+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 1401581] Re: FBO used for webview capture rendered everytime the webview is updated, impacts rendering performance
This bug was fixed in the package webbrowser-app - 0.23+15.04.20150226.1-0ubuntu1 --- webbrowser-app (0.23+15.04.20150226.1-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Olivier Tilloy ] * Use the new Item::grabToImage() API (new in Qt 5.4) to replace the custom ItemCapture element. (LP: #1401581, #1425550) [ Robert Bruce Park ] * Launchpad automatic translations update. -- CI Train Bot ci-train-...@canonical.com Thu, 26 Feb 2015 18:10:41 + ** Changed in: webbrowser-app (Ubuntu) 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/1401581 Title: FBO used for webview capture rendered everytime the webview is updated, impacts rendering performance Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The current mechanism to implement tab previews in the browser uses a ShaderEffectSource on the WebView, which basically renders the WebView into a FBO. To ensure that the preview is always up-to-date, the 'live' property is set to true as long as the webview is visible, meaning that every pixel visible on screen is rendered twice. This has a performance impact, which could be minimized if we found a way to have the 'live' property always false, except when a capture is requested. Alternatively, the capture mechanism could be implemented in oxide, thus achieving a better performance, and removing complexity from the browser itself. Note that https://code.launchpad.net/~osomon/webbrowser-app/webview- capture/+merge/243034 doesn’t address this specific issue (it doesn’t make it worse either). To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1401581/+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
