[Ubuntu-webapps-bugs] [Bug 1675963] Re: Get rid of oxide bits in //ui/gl/init

[Chris Coulson]

** 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/1675963

Title:
  Get rid of oxide bits in //ui/gl/init

Status in Oxide:
  Fix Released

Bug description:
  We currently replace the ozone bits in //ui/gl/init with Oxide
  implementations. This originates from a time when Chromium/Ozone
  builds didn't support GLX, but that's not the case anymore.

  I want to try to get Chromium's content shell working from an Oxide
  build in order to run the blink layout tests. The content shell will
  communicate directly with the windowing system rather than using
  Oxide, and so will require a full featured ozone platform. As part of
  this, I'm planning to enable the x11 ozone platform for Oxide builds,
  but in order to make this work, the ozone bits in //ui/gl/init need to
  be re-enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1675963/+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 1676027] Re: Build the x11 ozone platform

[Chris Coulson]

** 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/1676027

Title:
  Build the x11 ozone platform

Status in Oxide:
  Fix Released

Bug description:
  See bug 1675963 - I want to try to get Chromium's content shell
  working out of an Oxide build tree. For that, we need a full featured
  ozone platform, so let's enable the x11 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1676027/+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 1678219] [NEW] Maybe add an API for manipulating saved credentials

[Chris Coulson]

Public bug reported:

I'm not sure whether the browser will want this yet, or whether it
relies on whatever UI exists for manipulating the system secret service
(eg, seahorse).

** 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/1678219

Title:
  Maybe add an API for manipulating saved credentials

Status in Oxide:
  Triaged

Bug description:
  I'm not sure whether the browser will want this yet, or whether it
  relies on whatever UI exists for manipulating the system secret
  service (eg, seahorse).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678219/+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 1678216] [NEW] Add an API to allow the application to prompt to save a password

[Chris Coulson]

Public bug reported:

We need an API so that Oxide can tell the application to prompt whether
to save a password.

** 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/1678216

Title:
  Add an API to allow the application to prompt to save a password

Status in Oxide:
  Triaged

Bug description:
  We need an API so that Oxide can tell the application to prompt
  whether to save a password.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678216/+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 1678179] [NEW] Support autocomplete for password fields

[Chris Coulson]

Public bug reported:

We need to support autocomplete for password fields. Part of this will
involve implementing credentials storage. Chrome/Linux currently has
PasswordStore implementations that use libsecret / gnome keyring /
kwallet, but these are part of //chrome rather than
//components/password_manager. It can also fall back to its own login
DB, but that isn't encrypted on Linux.

** 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/1678179

Title:
  Support autocomplete for password fields

Status in Oxide:
  Triaged

Bug description:
  We need to support autocomplete for password fields. Part of this will
  involve implementing credentials storage. Chrome/Linux currently has
  PasswordStore implementations that use libsecret / gnome keyring /
  kwallet, but these are part of //chrome rather than
  //components/password_manager. It can also fall back to its own login
  DB, but that isn't encrypted on Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678179/+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 1678162] [NEW] Support "Clear Form" item in suggestions popup

[Chris Coulson]

Public bug reported:

Chrome has a "Clear Form" item in the autofill suggestions popup. We
should probably display something like this in Oxide too
(POPUP_ITEM_ID_CLEAR_FORM).

** 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/1678162

Title:
  Support "Clear Form" item in suggestions popup

Status in Oxide:
  Triaged

Bug description:
  Chrome has a "Clear Form" item in the autofill suggestions popup. We
  should probably display something like this in Oxide too
  (POPUP_ITEM_ID_CLEAR_FORM).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678162/+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 1678164] [NEW] Handle "not secure" warning in autofill suggestions

[Chris Coulson]

Public bug reported:

Chrome displays a "not secure" warning message item in the autofill
suggestions on insecure pages with password / username fields. Clicking
on the item opens a new tab with an explanation of the message.

We want to handle this in Oxide, but I'm not sure what the UX should be
- should we display a dialog with information in it?

** 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/1678164

Title:
  Handle "not secure" warning in autofill suggestions

Status in Oxide:
  Triaged

Bug description:
  Chrome displays a "not secure" warning message item in the autofill
  suggestions on insecure pages with password / username fields.
  Clicking on the item opens a new tab with an explanation of the
  message.

  We want to handle this in Oxide, but I'm not sure what the UX should
  be - should we display a dialog with information in it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678164/+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 1678156] [NEW] Add an API for manipulating credit cards

[Chris Coulson]

Public bug reported:

There needs to be an API for manipulating stored credit card details.

** 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/1678156

Title:
  Add an API for manipulating credit cards

Status in Oxide:
  Triaged

Bug description:
  There needs to be an API for manipulating stored credit card details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678156/+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 1678155] [NEW] Support autofilling credit card info

[Chris Coulson]

Public bug reported:

Add support for autofilling credit card info.

** 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/1678155

Title:
  Support autofilling credit card info

Status in Oxide:
  Triaged

Bug description:
  Add support for autofilling credit card info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678155/+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 1678151] [NEW] Add an API for manipulating autofill profiles

[Chris Coulson]

Public bug reported:

The browser needs an API for manipulating autofill profiles

** 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/1678151

Title:
  Add an API for manipulating autofill profiles

Status in Oxide:
  Triaged

Bug description:
  The browser needs an API for manipulating autofill profiles

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678151/+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 1678119] [NEW] Fails to build in zesty (missing linux/dma-buf.h)

[Chris Coulson]

Public bug reported:

FAILED: obj/ui/gfx/memory_buffer_sources/client_native_pixmap_dmabuf.o 
/usr/bin/c++ -MMD -MF 
obj/ui/gfx/memory_buffer_sources/client_native_pixmap_dmabuf.o.d 
-DGFX_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DDISABLE_NACL 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DOXIDE_BUILD -I../.. -Igen 
-I../../third_party/libdrm/src -I../../third_party/libdrm/src/include 
-I../../third_party/libdrm/src/include/drm -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -Wno-builtin-macro-redefined 
-D__DATE__= -D__TIME__= -D__TIMESTAMP__= -funwind-tables -fPIC -pipe -m64 
-march=x86-64 -pthread -Wall -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter
  -O2 -fno-ident -fdata-sections -ffunction-sections -g2 -fvisibility=hidden 
-fvisibility-inlines-hidden -fno-delete-null-pointer-checks -std=gnu++11 
-Wno-narrowing -fno-rtti -fno-exceptions -c 
../../ui/gfx/linux/client_native_pixmap_dmabuf.cc -o 
obj/ui/gfx/memory_buffer_sources/client_native_pixmap_dmabuf.o
../../ui/gfx/linux/client_native_pixmap_dmabuf.cc:39:27: fatal error: 
linux/dma-buf.h: No such file or directory
 #include 
   ^
compilation terminated.

** Affects: oxide
 Importance: Critical
 Status: Triaged

** 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/1678119

Title:
  Fails to build in zesty (missing linux/dma-buf.h)

Status in Oxide:
  Triaged

Bug description:
  FAILED: obj/ui/gfx/memory_buffer_sources/client_native_pixmap_dmabuf.o 
  /usr/bin/c++ -MMD -MF 
obj/ui/gfx/memory_buffer_sources/client_native_pixmap_dmabuf.o.d 
-DGFX_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DDISABLE_NACL 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DOXIDE_BUILD -I../.. -Igen 
-I../../third_party/libdrm/src -I../../third_party/libdrm/src/include 
-I../../third_party/libdrm/src/include/drm -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -Wno-builtin-macro-redefined 
-D__DATE__= -D__TIME__= -D__TIMESTAMP__= -funwind-tables -fPIC -pipe -m64 
-march=x86-64 -pthread -Wall -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-paramet
 er -O2 -fno-ident -fdata-sections -ffunction-sections -g2 -fvisibility=hidden 
-fvisibility-inlines-hidden -fno-delete-null-pointer-checks -std=gnu++11 
-Wno-narrowing -fno-rtti -fno-exceptions -c 
../../ui/gfx/linux/client_native_pixmap_dmabuf.cc -o 
obj/ui/gfx/memory_buffer_sources/client_native_pixmap_dmabuf.o
  ../../ui/gfx/linux/client_native_pixmap_dmabuf.cc:39:27: fatal error: 
linux/dma-buf.h: No such file or directory
   #include 
 ^
  compilation terminated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678119/+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 1678039] [NEW] Ensure we correctly configure WebPreferences required for pointer media queries

[Chris Coulson]

Public bug reported:

content::WebPreferences has several members that are used by blink for
the pointer and hover CSS media queries:

- available_pointer_types
- primary_pointer_type
- available_hover_types
- primary_hover_type

These are currently set in Chromium using functions from
ui/base/touch/touch_device.h, the Linux implementations of which rely on
ui::InputDeviceManager which isn't wired up in Oxide.

** Affects: oxide
 Importance: Medium
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
   Importance: High => 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/1678039

Title:
  Ensure we correctly configure WebPreferences required for pointer
  media queries

Status in Oxide:
  Triaged

Bug description:
  content::WebPreferences has several members that are used by blink for
  the pointer and hover CSS media queries:

  - available_pointer_types
  - primary_pointer_type
  - available_hover_types
  - primary_hover_type

  These are currently set in Chromium using functions from
  ui/base/touch/touch_device.h, the Linux implementations of which rely
  on ui::InputDeviceManager which isn't wired up in Oxide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1678039/+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 1676224] [NEW] Make it possible to run Chromium's content shell

[Chris Coulson]

Public bug reported:

So that we can run layout tests and content browser tests

** Affects: oxide
 Importance: Undecided
 Assignee: Chris Coulson (chrisccoulson)
 Status: In Progress

** Changed in: oxide
   Status: New => In Progress

** 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/1676224

Title:
  Make it possible to run Chromium's content shell

Status in Oxide:
  In Progress

Bug description:
  So that we can run layout tests and content browser tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1676224/+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 1676027] [NEW] Build the x11 ozone platform

[Chris Coulson]

Public bug reported:

See bug 1675963 - I want to try to get Chromium's content shell working
out of an Oxide build tree. For that, we need a full featured ozone
platform, so let's enable the x11 platform.

** 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/1676027

Title:
  Build the x11 ozone platform

Status in Oxide:
  New

Bug description:
  See bug 1675963 - I want to try to get Chromium's content shell
  working out of an Oxide build tree. For that, we need a full featured
  ozone platform, so let's enable the x11 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1676027/+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 1675963] [NEW] Get rid of oxide bits in //ui/gl/init

[Chris Coulson]

Public bug reported:

We currently replace the ozone bits in //ui/gl/init with Oxide
implementations. This originates from a time when Chromium/Ozone builds
didn't support GLX, but that's not the case anymore.

I want to try to get Chromium's content shell working from an Oxide
build in order to run the blink layout tests. The content shell will
communicate directly with the windowing system rather than using Oxide,
and so will require a full featured ozone platform. As part of this, I'm
planning to enable the x11 ozone platform for Oxide builds, but in order
to make this work, the ozone bits in //ui/gl/init need to be re-enabled.

** Affects: oxide
 Importance: Medium
 Assignee: Chris Coulson (chrisccoulson)
 Status: Fix Committed

** 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/1675963

Title:
  Get rid of oxide bits in //ui/gl/init

Status in Oxide:
  Fix Committed

Bug description:
  We currently replace the ozone bits in //ui/gl/init with Oxide
  implementations. This originates from a time when Chromium/Ozone
  builds didn't support GLX, but that's not the case anymore.

  I want to try to get Chromium's content shell working from an Oxide
  build in order to run the blink layout tests. The content shell will
  communicate directly with the windowing system rather than using
  Oxide, and so will require a full featured ozone platform. As part of
  this, I'm planning to enable the x11 ozone platform for Oxide builds,
  but in order to make this work, the ozone bits in //ui/gl/init need to
  be re-enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1675963/+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 1638852] Re: Add touch selection handles and quick menu to UbuntuWebView

[Chris Coulson]

** 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/1638852

Title:
  Add touch selection handles and quick menu to UbuntuWebView

Status in Oxide:
  Fix Released

Bug description:
  UbuntuWebView should have touch selection handles and the quick menu
  OOTB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1638852/+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 1674777] [NEW] Add QML tests for touch editing menu

[Chris Coulson]

Public bug reported:

TouchEditingMenuControllerImpl has quite extensive unit tests, but there
are no QML tests for the menu because the QML test harness doesn't
provide an API to inject touch events (we hit this limitation for
LocationBarController too).

Oxide should probably provide a test API for this.

** 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/1674777

Title:
  Add QML tests for touch editing menu

Status in Oxide:
  Triaged

Bug description:
  TouchEditingMenuControllerImpl has quite extensive unit tests, but
  there are no QML tests for the menu because the QML test harness
  doesn't provide an API to inject touch events (we hit this limitation
  for LocationBarController too).

  Oxide should probably provide a test API for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1674777/+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 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

[Chris Coulson]

** Changed in: oxide/1.21
   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/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665978/+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 1668614] Re: Fails to build with gcc 4.8

[Chris Coulson]

** Changed in: oxide/1.21
   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/1668614

Title:
  Fails to build with gcc 4.8

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Fix Released

Bug description:
  FAILED: /usr/bin/x86_64-linux-gnu-gcc -MMD -MF 
obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavutil_cpu.o.d 
-DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
-DFF_API_CONVERGENCE_DURATION=0 -D_ISOC99_SOURCE -D_LARGEFILE_SOURCE 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT 
-DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DUSE_EXTERNAL_POPUP_MENU=1 -DDISABLE_NACL -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/x64 
-I../../third_party/ffmpeg -I../.. -Igen -I../../third_party/opus/src/include 
-fPIC -fomit-frame-pointer -Wno-deprecated-declarations -w -std=c99 -pthread 
-fno-math-errno -fno-signed-zeros -fno-tree-vectorize -fomit-fr
 ame-pointer -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
-funwind-tables -fPIC -pipe -m64 -march=x86-64 -pthread -g1 
-Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -fvisibility=default  -c 
../../third_party/ffmpeg/libavutil/autorename_libavutil_cpu.c -o 
obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavutil_cpu.o
  In file included from 
../../third_party/ffmpeg/libavutil/autorename_libavutil_cpu.c:2:0:
  ../../third_party/ffmpeg/libavutil/cpu.c:24:23: fatal error: stdatomic.h: No 
such file or directory
   #include 
 ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1668614/+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 1673022] [NEW] Set FileDialog::nameFilters to an appropriate value

[Chris Coulson]

Public bug reported:

There is a TODO in the file dialog implementation:

+  // TODO: Find correct mapping from mimetypes to namefilter.
+  // nameFilters does filtering of file based on file extension and
+  // no clear mapping available from mimetypes to file extension, so allow
+  // all files to avoid any inconsistency as of now.
+  nameFilters: ["All files (*)"]

This can use net::GetExtensionsForMimeType. I don't think there's a Qt
API for it (or, at least I couldn't find one).

Also, the descriptions "All files" and any additional ones (like
"Images" or "Videos") need to be localized.

** Affects: oxide
 Importance: High
 Assignee: Santosh (santoshbit2007)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
 Assignee: (unassigned) => Santosh (santoshbit2007)

-- 
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/1673022

Title:
  Set FileDialog::nameFilters to an appropriate value

Status in Oxide:
  Triaged

Bug description:
  There is a TODO in the file dialog implementation:

  +  // TODO: Find correct mapping from mimetypes to namefilter.
  +  // nameFilters does filtering of file based on file extension and
  +  // no clear mapping available from mimetypes to file extension, so allow
  +  // all files to avoid any inconsistency as of now.
  +  nameFilters: ["All files (*)"]

  This can use net::GetExtensionsForMimeType. I don't think there's a Qt
  API for it (or, at least I couldn't find one).

  Also, the descriptions "All files" and any additional ones (like
  "Images" or "Videos") need to be localized.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1673022/+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 1672707] [NEW] Rethink file picker fallback

[Chris Coulson]

Public bug reported:

The initial FilePicker implementation in Oxide tries to open a
ContentPeerPicker and then falls back to a standard FileDialog if that
fails. The problem with this is that webbrowser-app depends on content-
hub, so opening a ContentPeerPicker will always succeed in any
application, even in scenarios where it displays no useful peers and the
application could open a standard file dialog.

The way I think this could work is:

- If ContentPeerModel indicates there are no peers (or the only peer is the 
current app) AND application confinement doesn't prevent the application from 
browsing the home directory, open a FileDialog, else open the ContentPeerPicker.
- When displaying the ContentPeerPicker, if application confinement doesn't 
prevent the application from browsing the home directory, display a button at 
the bottom of the window to switch to a FileDialog.

** 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/1672707

Title:
  Rethink file picker fallback

Status in Oxide:
  Triaged

Bug description:
  The initial FilePicker implementation in Oxide tries to open a
  ContentPeerPicker and then falls back to a standard FileDialog if that
  fails. The problem with this is that webbrowser-app depends on
  content-hub, so opening a ContentPeerPicker will always succeed in any
  application, even in scenarios where it displays no useful peers and
  the application could open a standard file dialog.

  The way I think this could work is:

  - If ContentPeerModel indicates there are no peers (or the only peer is the 
current app) AND application confinement doesn't prevent the application from 
browsing the home directory, open a FileDialog, else open the ContentPeerPicker.
  - When displaying the ContentPeerPicker, if application confinement doesn't 
prevent the application from browsing the home directory, display a button at 
the bottom of the window to switch to a FileDialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1672707/+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 1642317] Re: armhf build fails

[Chris Coulson]

** 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/1642317

Title:
  armhf build fails

Status in Oxide:
  Fix Released

Bug description:
  This doesn't seem to affect cross builds, but only archive builds:

  [13145/19378] python ../../v8/tools/run.py ./mksnapshot --startup_src 
gen/v8/snapshot.cc --random-seed 314159265 --startup_blob snapshot_blob.bin
  FAILED: gen/v8/snapshot.cc snapshot_blob.bin 
  python ../../v8/tools/run.py ./mksnapshot --startup_src gen/v8/snapshot.cc 
--random-seed 314159265 --startup_blob snapshot_blob.bin
  ninja: build stopped: subcommand failed.
  oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
  make[4]: *** [oxide/CMakeFiles/build_all] Error 1
  make[4]: Leaving directory '/<>/obj-arm-linux-gnueabihf'
  CMakeFiles/Makefile2:234: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
  make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
  make[3]: Leaving directory '/<>/obj-arm-linux-gnueabihf'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/obj-arm-linux-gnueabihf'
  dh_auto_build: make -j4 returned exit code 2
  debian/rules:20: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:14: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642317/+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 1668614] Re: Fails to build with gcc 4.8

[Chris Coulson]

** 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/1668614

Title:
  Fails to build with gcc 4.8

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Triaged

Bug description:
  FAILED: /usr/bin/x86_64-linux-gnu-gcc -MMD -MF 
obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavutil_cpu.o.d 
-DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
-DFF_API_CONVERGENCE_DURATION=0 -D_ISOC99_SOURCE -D_LARGEFILE_SOURCE 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT 
-DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DUSE_EXTERNAL_POPUP_MENU=1 -DDISABLE_NACL -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/x64 
-I../../third_party/ffmpeg -I../.. -Igen -I../../third_party/opus/src/include 
-fPIC -fomit-frame-pointer -Wno-deprecated-declarations -w -std=c99 -pthread 
-fno-math-errno -fno-signed-zeros -fno-tree-vectorize -fomit-fr
 ame-pointer -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
-funwind-tables -fPIC -pipe -m64 -march=x86-64 -pthread -g1 
-Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -fvisibility=default  -c 
../../third_party/ffmpeg/libavutil/autorename_libavutil_cpu.c -o 
obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavutil_cpu.o
  In file included from 
../../third_party/ffmpeg/libavutil/autorename_libavutil_cpu.c:2:0:
  ../../third_party/ffmpeg/libavutil/cpu.c:24:23: fatal error: stdatomic.h: No 
such file or directory
   #include 
 ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1668614/+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 1667822] [NEW] Investigate making qquick::ContentsView a QQuickItem

[Chris Coulson]

Public bug reported:

Currently OxideQQuickWebView proxies a bunch of calls through to
qquick::ContentsView. I've been thinking about devtools recently, and I
want to make the webview inspectable (ie, make it support displaying
Chromium's docked devtools UI and have it be invokable from the context
menu). To make the devtools panel undockable, there will be a new client
of qquick::ContentsView which will essentially be a window with a
WebContents embedder in it. It would be nice to not have to duplicate a
bunch of code to just proxy calls through to ContentsView.

** 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/1667822

Title:
  Investigate making qquick::ContentsView a QQuickItem

Status in Oxide:
  Triaged

Bug description:
  Currently OxideQQuickWebView proxies a bunch of calls through to
  qquick::ContentsView. I've been thinking about devtools recently, and
  I want to make the webview inspectable (ie, make it support displaying
  Chromium's docked devtools UI and have it be invokable from the
  context menu). To make the devtools panel undockable, there will be a
  new client of qquick::ContentsView which will essentially be a window
  with a WebContents embedder in it. It would be nice to not have to
  duplicate a bunch of code to just proxy calls through to ContentsView.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1667822/+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 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

[Chris Coulson]

** 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/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665978/+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 1666002] Re: IME won't work with OOPIF

[Chris Coulson]

https://git.launchpad.net/oxide/commit/?id=20049094b2d7c64ade5d2f6af81362207513a046

** 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/1666002

Title:
  IME won't work with OOPIF

Status in Oxide:
  Fix Released

Bug description:
  Oxide currently overrides RWHV::OnSelectionBoundsChanged and
  RWHV::OnSelectionChanged for IME support, but this won't work for
  cross-process sub-frames.

  We need to stop overriding these methods (the default implementations
  integrate with TextInputManager), and instead implement the
  TextInputManager::Observer interface, which will receive events from
  cross-process views.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1666002/+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 1666866] [NEW] Stop continuously updating WebView::editingCapabilities

[Chris Coulson]

Public bug reported:

Updating WebView::editingCapabilities isn't cheap if the clipboard
selection owner changes because we need to read data from the clipboard
to update the paste bit. Previous experience suggests this can take
>100ms in some cases. This used to be a bigger problem, although it was
improved significantly by caching clipboard status.

However, as part of bug 1666002, we're going to be refreshing
WebView::editingCapabilities from more callbacks. This is wasteful, and
I'd prefer we just stopped doing it.

In addition to this, CanUndo and CanRedo are always unset, because there
is currently no visibility of this on the browser side and no way to get
notifications for them from blink.

What we should do is:
- Stop continuously updating WebView::editingCapabilities.
- Add a new method to WebView to trigger an asynchronous refresh of the 
WebView::editingCapabilities. property. Applications can call this when 
displaying a UI that requires it (such as a window menu). This will perform a 
renderer round trip to get the undo/redo capabilities from blink.
- Refresh WebView::editingCapabilities when displaying the touch editing UI, to 
avoid breaking what looks like the only consumer of this API in webbrowser-app.

** Affects: oxide
 Importance: Medium
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
   Status: New => Triaged

** Description changed:

  Updating WebView::editingCapabilities isn't cheap if the clipboard
  selection owner changes because we need to read data from the clipboard
- to update the paste bit. This used to be a bigger problem, although it
- was improved significantly by caching clipboard status.
+ to update the paste bit. Previous experience suggests this can take
+ >100ms in some cases. This used to be a bigger problem, although it was
+ improved significantly by caching clipboard status.
  
  However, as part of bug 1666002, we're going to be refreshing
  WebView::editingCapabilities from more callbacks. This is wasteful, and
  I'd prefer we just stopped doing it.
  
  In addition to this, CanUndo and CanRedo are always unset, because there
  is currently no visibility of this on the browser side and no way to get
  notifications for them from blink.
  
  What we should do is:
  - Stop continuously updating WebView::editingCapabilities.
  - Add a new method to WebView to trigger an asynchronous refresh of the 
WebView::editingCapabilities. property. Applications can call this when 
displaying a UI that requires it (such as a window menu).
  - Refresh WebView::editingCapabilities when displaying the touch editing UI, 
to avoid breaking what looks like the only consumer of this API in 
webbrowser-app.

** Description changed:

  Updating WebView::editingCapabilities isn't cheap if the clipboard
  selection owner changes because we need to read data from the clipboard
  to update the paste bit. Previous experience suggests this can take
  >100ms in some cases. This used to be a bigger problem, although it was
  improved significantly by caching clipboard status.
  
  However, as part of bug 1666002, we're going to be refreshing
  WebView::editingCapabilities from more callbacks. This is wasteful, and
  I'd prefer we just stopped doing it.
  
  In addition to this, CanUndo and CanRedo are always unset, because there
  is currently no visibility of this on the browser side and no way to get
  notifications for them from blink.
  
  What we should do is:
  - Stop continuously updating WebView::editingCapabilities.
- - Add a new method to WebView to trigger an asynchronous refresh of the 
WebView::editingCapabilities. property. Applications can call this when 
displaying a UI that requires it (such as a window menu).
+ - Add a new method to WebView to trigger an asynchronous refresh of the 
WebView::editingCapabilities. property. Applications can call this when 
displaying a UI that requires it (such as a window menu). This will perform a 
renderer round trip to get the undo/redo capabilities from blink.
  - Refresh WebView::editingCapabilities when displaying the touch editing UI, 
to avoid breaking what looks like the only consumer of this API in 
webbrowser-app.

-- 
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/1666866

Title:
  Stop continuously updating WebView::editingCapabilities

Status in Oxide:
  Triaged

Bug description:
  Updating WebView::editingCapabilities isn't cheap if the clipboard
  selection owner changes because we need to read data from the
  clipboard to update the paste bit. Previous experience suggests this
  can take >100ms in some cases. This used to be a bigger problem,
  although it was improved significantly by caching clipboard status.

  However, as part of bug 1666002, we're going to be refreshing
  WebView::editingCapabilities from more callbacks. This is wasteful,
  and I'd 

[Ubuntu-webapps-bugs] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

[Chris Coulson]

** Changed in: webbrowser-app (Ubuntu)
   Status: New => 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/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665978/+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 1546648] Re: Add support for input event routing in the browser process

[Chris Coulson]

** Changed in: oxide
   Status: Triaged => Fix Released

** 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/1546648

Title:
  Add support for input event routing in the browser process

Status in Oxide:
  Fix Released

Bug description:
  To support OOPIF, we need to add support for browser-side quad-based
  hit-testing for input events, so that they get routed to the correct
  render process. Other Chrome platforms already have this.

  See https://docs.google.com/document/d/1RQUbxiK60Z7CZDcWeryqKeX-
  bewZzgsirjF2Dprfx3U

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1546648/+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 1665383] Re: Clean up location bar offset update tracking

[Chris Coulson]

https://git.launchpad.net/oxide/commit/?id=b1c45249c8662047184d366c530416183df4b22e

** Changed in: oxide
   Status: In Progress => Fix Released

** Changed in: oxide
Milestone: None => branch-1.22

-- 
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/1665383

Title:
  Clean up location bar offset update tracking

Status in Oxide:
  Fix Released

Bug description:
  We pass cc::CompositorFrameMetadata around to a few places - a couple
  of which are interested in the location bar position, and each
  responsible for attempting to synchronize updates to this with the
  compositor.

  The touch editing menu implementation needs to be aware of location
  bar position updates, but there's currently no good way of plumbing
  this in. It seems we've hit this issue in the past but just worked
  around it rather than fixing it, eg:

  
https://git.launchpad.net/oxide/tree/shared/browser/oxide_render_widget_host_view.cc?id=40441702cbbe4e4e45a70d0571d5a63fb1eb#n456

  This code works around the fact that the touch handle drawables aren't
  aware of location bar position updates, but they should be.

  Also, where coordinates are transformed for the location bar position
  isn't very consistent - eg, input events are transformed in qt/,
  whereas coordinates for the popup menu and other bits are transformed
  in shared/.

  Time to clean this up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665383/+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 1665722] [NEW] Location bar content offset transformation for MotionEvents should move to shared/

[Chris Coulson]

Public bug reported:

With bug 1665383 fixed, the only thing outside of shared/ that cares
about the location bar content offset is qt::MotionEventFactory. We
should fix this, but it's a reasonable amount of work, which is why I've
split this from bug 1665383.

** 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/1665722

Title:
  Location bar content offset transformation for MotionEvents should
  move to shared/

Status in Oxide:
  Triaged

Bug description:
  With bug 1665383 fixed, the only thing outside of shared/ that cares
  about the location bar content offset is qt::MotionEventFactory. We
  should fix this, but it's a reasonable amount of work, which is why
  I've split this from bug 1665383.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665722/+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 1665655] [NEW] Scrolling over addressbar shouldn't scroll webview

[Chris Coulson]

Public bug reported:

Steps to reproduce:

1) Move mouse pointer to addressbar (over the text entry).
2) Use the scroll wheel.

What should happen:

Nothing

What happens:

The webview content scrolls

** Affects: oxide
 Importance: Medium
 Status: Triaged

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
   Status: New => Triaged

** Also affects: webbrowser-app (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/1665655

Title:
  Scrolling over addressbar shouldn't scroll webview

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Move mouse pointer to addressbar (over the text entry).
  2) Use the scroll wheel.

  What should happen:

  Nothing

  What happens:

  The webview content scrolls

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665655/+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 1665633] [NEW] Context menu only opens downwards if there's not enough space above

[Chris Coulson]

Public bug reported:

I would expect the context menu to open downwards in all cases, except
in the case where there isn't enough space to. But it always seems to
open upwards.

There are tests that verify the position is as expected, but the
elements tested are all near the top of the webview.

** Affects: oxide
 Importance: High
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
Milestone: None => branch-1.22

-- 
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/1665633

Title:
  Context menu only opens downwards if there's not enough space above

Status in Oxide:
  Triaged

Bug description:
  I would expect the context menu to open downwards in all cases, except
  in the case where there isn't enough space to. But it always seems to
  open upwards.

  There are tests that verify the position is as expected, but the
  elements tested are all near the top of the webview.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665633/+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 1665383] [NEW] Clean up location bar offset update tracking

[Chris Coulson]

Public bug reported:

We pass cc::CompositorFrameMetadata around to a few places - a couple of
which are interested in the location bar position, and each responsible
for attempting to synchronize updates to this with the compositor.

The touch editing menu implementation needs to be aware of location bar
position updates, but there's currently no good way of plumbing this in.
It seems we've hit this issue in the past but just worked around it
rather than fixing it, eg:

https://git.launchpad.net/oxide/tree/shared/browser/oxide_render_widget_host_view.cc?id=40441702cbbe4e4e45a70d0571d5a63fb1eb#n456

This code works around the fact that the touch handle drawables aren't
aware of location bar position updates, but they should be.

Also, where coordinates are transformed for the location bar position
isn't very consistent - eg, input events are transformed in qt/, whereas
coordinates for the popup menu and other bits are transformed in
shared/.

Time to clean this up.

** Affects: oxide
 Importance: High
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
   Status: New => Triaged

** 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/1665383

Title:
  Clean up location bar offset update tracking

Status in Oxide:
  Triaged

Bug description:
  We pass cc::CompositorFrameMetadata around to a few places - a couple
  of which are interested in the location bar position, and each
  responsible for attempting to synchronize updates to this with the
  compositor.

  The touch editing menu implementation needs to be aware of location
  bar position updates, but there's currently no good way of plumbing
  this in. It seems we've hit this issue in the past but just worked
  around it rather than fixing it, eg:

  
https://git.launchpad.net/oxide/tree/shared/browser/oxide_render_widget_host_view.cc?id=40441702cbbe4e4e45a70d0571d5a63fb1eb#n456

  This code works around the fact that the touch handle drawables aren't
  aware of location bar position updates, but they should be.

  Also, where coordinates are transformed for the location bar position
  isn't very consistent - eg, input events are transformed in qt/,
  whereas coordinates for the popup menu and other bits are transformed
  in shared/.

  Time to clean this up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665383/+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 1665381] [NEW] Replace Render{Frame, Widget}HostID with a weak pointer class

[Chris Coulson]

Public bug reported:

We have this helper class for storing IDs that's used in a few places,
but it's used like a weak pointer. We should just make this in to a
weak-pointer-like class instead.

** Affects: oxide
 Importance: Low
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Low

** Changed in: oxide
   Status: New => Triaged

** 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/1665381

Title:
  Replace Render{Frame,Widget}HostID with a weak pointer class

Status in Oxide:
  Triaged

Bug description:
  We have this helper class for storing IDs that's used in a few places,
  but it's used like a weak pointer. We should just make this in to a
  weak-pointer-like class instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1665381/+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 1663609] [NEW] Leak BrowserProcessMain at shutdown

[Chris Coulson]

Public bug reported:

We currently run the BrowserProcessMain destructor at process exit, but
this results in a CHECK failure in the event of an unclean shutdown (ie,
anything outside of Oxide just calling exit()).

See, eg, bug 1560994 and bug 1649262 - both bugs originally reported
against Oxide but are actually nothing to do with it.

Given that most singletons in Chromium are already leaky, we should
probably just leak this too.

** Affects: oxide
 Importance: High
 Assignee: Chris Coulson (chrisccoulson)
 Status: 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/1663609

Title:
  Leak BrowserProcessMain at shutdown

Status in Oxide:
  Fix Released

Bug description:
  We currently run the BrowserProcessMain destructor at process exit,
  but this results in a CHECK failure in the event of an unclean
  shutdown (ie, anything outside of Oxide just calling exit()).

  See, eg, bug 1560994 and bug 1649262 - both bugs originally reported
  against Oxide but are actually nothing to do with it.

  Given that most singletons in Chromium are already leaky, we should
  probably just leak this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1663609/+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 1649262] Re: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

[Chris Coulson]

This is not a bug in Oxide - the CHECK failure in this case is a red
herring and is a side effect of a bug elsewhere that triggers an unclean
exit() (see bug 1663609)

** Project changed: oxide => qtdeclarative-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/1649262

Title:
  webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

Status in Canonical System Image:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  17.04 unity7

  ~$ webbrowser-app 
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  UCUriHandler: Empty "APP_ID" environment variable, ignoring.
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information
  could not open containers config file  
"/home/pixel/.local/share/libertine/ContainersConfig.json"
  APP_ID isn't set, the handler can not be registered
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
  Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
  Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" 
QFlags(0x2)
  Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
  Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

  (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not 
connect: Permission denied
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  APP_ID isn't set, the handler ignored
  qml: Loaded 13 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  ^CSegmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649262/+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 1663572] [NEW] Add an API to request the application brings a webview in to the foreground

[Chris Coulson]

Public bug reported:

We should expose a webview signal that fires off of
WebContentsDelegate::ActivateContents() - the use case for this is that
if a user action results in a navigation in another window (eg, clicking
on a  element with a target attribute), there should be a mechanism
to request that the webview hosting the target window is focused.

There may be another use case for this - focusing a webview that has a
pending alert dialog.

** 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/1663572

Title:
  Add an API to request the application brings a webview in to the
  foreground

Status in Oxide:
  Triaged

Bug description:
  We should expose a webview signal that fires off of
  WebContentsDelegate::ActivateContents() - the use case for this is
  that if a user action results in a navigation in another window (eg,
  clicking on a  element with a target attribute), there should be a
  mechanism to request that the webview hosting the target window is
  focused.

  There may be another use case for this - focusing a webview that has a
  pending alert dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1663572/+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 1603729] Re: [Oxide 1.18] webapp option --enable-media-hub-audio breaks audio stream

[Chris Coulson]

** Changed in: oxide
   Status: New => Fix Released

** Changed in: oxide
Milestone: None => branch-1.22

-- 
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/1603729

Title:
  [Oxide 1.18] webapp option --enable-media-hub-audio breaks audio
  stream

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in media-hub package in Ubuntu:
  In Progress

Bug description:
  My webapp "KlassikRadio" does not work any more.

  Opening the webapp opens the window as expected. Nevertheless the
  audio keeps dry. The phone remains silent.

  I have played around and found out that the option: --enable-media-
  hub-audio breaks the audio stream. When I take this option off the
  KlassikRadio.desktop file it works.

  I am using:

  current build number: 387
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-07-16 08:46:05
  version version: 387
  version ubuntu: 20160716
  version device: 20160606-ab415b2
  version custom: 20160701-981-38-14

  Nevertheless this issue is around since several weeks. I assume the
  option still works with OTA11 but I can not proof this right now.

  Can someone have a look? Is the option not available any more in the
  latest release or is it just a bug? The option is still mentioned in:

  https://developer.ubuntu.com/en/phone/web/ubuntu-webapps-guide/

  Thanks for your support. If someone wants to test this, the
  KlassikRadio app version 0.30 has this option enabled. I will put
  another version (0.31) in the store in the next days before OTA12
  comes along, where I will take this option out and replace it with
  "keep-display-on" in the apparmor-file.

  The keep-display-on solution is not nice. Are there any other options
  I could use alternatively?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603729/+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 1644460] Re: Fails to build because of media-hub, again

[Chris Coulson]

** 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/1644460

Title:
  Fails to build because of media-hub, again

Status in Oxide:
  Fix Released
Status in Oxide 1.20 series:
  Won't Fix
Status in Oxide 1.21 series:
  Triaged

Bug description:
  AILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
obj/oxide/shared/shared/oxide_content_renderer_client.o.d 
-DOXIDE_SUBPROCESS_PATH=\"oxide-qt/oxide-renderer\" 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DOXIDE_SHARED_IMPLEMENTATION 
-DENABLE_MEDIAHUB -DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS 
-DENABLE_PDF=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DENABLE_HYBRIS 
-DENABLE_HYBRIS_CAMERA -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DOXIDE_BUILD 
-DOXIDE_BUILD -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 
-DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE 
-DSK_IGNORE_DW_GRAY_FIX -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS 
-DSK_SUPPORT_GPU=1 -DGOOGLE_PROTOBUF_NO_RTTI 
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DOXIDE_BUILD 
-DV8_USE_EXTERNAL_STARTUP_DATA -DOPUS_FIXED_POINT -DMESA_EGL_NO_X11_HEADERS 
-I../.. -Igen -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../../oxide -Igen/oxide 
-I../../third_party/khronos -I../../gpu -I../../third_party/libwebp 
-I../../third_party/re2/src -Igen/oxide/shared -I../../third_party/ced/src 
-I../../third_party/icu/source/common -I../../third_party/icu/source/i18n 
-I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c 
-I../../third_party/skia/include/config -I../../third_party/skia/include/core 
-I../../third_party/skia/include/effects 
-I../../third_party/skia/include/images -I../../third_party/skia/include/lazy 
-I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf 
-I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports 
-I../../third_party/skia/include/utils -I../../third_party/skia/include/gpu 
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl 
-I../../third_party/protobuf/src -Igen/protoc_out 
-I../../third_party/protobuf/src -I../../third_party/libwebm/source 
-I../../third_party/opus/src/include -I../../third_party/boringssl/src/include 
-I/usr/include/nss -I/usr/include/nspr -Igen -I../../third_party/WebKit 
-Igen/third_party/WebKit -I../../v8/include -Igen/v8/include -I../../v8/include 
-Igen/v8/include -I../../third_party/mesa/src/include 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/arm-neon 
-I../../third_party/ffmpeg -I/usr/include/dbus-1.0 
-I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -mfpu=neon 
-mthumb -Wall -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g1 -fvisibility=hidden 
-fno-threadsafe-statics -fvisibility-inlines-hidden 
-fno-delete-null-pointer-checks -std=gnu++11 -Wno-narrowing -fno-rtti 
-fno-exceptions -c ../../oxide/shared/renderer/oxide_content_renderer_client.cc 
-o obj/oxide/shared/shared/oxide_content_renderer_client.o
  In file included from 
../../oxide/shared/renderer/oxide_content_renderer_client.cc:53:0:
  ../../oxide/shared/renderer/media/oxide_web_media_player.h:170:8: error: 
conflicting return type specified for ‘virtual void 
oxide::WebMediaPlayer::OnSuspendRequested(bool)’
 void OnSuspendRequested(bool must_suspend) override;
  ^
  In file included from 
../../oxide/shared/renderer/media/oxide_web_media_player.h:21:0,
   from 
../../oxide/shared/renderer/oxide_content_renderer_client.cc:53:
  ../../media/blink/webmediaplayer_delegate.h:37:18: error:   overriding 
‘virtual bool media::WebMediaPlayerDelegate::Observer::OnSuspendRequested(bool)’
   virtual bool OnSuspendRequested(bool must_suspend) = 0;
^
  ninja: build stopped: subcommand failed.

To manage notifications 

[Ubuntu-webapps-bugs] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

[Chris Coulson]

The abort here is a red herring and is masking the primary issue, which
you can see a few frames further down:

#5  0x7f87c8e3d088 in __run_exit_handlers (status=status@entry=1, 
listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
atfct = 
onfct = 
cxafct = 
#6  0x7f87c8e3d0d5 in __GI_exit (status=status@entry=1) at exit.c:104
No locals.
#7  0x7f87bd0d2ea1 in gdk_x_io_error (display=) at 
/build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkmain-x11.c:544
No locals.
#8  0x7f87c8387cee in _XIOError (dpy=dpy@entry=0x5646ce4eb0f0) at 
../../src/XlibInt.c:1464
No locals.
#9  0x7f87c8385d4a in _XReply (dpy=dpy@entry=0x5646ce4eb0f0, 
rep=rep@entry=0x7ffebcbf6160, extra=extra@entry=0, discard=discard@entry=1) at 
../../src/xcb_io.c:708
error = 0x0
c = 
reply = 0x0
current = 0x5646cf5f8b60
__PRETTY_FUNCTION__ = "_XReply"
#10 0x7f87c838148d in XSync (dpy=0x5646ce4eb0f0, discard=0) at 
../../src/Sync.c:44
rep = {type = 167 '\247', revertTo = 98 'b', sequenceNumber = 48319, 
length = 28, focus = 3465286592, pad1 = 0, pad2 = 3166658864, pad3 = 32766, 
pad4 = 32, pad5 = 0}
#11 0x7f87c764deda in dri2SwapBuffers () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#12 0x7f87cb956342 in QGLXContext::swapBuffers(QPlatformSurface*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
No symbol table info available.
#13 0x7f87ca495326 in QOpenGLContext::swapBuffers(QSurface*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
No symbol table info available.
#14 0x7f87cae4978e in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
#15 0x7f87cae4a521 in QSGGuiThreadRenderLoop::event(QEvent*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
#16 0x7f87cb20e05c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#17 0x7f87cb213516 in QApplication::notify(QObject*, QEvent*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#18 0x7f87c9cf45bb in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#19 0x7f87c9d4986d in QTimerInfoList::activateTimers() () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#20 0x7f87c9d49d71 in timerSourceDispatch(_GSource*, int (*)(void*), void*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#21 0x7f87c86cc127 in g_main_context_dispatch () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#22 0x7f87c86cc380 in g_main_context_iterate.isra () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#23 0x7f87c86cc42c in g_main_context_iteration () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#24 0x7f87c9d4aa4f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#25 0x7f87c9cf1d7a in 
QEventLoop::exec(QFlags) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#26 0x7f87c9cf9e1c in QCoreApplication::exec() () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#27 0x5646ccf87e26 in BrowserApplication::run (this=0x7ffebcbf6930) at 
/build/webbrowser-app-W5j7m8/webbrowser-app-0.23+16.04.20160318/src/app/browserapplication.cpp:261
No locals.
#28 0x5646ccf7ca85 in main (argc=1, argv=0x7ffebcbf6a88) at 
/build/webbrowser-app-W5j7m8/webbrowser-app-0.23+16.04.20160318/src/app/webbrowser/webbrowser-app.cpp:122
app = { = { = {}, 
static staticMetaObject = {d = {superdata = 0x7f87cb710140 
, stringdata = 0x5646ccfca9c0 
, data = 0x5646ccfca960 
, static_metacall = 0x5646ccf92bf0 
, relatedMetaObjects = 0x0, extradata = 0x0}}, m_arguments = 
{ = { = {}, {p = 
{static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin = 0, 
end = 0, array = {0x0}}, d = 0x5646ce80fbe0}, d = 0x5646ce80fbe0}}, }, m_engine = 0x5646ce818880, m_window = 0x5646ce8c13c0, m_component = 
0x5646ce8b8570, m_webbrowserWindowProxy = 

[Ubuntu-webapps-bugs] [Bug 1644460] Re: Fails to build because of media-hub, again

[Chris Coulson]

** Also affects: oxide/1.21
   Importance: Undecided
   Status: New

** Changed in: oxide/1.21
   Importance: Undecided => Critical

** Changed in: oxide/1.21
   Status: New => Triaged

** Changed in: oxide/1.20
   Status: Triaged => Won't Fix

** Changed in: oxide
Milestone: branch-1.21 => branch-1.22

-- 
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/1644460

Title:
  Fails to build because of media-hub, again

Status in Oxide:
  Triaged
Status in Oxide 1.20 series:
  Won't Fix
Status in Oxide 1.21 series:
  Triaged

Bug description:
  AILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
obj/oxide/shared/shared/oxide_content_renderer_client.o.d 
-DOXIDE_SUBPROCESS_PATH=\"oxide-qt/oxide-renderer\" 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DOXIDE_SHARED_IMPLEMENTATION 
-DENABLE_MEDIAHUB -DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS 
-DENABLE_PDF=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DENABLE_HYBRIS 
-DENABLE_HYBRIS_CAMERA -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DOXIDE_BUILD 
-DOXIDE_BUILD -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 
-DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE 
-DSK_IGNORE_DW_GRAY_FIX -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS 
-DSK_SUPPORT_GPU=1 -DGOOGLE_PROTOBUF_NO_RTTI 
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DOXIDE_BUILD 
-DV8_USE_EXTERNAL_STARTUP_DATA -DOPUS_FIXED_POINT -DMESA_EGL_NO_X11_HEADERS 
-I../.. -Igen -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../../oxide -Igen/oxide 
-I../../third_party/khronos -I../../gpu -I../../third_party/libwebp 
-I../../third_party/re2/src -Igen/oxide/shared -I../../third_party/ced/src 
-I../../third_party/icu/source/common -I../../third_party/icu/source/i18n 
-I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c 
-I../../third_party/skia/include/config -I../../third_party/skia/include/core 
-I../../third_party/skia/include/effects 
-I../../third_party/skia/include/images -I../../third_party/skia/include/lazy 
-I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf 
-I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports 
-I../../third_party/skia/include/utils -I../../third_party/skia/include/gpu 
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl 
-I../../third_party/protobuf/src -Igen/protoc_out 
-I../../third_party/protobuf/src -I../../third_party/libwebm/source 
-I../../third_party/opus/src/include -I../../third_party/boringssl/src/include 
-I/usr/include/nss -I/usr/include/nspr -Igen -I../../third_party/WebKit 
-Igen/third_party/WebKit -I../../v8/include -Igen/v8/include -I../../v8/include 
-Igen/v8/include -I../../third_party/mesa/src/include 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/arm-neon 
-I../../third_party/ffmpeg -I/usr/include/dbus-1.0 
-I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -mfpu=neon 
-mthumb -Wall -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g1 -fvisibility=hidden 
-fno-threadsafe-statics -fvisibility-inlines-hidden 
-fno-delete-null-pointer-checks -std=gnu++11 -Wno-narrowing -fno-rtti 
-fno-exceptions -c ../../oxide/shared/renderer/oxide_content_renderer_client.cc 
-o obj/oxide/shared/shared/oxide_content_renderer_client.o
  In file included from 
../../oxide/shared/renderer/oxide_content_renderer_client.cc:53:0:
  ../../oxide/shared/renderer/media/oxide_web_media_player.h:170:8: error: 
conflicting return type specified for ‘virtual void 
oxide::WebMediaPlayer::OnSuspendRequested(bool)’
 void OnSuspendRequested(bool must_suspend) override;
  ^
  In file included from 
../../oxide/shared/renderer/media/oxide_web_media_player.h:21:0,
   from 
../../oxide/shared/renderer/oxide_content_renderer_client.cc:53:
  ../../media/blink/webmediaplayer_delegate.h:37:18: 

[Ubuntu-webapps-bugs] [Bug 1642318] Re: arm64 xenial build fails

[Chris Coulson]

** Changed in: oxide/1.20
   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/1642318

Title:
  arm64 xenial build fails

Status in Oxide:
  Fix Released
Status in Oxide 1.20 series:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Invalid
Status in gcc-5 source package in Xenial:
  New

Bug description:
  FAILED: /usr/bin/aarch64-linux-gnu-gcc -MMD -MF 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o.d 
-DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PDF=1 
-DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DNO_TCMALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 
-DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 
-DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../.. -Igen -I../../third_party/libvpx/source/config 
-I../../third_party/libvpx/source/config/linux/arm64 
-I../../third_party/libvpx/source/libvpx -Igen/third_party/libvpx 
-I../../third_party/libvpx/source/libvpx -fno-strict-aliasing 
--param=ssp-buffer-si
 ze=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g1 
-fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function 
-Wno-sign-compare  -c 
../../third_party/libvpx/source/libvpx/vpx_dsp/arm/idct32x32_34_add_neon.c -o 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o
  {standard input}: Assembler messages:
  {standard input}: Error: unaligned opcodes detected in executable segment
  ninja: build stopped: subcommand failed.
  oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
  make[4]: *** [oxide/CMakeFiles/build_all] Error 1
  make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  CMakeFiles/Makefile2:267: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
  make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
  make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  dh_auto_build: make -j4 returned exit code 2
  debian/rules:26: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:20: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642318/+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 1654655] Re: GN bootstrap fails in PPA builds

[Chris Coulson]

I've not seen this issue since

** Changed in: oxide
   Status: Triaged => Invalid

** Changed in: oxide
Milestone: branch-1.21 => 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/1654655

Title:
  GN bootstrap fails in PPA builds

Status in Oxide:
  Invalid

Bug description:
  The latest uploads (71548c4) all fail like this:

  Building gn manually in a temporary directory for bootstrapping...
  -- Generating build files with initial Generate Ninja
  ERROR at build arg file (use "gn args " to edit):12:25: Build 
argument has no effect.
  fatal_linker_warnings = false
  ^
  The variable "fatal_linker_warnings" was set as a build argument
  but never appeared in a declare_args() block in any buildfile.

  To view all possible args, run "gn args --list "
  ERROR No targets.
  I could not find any targets to write, so I'm doing nothing.
  [0106/163659.319124:FATAL:err.cc(161)] Check failed: has_error_. 

  CMake Error at oxide/build/scripts/bootstrap-gn.cmake:68 (message):
Failed to run Generate Ninja

  
  CMake Error at oxide/build/cmake/ChromiumBuildShim.cmake:66 (message):
Failed to bootstrap Generate Ninja binary
  Call Stack (most recent call first):
oxide/build/cmake/ChromiumBuildShim.cmake:298 (_bootstrap_gn)
oxide/CMakeLists.txt:224 (run_generate_ninja)

  
  -- Configuring incomplete, errors occurred!

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654655/+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 1637195] Re: Add JS dialogs to UbuntuWebView

[Chris Coulson]

** Changed in: oxide
   Status: In Progress => Fix Released

** Changed in: oxide
Milestone: None => branch-1.21

-- 
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/1637195

Title:
  Add JS dialogs to UbuntuWebView

Status in Oxide:
  Fix Released

Bug description:
  UbuntuWebView needs support for displaying JS dialogs (alert, confirm,
  before unload, prompt).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1637195/+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 1568296] Re: Make JS dialogs app modal

[Chris Coulson]

** 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/1568296

Title:
  Make JS dialogs app modal

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Chrome only supports app-modal JS dialogs, and so does Blink
  (window.alert blocks the calling process).

  Oxide pretends to support tab-modal JS dialogs by having a per-WebContents 
dispatch queue. However, the behaviour is quite broken:
  - It's really app-modal in single process because there's only a single 
RenderThread.
  - In multi-process it's not really tab-modal - it's render-process modal (ie, 
only a single tab in a render process can show a JS dialog). So, if 2 tabs live 
in separate processes then they can display JS dialogs at the same time. But if 
they're from the same SiteInstance and live in the same process, they can't.

  We should just change the dispatch of JS dialogs to be application
  modal instead, so it behaves consistently in all configurations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1568296/+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 1647799] Re: Don't run ubuntu_ui QML tests when ENABLE_UITK_WEBVIEW isn't defined

[Chris Coulson]

** Changed in: oxide
   Status: In Progress => Fix Released

** Changed in: oxide
Milestone: None => branch-1.21

-- 
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/1647799

Title:
  Don't run ubuntu_ui QML tests when ENABLE_UITK_WEBVIEW isn't defined

Status in Oxide:
  Fix Released

Bug description:
  The ubuntu_ui test sequence is enabled unconditionally, but these
  depend on the Oxide.Ubuntu QML module which requires the
  ENABLE_UITK_WEBVIEW build flag to be defined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1647799/+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 1638912] Re: mediahub code fails to build

[Chris Coulson]

** Changed in: oxide/1.19
   Status: In Progress => Won't Fix

** Changed in: oxide/1.20
   Status: Triaged => 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/1638912

Title:
  mediahub code fails to build

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Won't Fix
Status in Oxide 1.20 series:
  Invalid

Bug description:
  FAILED: obj/oxide/shared/shared/oxide_web_media_player.o 
  /usr/bin/c++ -MMD -MF obj/oxide/shared/shared/oxide_web_media_player.o.d 
-DOXIDE_SUBPROCESS_PATH=\"oxide-qt/oxide-renderer\" 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DOXIDE_SHARED_IMPLEMENTATION 
-DENABLE_MEDIAHUB -DV8_DEPRECATION_WARNINGS -DENABLE_MDNS=1 
-DENABLE_NOTIFICATIONS -DENABLE_PDF=1 -DENABLE_SPELLCHECK=1 -DUSE_UDEV 
-DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_PANGO=1 
-DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DENABLE_WEBRTC=1 -DDISABLE_NACL -DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 
-DENABLE_THEMES=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 
-DENABLE_SESSION_SERVICE=1 -DENABLE_SUPERVISED_USERS=1 
-DENABLE_SERVICE_DISCOVERY=1 -DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD 
-DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DENABLE_HYBRIS -DENABLE_HYBRIS_CAMERA 
-DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DOXIDE_BUILD -DOXIDE_BUILD 
-DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_NOEXCEPT= 
-DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE 
-DSK_IGNORE_DW_GRAY_FIX -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS 
-DSK_SUPPORT_GPU=1 -DGOOGLE_PROTOBUF_NO_RTTI 
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DOXIDE_BUILD 
-DV8_USE_EXTERNAL_STARTUP_DATA -DOPUS_FIXED_POINT -DMESA_EGL_NO_X11_HEADERS 
-DENABLE_WEBSOCKETS -I../.. -Igen -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../../oxide -Igen/oxide 
-I../../third_party/khronos -I../../gpu -I../../third_party/libwebp 
-I../../third_party/re2/src -Igen/oxide/shared -I../../third_party/ced/src 
-I../../third_party/icu/source/common -I../../third_party/icu/source/i18n 
-I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c 
-I../../third_party/skia/include/config -I../../third_party/skia/include/core 
-I../../third_party/skia/include/effects 
-I../../third_party/skia/include/images -I../../third_party/skia/include/lazy 
-I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf 
-I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports 
-I../../third_party/skia/include/utils -I../../third_party/skia/include/gpu 
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl 
-I../../third_party/protobuf/src -Igen/protoc_out 
-I../../third_party/protobuf/src -I../../third_party/libwebm/source 
-I../../third_party/opus/src/include -Igen -I../../third_party/WebKit 
-Igen/third_party/WebKit -I../../v8/include -Igen/v8/include 
-I../../third_party/boringssl/src/include -I../../v8/include -Igen/v8/include 
-I../../third_party/mesa/src/include -I/usr/include/nss -I/usr/include/nspr 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/arm-neon 
-I../../third_party/ffmpeg -I/usr/include/dbus-1.0 
-I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -march=armv7-a -mfloat-abi=hard -mthumb -mtune=generic-armv7-a 
-mfpu=neon -Wall -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g1 -fvisibility=hidden 
-fno-threadsafe-statics -fvisibility-inlines-hidden 
-fno-delete-null-pointer-checks -std=gnu++11 -Wno-narrowing -fno-rtti 
-fno-exceptions -c ../../oxide/shared/renderer/media/oxide_web_media_player.cc 
-o obj/oxide/shared/shared/oxide_web_media_player.o
  In file included from 
../../oxide/shared/renderer/media/oxide_web_media_player.cc:5:0:
  ../../oxide/shared/renderer/media/oxide_web_media_player.h:129:77: error: 
‘SkXfermode’ has not been declared
 void paint(blink::WebCanvas*, const blink::WebRect&, unsigned char alpha, 
SkXfermode::Mode);
   
^~
  ../../oxide/shared/renderer/media/oxide_web_media_player.cc:408:6: error: 
prototype for ‘void oxide::WebMediaPlayer::paint(blink::WebCanvas*, const 

[Ubuntu-webapps-bugs] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

[Chris Coulson]

** Changed in: oxide/1.20
   Status: Fix Committed => Fix Released

** Changed in: oxide/1.19
   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/1649861

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Fix Released
Status in Oxide 1.20 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1649861/+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 1642318] Re: arm64 xenial build fails

[Chris Coulson]

** 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/1642318

Title:
  arm64 xenial build fails

Status in Oxide:
  Fix Released
Status in Oxide 1.20 series:
  Triaged
Status in gcc-5 package in Ubuntu:
  Invalid
Status in gcc-5 source package in Xenial:
  New

Bug description:
  FAILED: /usr/bin/aarch64-linux-gnu-gcc -MMD -MF 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o.d 
-DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PDF=1 
-DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DNO_TCMALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 
-DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 
-DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../.. -Igen -I../../third_party/libvpx/source/config 
-I../../third_party/libvpx/source/config/linux/arm64 
-I../../third_party/libvpx/source/libvpx -Igen/third_party/libvpx 
-I../../third_party/libvpx/source/libvpx -fno-strict-aliasing 
--param=ssp-buffer-si
 ze=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g1 
-fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function 
-Wno-sign-compare  -c 
../../third_party/libvpx/source/libvpx/vpx_dsp/arm/idct32x32_34_add_neon.c -o 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o
  {standard input}: Assembler messages:
  {standard input}: Error: unaligned opcodes detected in executable segment
  ninja: build stopped: subcommand failed.
  oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
  make[4]: *** [oxide/CMakeFiles/build_all] Error 1
  make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  CMakeFiles/Makefile2:267: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
  make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
  make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  dh_auto_build: make -j4 returned exit code 2
  debian/rules:26: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:20: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642318/+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 1655736] Re: Context menu / popup menu leaks if webview is deleted

[Chris Coulson]

It turns out my test for this wasn't quite right and that it does work,
although it's a little obscure (the menus are deleted via
WebContentsObserver::RenderFrameDeleted). I've added a test for this
here -
https://git.launchpad.net/oxide/commit/?id=8c7483e5fd4b9e32f94b3f1e1d560007d270e389

** Changed in: oxide
   Status: Triaged => 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/1655736

Title:
  Context menu / popup menu leaks if webview is deleted

Status in Oxide:
  Invalid

Bug description:
  I'm fairly sure that deleting a webview will cause an open context
  menu to be leaked. I can't see anywhere that we handle cleaning up the
  context menu in this case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1655736/+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 1656303] Re: qml-core-test sequence hangs in tst_focus.qml

[Chris Coulson]

** 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/1656303

Title:
  qml-core-test sequence hangs in tst_focus.qml

Status in Oxide:
  Fix Released

Bug description:
  tst_focus.qml always hangs for me, and it usually also spins the CPU
  and has to be killed. It seems this probably isn't a failure in
  tst_focus.qml though, as it requires tst_bug1626099.qml to precede it
  (and this test always used to run last).

  If I comment out the lines in tst_bug1626099.qml that create and test
  the second webview, then the test sequence completes successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1656303/+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 1637194] Re: Add popup menu support to UbuntuWebView

[Chris Coulson]

https://git.launchpad.net/oxide/commit/?id=4d01888eb43d188c7869301dcc18b90ca25bdf00

** 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/1637194

Title:
  Add  popup menu support to UbuntuWebView

Status in Oxide:
  Fix Released

Bug description:
  UbuntuWebView needs support for handling  popup menus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1637194/+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 1656303] [NEW] qml-core-test sequence hangs in tst_focus.qml

[Chris Coulson]

Public bug reported:

tst_focus.qml always hangs for me, and it usually also spins the CPU and
has to be killed. It seems this probably isn't a failure in
tst_focus.qml though, as it requires tst_bug1626099.qml to precede it
(and this test always used to run last).

If I comment out the lines in tst_bug1626099.qml that create and test
the second webview, then the test sequence completes successfully.

** Affects: oxide
 Importance: Critical
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
Milestone: None => branch-1.21

-- 
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/1656303

Title:
  qml-core-test sequence hangs in tst_focus.qml

Status in Oxide:
  Triaged

Bug description:
  tst_focus.qml always hangs for me, and it usually also spins the CPU
  and has to be killed. It seems this probably isn't a failure in
  tst_focus.qml though, as it requires tst_bug1626099.qml to precede it
  (and this test always used to run last).

  If I comment out the lines in tst_bug1626099.qml that create and test
  the second webview, then the test sequence completes successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1656303/+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 1655736] [NEW] Context menu leaks if webview is deleted

[Chris Coulson]

Public bug reported:

I'm fairly sure that deleting a webview will cause an open context menu
to be leaked. I can't see anywhere that we handle cleaning up the
context menu in this case.

** 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/1655736

Title:
  Context menu leaks if webview is deleted

Status in Oxide:
  Triaged

Bug description:
  I'm fairly sure that deleting a webview will cause an open context
  menu to be leaked. I can't see anywhere that we handle cleaning up the
  context menu in this case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1655736/+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 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

[Chris Coulson]

** 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/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1599771/+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 1655660] [NEW] Consider replacing com.canonical.Oxide with Oxide.Ubuntu

[Chris Coulson]

Public bug reported:

At the moment, Oxide.Ubuntu depdends on com.canonical.Oxide, and the
types it registers are prefixed with "Ubuntu" (eg, UbuntuWebView). I
wonder whether we should actually use it to replace com.canonical.Oxide
entirely, so that it registers all of the existing QML types. This would
mean we could drop the "Ubuntu" prefix from new types and just call the
new webview "WebView"

** 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/1655660

Title:
  Consider replacing com.canonical.Oxide with Oxide.Ubuntu

Status in Oxide:
  New

Bug description:
  At the moment, Oxide.Ubuntu depdends on com.canonical.Oxide, and the
  types it registers are prefixed with "Ubuntu" (eg, UbuntuWebView). I
  wonder whether we should actually use it to replace
  com.canonical.Oxide entirely, so that it registers all of the existing
  QML types. This would mean we could drop the "Ubuntu" prefix from new
  types and just call the new webview "WebView"

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1655660/+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 1655650] [NEW] Make the workaround for bug 1642318 more specific

[Chris Coulson]

Public bug reported:

The workaround for bug 1642318 disables debug symbols for libvpx on
arm64 builds, but it should:

- Disable them only for the affected compiler (gcc-5)
- Disable them only for the affected object file

** 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/1655650

Title:
  Make the workaround for bug 1642318 more specific

Status in Oxide:
  Triaged

Bug description:
  The workaround for bug 1642318 disables debug symbols for libvpx on
  arm64 builds, but it should:

  - Disable them only for the affected compiler (gcc-5)
  - Disable them only for the affected object file

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1655650/+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 1642318] Re: arm64 xenial build fails

[Chris Coulson]

Note that the problem only occurs on aarch64 with xenial's gcc (both the
host compiler and cross compiler). This source compiles fine in yakkety.

** Also affects: gcc-5 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: Ubuntu Xenial
   Importance: Undecided
   Status: New

** Changed in: ubuntu
   Status: New => 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/1642318

Title:
  arm64 xenial build fails

Status in Oxide:
  Triaged
Status in Oxide 1.20 series:
  Triaged
Status in gcc-5 package in Ubuntu:
  Invalid
Status in gcc-5 source package in Xenial:
  New

Bug description:
  FAILED: /usr/bin/aarch64-linux-gnu-gcc -MMD -MF 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o.d 
-DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PDF=1 
-DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DNO_TCMALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 
-DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 
-DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../.. -Igen -I../../third_party/libvpx/source/config 
-I../../third_party/libvpx/source/config/linux/arm64 
-I../../third_party/libvpx/source/libvpx -Igen/third_party/libvpx 
-I../../third_party/libvpx/source/libvpx -fno-strict-aliasing 
--param=ssp-buffer-si
 ze=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g1 
-fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function 
-Wno-sign-compare  -c 
../../third_party/libvpx/source/libvpx/vpx_dsp/arm/idct32x32_34_add_neon.c -o 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o
  {standard input}: Assembler messages:
  {standard input}: Error: unaligned opcodes detected in executable segment
  ninja: build stopped: subcommand failed.
  oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
  make[4]: *** [oxide/CMakeFiles/build_all] Error 1
  make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  CMakeFiles/Makefile2:267: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
  make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
  make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  dh_auto_build: make -j4 returned exit code 2
  debian/rules:26: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:20: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642318/+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 1654656] Re: Trusty PPA build fails

[Chris Coulson]

** 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/1654656

Title:
  Trusty PPA build fails

Status in Oxide:
  Fix Released

Bug description:
  The Trusty PPA build (71548c4) fails with an error like this:

  FAILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
base/debug/activity_tracker.o.d  -I/tmp/tmp7LfDjr/gen -I/<> 
-DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0 -D_FILE_OFFSET_BITS=64 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions 
-std=c++11 -Wno-c++11-narrowing -c 
/<>/base/debug/activity_tracker.cc -o base/debug/activity_tracker.o
  In file included from /<>/base/debug/activity_tracker.h:28:0,
   from /<>/base/debug/activity_tracker.cc:5:
  /<>/base/metrics/persistent_memory_allocator.h: In instantiation 
of ‘T* 
base::PersistentMemoryAllocator::GetAsObject(base::PersistentMemoryAllocator::Reference,
 uint32_t) [with T = base::debug::ThreadActivityTracker::Header; 
base::PersistentMemoryAllocator::Reference = unsigned int; uint32_t = unsigned 
int]’:
  /<>/base/debug/activity_tracker.cc:1026:44:   required from here
  /<>/base/metrics/persistent_memory_allocator.h:281:5: error: 
static assertion failed: only simple objects
   static_assert(std::is_pod::value, "only simple objects");
   ^
  cc1plus: warning: unrecognized command line option "-Wno-c++11-narrowing" 
[enabled by default]
  ninja: build stopped: subcommand failed.
  Command '['ninja', '-C', '/tmp/tmp7LfDjr', '-v', 'gn']' returned non-zero 
exit status 1
  Building gn manually in a temporary directory for bootstrapping...
  CMake Error at oxide/build/scripts/bootstrap-gn.cmake:59 (message):
Failed to bootstrap Generate Ninja binary

  
  CMake Error at oxide/build/cmake/ChromiumBuildShim.cmake:66 (message):
Failed to bootstrap Generate Ninja binary
  Call Stack (most recent call first):
oxide/build/cmake/ChromiumBuildShim.cmake:298 (_bootstrap_gn)
oxide/CMakeLists.txt:224 (run_generate_ninja)

  
  -- Configuring incomplete, errors occurred!

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654656/+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 1654656] [NEW] Trusty PPA build fails

[Chris Coulson]

Public bug reported:

The Trusty PPA build (71548c4) fails with an error like this:

FAILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
base/debug/activity_tracker.o.d  -I/tmp/tmp7LfDjr/gen -I/<> 
-DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0 -D_FILE_OFFSET_BITS=64 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions 
-std=c++11 -Wno-c++11-narrowing -c 
/<>/base/debug/activity_tracker.cc -o base/debug/activity_tracker.o
In file included from /<>/base/debug/activity_tracker.h:28:0,
 from /<>/base/debug/activity_tracker.cc:5:
/<>/base/metrics/persistent_memory_allocator.h: In instantiation 
of ‘T* 
base::PersistentMemoryAllocator::GetAsObject(base::PersistentMemoryAllocator::Reference,
 uint32_t) [with T = base::debug::ThreadActivityTracker::Header; 
base::PersistentMemoryAllocator::Reference = unsigned int; uint32_t = unsigned 
int]’:
/<>/base/debug/activity_tracker.cc:1026:44:   required from here
/<>/base/metrics/persistent_memory_allocator.h:281:5: error: 
static assertion failed: only simple objects
 static_assert(std::is_pod::value, "only simple objects");
 ^
cc1plus: warning: unrecognized command line option "-Wno-c++11-narrowing" 
[enabled by default]
ninja: build stopped: subcommand failed.
Command '['ninja', '-C', '/tmp/tmp7LfDjr', '-v', 'gn']' returned non-zero exit 
status 1
Building gn manually in a temporary directory for bootstrapping...
CMake Error at oxide/build/scripts/bootstrap-gn.cmake:59 (message):
  Failed to bootstrap Generate Ninja binary


CMake Error at oxide/build/cmake/ChromiumBuildShim.cmake:66 (message):
  Failed to bootstrap Generate Ninja binary
Call Stack (most recent call first):
  oxide/build/cmake/ChromiumBuildShim.cmake:298 (_bootstrap_gn)
  oxide/CMakeLists.txt:224 (run_generate_ninja)


-- Configuring incomplete, errors occurred!

** Affects: oxide
 Importance: Critical
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
Milestone: None => branch-1.21

-- 
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/1654656

Title:
  Trusty PPA build fails

Status in Oxide:
  Triaged

Bug description:
  The Trusty PPA build (71548c4) fails with an error like this:

  FAILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
base/debug/activity_tracker.o.d  -I/tmp/tmp7LfDjr/gen -I/<> 
-DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0 -D_FILE_OFFSET_BITS=64 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions 
-std=c++11 -Wno-c++11-narrowing -c 
/<>/base/debug/activity_tracker.cc -o base/debug/activity_tracker.o
  In file included from /<>/base/debug/activity_tracker.h:28:0,
   from /<>/base/debug/activity_tracker.cc:5:
  /<>/base/metrics/persistent_memory_allocator.h: In instantiation 
of ‘T* 
base::PersistentMemoryAllocator::GetAsObject(base::PersistentMemoryAllocator::Reference,
 uint32_t) [with T = base::debug::ThreadActivityTracker::Header; 
base::PersistentMemoryAllocator::Reference = unsigned int; uint32_t = unsigned 
int]’:
  /<>/base/debug/activity_tracker.cc:1026:44:   required from here
  /<>/base/metrics/persistent_memory_allocator.h:281:5: error: 
static assertion failed: only simple objects
   static_assert(std::is_pod::value, "only simple objects");
   ^
  cc1plus: warning: unrecognized command line option "-Wno-c++11-narrowing" 
[enabled by default]
  ninja: build stopped: subcommand failed.
  Command '['ninja', '-C', '/tmp/tmp7LfDjr', '-v', 'gn']' returned non-zero 
exit status 1
  Building gn manually in a temporary directory for bootstrapping...
  CMake Error at oxide/build/scripts/bootstrap-gn.cmake:59 (message):
Failed to bootstrap Generate Ninja binary

  
  CMake Error at oxide/build/cmake/ChromiumBuildShim.cmake:66 (message):
Failed to bootstrap Generate Ninja binary
  Call Stack (most recent call first):
oxide/build/cmake/ChromiumBuildShim.cmake:298 (_bootstrap_gn)
oxide/CMakeLists.txt:224 (run_generate_ninja)

  
  -- Configuring incomplete, errors occurred!

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654656/+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 1654655] [NEW] GN bootstrap fails in PPA builds

[Chris Coulson]

Public bug reported:

The latest uploads (71548c4) all fail like this:

Building gn manually in a temporary directory for bootstrapping...
-- Generating build files with initial Generate Ninja
ERROR at build arg file (use "gn args " to edit):12:25: Build argument 
has no effect.
fatal_linker_warnings = false
^
The variable "fatal_linker_warnings" was set as a build argument
but never appeared in a declare_args() block in any buildfile.

To view all possible args, run "gn args --list "
ERROR No targets.
I could not find any targets to write, so I'm doing nothing.
[0106/163659.319124:FATAL:err.cc(161)] Check failed: has_error_. 

CMake Error at oxide/build/scripts/bootstrap-gn.cmake:68 (message):
  Failed to run Generate Ninja


CMake Error at oxide/build/cmake/ChromiumBuildShim.cmake:66 (message):
  Failed to bootstrap Generate Ninja binary
Call Stack (most recent call first):
  oxide/build/cmake/ChromiumBuildShim.cmake:298 (_bootstrap_gn)
  oxide/CMakeLists.txt:224 (run_generate_ninja)


-- Configuring incomplete, errors occurred!

** Affects: oxide
 Importance: Critical
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
Milestone: None => branch-1.21

-- 
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/1654655

Title:
  GN bootstrap fails in PPA builds

Status in Oxide:
  Triaged

Bug description:
  The latest uploads (71548c4) all fail like this:

  Building gn manually in a temporary directory for bootstrapping...
  -- Generating build files with initial Generate Ninja
  ERROR at build arg file (use "gn args " to edit):12:25: Build 
argument has no effect.
  fatal_linker_warnings = false
  ^
  The variable "fatal_linker_warnings" was set as a build argument
  but never appeared in a declare_args() block in any buildfile.

  To view all possible args, run "gn args --list "
  ERROR No targets.
  I could not find any targets to write, so I'm doing nothing.
  [0106/163659.319124:FATAL:err.cc(161)] Check failed: has_error_. 

  CMake Error at oxide/build/scripts/bootstrap-gn.cmake:68 (message):
Failed to run Generate Ninja

  
  CMake Error at oxide/build/cmake/ChromiumBuildShim.cmake:66 (message):
Failed to bootstrap Generate Ninja binary
  Call Stack (most recent call first):
oxide/build/cmake/ChromiumBuildShim.cmake:298 (_bootstrap_gn)
oxide/CMakeLists.txt:224 (run_generate_ninja)

  
  -- Configuring incomplete, errors occurred!

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654655/+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 1654363] Re: Fails to build with vivid gcc

[Chris Coulson]

** 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/1654363

Title:
  Fails to build with vivid gcc

Status in Oxide:
  Fix Released

Bug description:
  FAILED: obj/base/base_paths/base_paths.o 
  /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF obj/base/base_paths/base_paths.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT 
-DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TC
  MALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DDISABLE_NACL -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -
  D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 
-DCOMPONENT_BUILD -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IM
  PLEMENTATION -I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -funwind-tables -fPIC -pipe -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -pthread -mfpu=neon -mthumb -Wall -Wn
  o-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g2 -fvisibility=hidden 
-fno-threadsafe-statics
   -fvisibility-inlines-hidden -fno-delete-null-pointer-checks -std=gnu++11 
-Wno-narrowing -fno-rtti -fno-exceptions -c ../../base/base_paths.cc -o 
obj/base/base_paths/base_paths.o
  In file included from ../../base/logging.h:21:0,
   from ../../base/hash.h:16,
   from ../../base/containers/hash_tables.h:13,
   from ../../base/files/file_path.h:113,
   from ../../base/base_paths.cc:7:
  ../../base/template_util.h:189:36: error: 'is_trivially_copyable' in 
namespace 'std' does not name a template type
   using is_trivially_copyable = std::is_trivially_copyable;
  ^
  [21/20728] CXX obj/base/base/allocator_extension.o

  Seems like fallout from
  
https://chromium.googlesource.com/chromium/src.git/+/7cebcfb2d80152bc84d88fc711eda6e61acda8be

  See also
  
https://chromium.googlesource.com/chromium/src.git/+/bf74cf1b649e20b4a60d2f5602db03697c8a82ef%5E%21/

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654363/+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 1654512] Re: blink_core fails to link in a component build

[Chris Coulson]

** 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/1654512

Title:
  blink_core fails to link in a component build

Status in Oxide:
  Fix Released

Bug description:
  FAILED: libblink_core.so libblink_core.so.TOC 
  python 
"/home/chr1s/src/oxide/master/src/build/toolchain/gcc_solink_wrapper.py" 
--readelf="/usr/bin/arm-linux-gnueabihf-readelf" 
--nm="/usr/bin/arm-linux-gnueabihf-nm"  --sofile="./libblink_core.so" 
--tocfile="./
  libblink_core.so.TOC" --output="./libblink_core.so"  -- 
/usr/bin/arm-linux-gnueabihf-g++ -shared -fPIC -Wl,-z,noexecstack -Wl,-z,now 
-Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=
  gold -Wl,--icf=all -pthread -Wl,-O1 -Wl,--gc-sections 
-L/usr/lib/arm-linux-gnueabihf -o "./libblink_core.so" 
-Wl,-soname="libblink_core.so" @"./libblink_core.so.rsp"
  gen/cc/ipc/mojo_compositor_frame_sink.mojom-blink.h:372: error: undefined 
reference to 
'cc::mojom::blink::MojoCompositorFrameSinkClientStubDispatch::AcceptWithResponder(cc::mojom::blink::MojoCompositorFrameSinkCl
  ient*, mojo::internal::SerializationContext*, mojo::Message*, 
mojo::MessageReceiverWithStatus*)'
  gen/cc/ipc/mojo_compositor_frame_sink.mojom-blink.h:362: error: undefined 
reference to 
'cc::mojom::blink::MojoCompositorFrameSinkClientStubDispatch::Accept(cc::mojom::blink::MojoCompositorFrameSinkClient*,
 mojo::
  internal::SerializationContext*, mojo::Message*)'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654512/+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 1654512] [NEW] blink_core fails to link in a component build

[Chris Coulson]

Public bug reported:

FAILED: libblink_core.so libblink_core.so.TOC 
python "/home/chr1s/src/oxide/master/src/build/toolchain/gcc_solink_wrapper.py" 
--readelf="/usr/bin/arm-linux-gnueabihf-readelf" 
--nm="/usr/bin/arm-linux-gnueabihf-nm"  --sofile="./libblink_core.so" 
--tocfile="./
libblink_core.so.TOC" --output="./libblink_core.so"  -- 
/usr/bin/arm-linux-gnueabihf-g++ -shared -fPIC -Wl,-z,noexecstack -Wl,-z,now 
-Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=
gold -Wl,--icf=all -pthread -Wl,-O1 -Wl,--gc-sections 
-L/usr/lib/arm-linux-gnueabihf -o "./libblink_core.so" 
-Wl,-soname="libblink_core.so" @"./libblink_core.so.rsp"
gen/cc/ipc/mojo_compositor_frame_sink.mojom-blink.h:372: error: undefined 
reference to 
'cc::mojom::blink::MojoCompositorFrameSinkClientStubDispatch::AcceptWithResponder(cc::mojom::blink::MojoCompositorFrameSinkCl
ient*, mojo::internal::SerializationContext*, mojo::Message*, 
mojo::MessageReceiverWithStatus*)'
gen/cc/ipc/mojo_compositor_frame_sink.mojom-blink.h:362: error: undefined 
reference to 
'cc::mojom::blink::MojoCompositorFrameSinkClientStubDispatch::Accept(cc::mojom::blink::MojoCompositorFrameSinkClient*,
 mojo::
internal::SerializationContext*, mojo::Message*)'
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
collect2: error: ld returned 1 exit status

** Affects: oxide
 Importance: High
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
Milestone: None => branch-1.21

** 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/1654512

Title:
  blink_core fails to link in a component build

Status in Oxide:
  Triaged

Bug description:
  FAILED: libblink_core.so libblink_core.so.TOC 
  python 
"/home/chr1s/src/oxide/master/src/build/toolchain/gcc_solink_wrapper.py" 
--readelf="/usr/bin/arm-linux-gnueabihf-readelf" 
--nm="/usr/bin/arm-linux-gnueabihf-nm"  --sofile="./libblink_core.so" 
--tocfile="./
  libblink_core.so.TOC" --output="./libblink_core.so"  -- 
/usr/bin/arm-linux-gnueabihf-g++ -shared -fPIC -Wl,-z,noexecstack -Wl,-z,now 
-Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=
  gold -Wl,--icf=all -pthread -Wl,-O1 -Wl,--gc-sections 
-L/usr/lib/arm-linux-gnueabihf -o "./libblink_core.so" 
-Wl,-soname="libblink_core.so" @"./libblink_core.so.rsp"
  gen/cc/ipc/mojo_compositor_frame_sink.mojom-blink.h:372: error: undefined 
reference to 
'cc::mojom::blink::MojoCompositorFrameSinkClientStubDispatch::AcceptWithResponder(cc::mojom::blink::MojoCompositorFrameSinkCl
  ient*, mojo::internal::SerializationContext*, mojo::Message*, 
mojo::MessageReceiverWithStatus*)'
  gen/cc/ipc/mojo_compositor_frame_sink.mojom-blink.h:362: error: undefined 
reference to 
'cc::mojom::blink::MojoCompositorFrameSinkClientStubDispatch::Accept(cc::mojom::blink::MojoCompositorFrameSinkClient*,
 mojo::
  internal::SerializationContext*, mojo::Message*)'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  
../../third_party/WebKit/Source/platform/graphics/OffscreenCanvasFrameDispatcherImpl.h:33:
 error: undefined reference to 'cc::SurfaceIdAllocator::~SurfaceIdAllocator()'
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654512/+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 1654363] [NEW] Fails to build with vivid gcc

[Chris Coulson]

Public bug reported:

FAILED: obj/base/base_paths/base_paths.o 
/usr/bin/arm-linux-gnueabihf-g++ -MMD -MF obj/base/base_paths/base_paths.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT 
-DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TC
MALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DDISABLE_NACL -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -
D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 
-DCOMPONENT_BUILD -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IM
PLEMENTATION -I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -funwind-tables -fPIC -pipe -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -pthread -mfpu=neon -mthumb -Wall -Wn
o-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g2 -fvisibility=hidden 
-fno-threadsafe-statics
 -fvisibility-inlines-hidden -fno-delete-null-pointer-checks -std=gnu++11 
-Wno-narrowing -fno-rtti -fno-exceptions -c ../../base/base_paths.cc -o 
obj/base/base_paths/base_paths.o
In file included from ../../base/logging.h:21:0,
 from ../../base/hash.h:16,
 from ../../base/containers/hash_tables.h:13,
 from ../../base/files/file_path.h:113,
 from ../../base/base_paths.cc:7:
../../base/template_util.h:189:36: error: 'is_trivially_copyable' in namespace 
'std' does not name a template type
 using is_trivially_copyable = std::is_trivially_copyable;
^
[21/20728] CXX obj/base/base/allocator_extension.o

Seems like fallout from
https://chromium.googlesource.com/chromium/src.git/+/7cebcfb2d80152bc84d88fc711eda6e61acda8be

See also
https://chromium.googlesource.com/chromium/src.git/+/bf74cf1b649e20b4a60d2f5602db03697c8a82ef%5E%21/

** Affects: oxide
 Importance: Critical
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
Milestone: None => branch-1.21

-- 
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/1654363

Title:
  Fails to build with vivid gcc

Status in Oxide:
  Triaged

Bug description:
  FAILED: obj/base/base_paths/base_paths.o 
  /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF obj/base/base_paths/base_paths.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT 
-DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TC
  MALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DDISABLE_NACL -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -
  D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 
-DCOMPONENT_BUILD -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IM
  PLEMENTATION -I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -funwind-tables -fPIC -pipe -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -pthread -mfpu=neon -mthumb -Wall -Wn
  o-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g2 -fvisibility=hidden 
-fno-threadsafe-statics
   -fvisibility-inlines-hidden -fno-delete-null-pointer-checks -std=gnu++11 
-Wno-narrowing -fno-rtti -fno-exceptions -c ../../base/base_paths.cc -o 
obj/base/base_paths/base_paths.o
  In file included from ../../base/logging.h:21:0,
   from ../../base/hash.h:16,
   from ../../base/containers/hash_tables.h:13,
   from ../../base/files/file_path.h:113,
   from ../../base/base_paths.cc:7:
  ../../base/template_util.h:189:36: error: 'is_trivially_copyable' in 
namespace 'std' does not name a template type
   using is_trivially_copyable = std::is_trivially_copyable;
  ^
  [21/20728] CXX obj/base/base/allocator_extension.o

  Seems like fallout from
  
https://chromium.googlesource.com/chromium/src.git/+/7cebcfb2d80152bc84d88fc711eda6e61acda8be

  See also
  
https://chromium.googlesource.com/chromium/src.git/+/bf74cf1b649e20b4a60d2f5602db03697c8a82ef%5E%21/

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1654363/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-

[Ubuntu-webapps-bugs] [Bug 1647895] Re: Tablet suspends while playing video or audio in browser

[Chris Coulson]

** Changed in: oxide/1.19
   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/1647895

Title:
  Tablet suspends while playing video or audio in browser

Status in Canonical System Image:
  New
Status in Oxide:
  Fix Released
Status in Oxide 1.18 series:
  Fix Committed
Status in Oxide 1.19 series:
  Fix Released

Bug description:
  In frieza build 246 (20161206) the tablet will suspend while video or
  audio is playing in the browser. This did not happen in releases a few
  days ago.

  Steps to reproduce
  1) Set lock when idle to 1 minute
  2) Play a youtube video
  3) Tablet suspends after 1 minute, stopping the playback.

  Expected result
  The idle timer should not start until playback has finish

  Also see Bug #1602739

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647895/+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 1649577] Re: Fix for bug 1599771 breaks popup menus

[Chris Coulson]

** Changed in: oxide/1.19
   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/1649577

Title:
  Fix for bug 1599771 breaks popup menus

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Fix Released

Bug description:
  Whilst trying to bring  popup menu support in to
  UbuntuWebView, I've been struggling to get them working. It turns out
  that popup menus are also broken in webbrowser-app with Oxide 1.19.

  What's happening is:

  1) The popup menu opens and receives focus.
  2) Blink immediately requests that the popup menu closes because the webview 
sends a blur event.

  This is a regression from bug 1599771. It sucks that we didn't find
  this sooner (when the UI lives in Oxide, this sort of thing will be
  easily testable with automated tests in Oxide).

  I wonder whether we should revert the fix for bug 1599771 on the 1.19
  branch and come up with a different fix for that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1649577/+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 1638912] Re: mediahub code fails to build

[Chris Coulson]

** Also affects: oxide/1.20
   Importance: Undecided
   Status: New

** Changed in: oxide/1.20
   Importance: Undecided => Critical

** Changed in: oxide/1.20
   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/1638912

Title:
  mediahub code fails to build

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  In Progress
Status in Oxide 1.20 series:
  Triaged

Bug description:
  FAILED: obj/oxide/shared/shared/oxide_web_media_player.o 
  /usr/bin/c++ -MMD -MF obj/oxide/shared/shared/oxide_web_media_player.o.d 
-DOXIDE_SUBPROCESS_PATH=\"oxide-qt/oxide-renderer\" 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DOXIDE_SHARED_IMPLEMENTATION 
-DENABLE_MEDIAHUB -DV8_DEPRECATION_WARNINGS -DENABLE_MDNS=1 
-DENABLE_NOTIFICATIONS -DENABLE_PDF=1 -DENABLE_SPELLCHECK=1 -DUSE_UDEV 
-DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_PANGO=1 
-DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DENABLE_WEBRTC=1 -DDISABLE_NACL -DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 
-DENABLE_THEMES=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 
-DENABLE_SESSION_SERVICE=1 -DENABLE_SUPERVISED_USERS=1 
-DENABLE_SERVICE_DISCOVERY=1 -DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD 
-DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DENABLE_HYBRIS -DENABLE_HYBRIS_CAMERA 
-DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DOXIDE_BUILD -DOXIDE_BUILD 
-DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_NOEXCEPT= 
-DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE 
-DSK_IGNORE_DW_GRAY_FIX -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS 
-DSK_SUPPORT_GPU=1 -DGOOGLE_PROTOBUF_NO_RTTI 
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DOXIDE_BUILD 
-DV8_USE_EXTERNAL_STARTUP_DATA -DOPUS_FIXED_POINT -DMESA_EGL_NO_X11_HEADERS 
-DENABLE_WEBSOCKETS -I../.. -Igen -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../../oxide -Igen/oxide 
-I../../third_party/khronos -I../../gpu -I../../third_party/libwebp 
-I../../third_party/re2/src -Igen/oxide/shared -I../../third_party/ced/src 
-I../../third_party/icu/source/common -I../../third_party/icu/source/i18n 
-I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c 
-I../../third_party/skia/include/config -I../../third_party/skia/include/core 
-I../../third_party/skia/include/effects 
-I../../third_party/skia/include/images -I../../third_party/skia/include/lazy 
-I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf 
-I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports 
-I../../third_party/skia/include/utils -I../../third_party/skia/include/gpu 
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl 
-I../../third_party/protobuf/src -Igen/protoc_out 
-I../../third_party/protobuf/src -I../../third_party/libwebm/source 
-I../../third_party/opus/src/include -Igen -I../../third_party/WebKit 
-Igen/third_party/WebKit -I../../v8/include -Igen/v8/include 
-I../../third_party/boringssl/src/include -I../../v8/include -Igen/v8/include 
-I../../third_party/mesa/src/include -I/usr/include/nss -I/usr/include/nspr 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/arm-neon 
-I../../third_party/ffmpeg -I/usr/include/dbus-1.0 
-I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -march=armv7-a -mfloat-abi=hard -mthumb -mtune=generic-armv7-a 
-mfpu=neon -Wall -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g1 -fvisibility=hidden 
-fno-threadsafe-statics -fvisibility-inlines-hidden 
-fno-delete-null-pointer-checks -std=gnu++11 -Wno-narrowing -fno-rtti 
-fno-exceptions -c ../../oxide/shared/renderer/media/oxide_web_media_player.cc 
-o obj/oxide/shared/shared/oxide_web_media_player.o
  In file included from 
../../oxide/shared/renderer/media/oxide_web_media_player.cc:5:0:
  ../../oxide/shared/renderer/media/oxide_web_media_player.h:129:77: error: 
‘SkXfermode’ has not been declared
 void paint(blink::WebCanvas*, const blink::WebRect&, unsigned char alpha, 
SkXfermode::Mode);
   
^~
  ../../oxide/shared/renderer/media/oxide_web_media_player.cc:408:6: error: 

[Ubuntu-webapps-bugs] [Bug 1611146] Re: Location bar height won't be rescaled on display change

[Chris Coulson]

** Changed in: oxide/1.18
   Status: Triaged => Won't Fix

** Changed in: oxide/1.19
   Status: Triaged => Won't Fix

** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

-- 
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/1611146

Title:
  Location bar height won't be rescaled on display change

Status in Oxide:
  Triaged
Status in Oxide 1.18 series:
  Won't Fix
Status in Oxide 1.19 series:
  Won't Fix

Bug description:
  
https://git.launchpad.net/oxide/diff/qt/core/browser/oxide_qt_web_view.cc?id=a32c044a2d75e4d14b1d01f271a3dc066a35a448
  changes how the location bar height is rescaled when the device scale
  changes. Previously, it would be rescaled if the scale of the display
  changed or if a view moved between displays. Now it will only rescale
  if the scale of the display changes, meaning there is a clear chance
  of a regression here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1611146/+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 1642318] Re: arm64 xenial build fails

[Chris Coulson]

** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

** Also affects: oxide/1.20
   Importance: Undecided
   Status: New

** Changed in: oxide/1.20
   Importance: Undecided => Critical

** Changed in: oxide/1.20
   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/1642318

Title:
  arm64 xenial build fails

Status in Oxide:
  Triaged
Status in Oxide 1.20 series:
  Triaged

Bug description:
  FAILED: /usr/bin/aarch64-linux-gnu-gcc -MMD -MF 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o.d 
-DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PDF=1 
-DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DNO_TCMALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 
-DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 
-DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../.. -Igen -I../../third_party/libvpx/source/config 
-I../../third_party/libvpx/source/config/linux/arm64 
-I../../third_party/libvpx/source/libvpx -Igen/third_party/libvpx 
-I../../third_party/libvpx/source/libvpx -fno-strict-aliasing 
--param=ssp-buffer-si
 ze=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g1 
-fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function 
-Wno-sign-compare  -c 
../../third_party/libvpx/source/libvpx/vpx_dsp/arm/idct32x32_34_add_neon.c -o 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o
  {standard input}: Assembler messages:
  {standard input}: Error: unaligned opcodes detected in executable segment
  ninja: build stopped: subcommand failed.
  oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
  make[4]: *** [oxide/CMakeFiles/build_all] Error 1
  make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  CMakeFiles/Makefile2:267: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
  make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
  make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  dh_auto_build: make -j4 returned exit code 2
  debian/rules:26: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:20: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642318/+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 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

[Chris Coulson]

** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

** Also affects: oxide/1.20
   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/1649861

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  Confirmed
Status in Oxide 1.19 series:
  Confirmed
Status in Oxide 1.20 series:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1649861/+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 1640264] Re: find in page doesn’t wrap correctly

[Chris Coulson]

** Changed in: oxide/1.19
   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/1640264

Title:
  find in page doesn’t wrap correctly

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Fix Released

Bug description:
  I’m testing webbrowser-app with a local build of oxide master, and I’m seeing 
a regression in the find-in-page functionality.
   1) If I browse to e.g. http://start.ubuntu.com, activate find-in-page and 
search for "ubuntu", I get 3 results, and the first one is highlighted 
(counter: "1/3")
   2) If I press the next match button, the second match is highlighted 
(counter: "2/3")
   3) If I press again the next match button, the third match is highlighted 
(counter: "3/3")
   4) If I press again the next match button, I expect the navigation to wrap, 
and the first match to be highlighted, but instead no match is highlighted, and 
the counter remains at "3/3"
   5) If I press again the next match button, the first match is highlighted, 
and the counter updated to "1/3".

  It looks like find-in-page behaves as if there was a fourth phantom
  match that doesn’t update the counter (at step 4).

  I’m not observing this with oxide 1.18.3, so this seems to be a recent
  regression in oxide master.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1640264/+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 1648572] [NEW] Add UbuntuWebContextMenu.removeStockAction

[Chris Coulson]

Public bug reported:

One of the use cases for the API for customizing context menu actions is
removing stock actions in some cases. The current API provides
indexOfStockAction and removeItemAt, but it would probably be useful to
have a removeStockAction() method that just takes an Action enum.

** 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/1648572

Title:
  Add UbuntuWebContextMenu.removeStockAction

Status in Oxide:
  Triaged

Bug description:
  One of the use cases for the API for customizing context menu actions
  is removing stock actions in some cases. The current API provides
  indexOfStockAction and removeItemAt, but it would probably be useful
  to have a removeStockAction() method that just takes an Action enum.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1648572/+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 1640634] Re: Update WebView::OpenURLFromTab for context menu interaction

[Chris Coulson]

https://git.launchpad.net/oxide/commit/?id=293d3ab3cccf68aae0acc04dfb7a95a498be888a

** 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/1640634

Title:
  Update WebView::OpenURLFromTab for context menu interaction

Status in Oxide:
  Fix Released

Bug description:
  The UbuntuWebView context menu "Open  in new tab/window" actions
  will go through this function, but it has a couple of issues:

  - It DCHECK's that OpenURLParams::is_renderer_initiated is true.

  - It shouldn't call WebContentsClient::ShouldCreateNewWebContents()
  for context menu initiated calls. We don't want the application to
  block these (it should create a new tab / window unconditionally)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1640634/+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 1637190] Re: Add support for customising the context menu in UbuntuWebView

[Chris Coulson]

https://git.launchpad.net/oxide/commit/?id=3d1bfbbf47817a939f87fc9ac50ca0e6187f24ae

** 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/1637190

Title:
  Add support for customising the context menu in UbuntuWebView

Status in Oxide:
  Fix Released

Bug description:
  With UbuntuWebView responsible for handling context menus, we need an
  additional API to allow applications to add custom entries to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1637190/+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 1639185] Re: oxide 1.18.3 crashes when running webbrowser-app tests

[Chris Coulson]

** Changed in: oxide/1.18
   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/1639185

Title:
  oxide 1.18.3 crashes when running webbrowser-app tests

Status in Oxide:
  Invalid
Status in Oxide 1.18 series:
  Fix Released

Bug description:
  After upgrading oxide-qt from 1.17.9 to 1.18.3 I’ve started observing
  consistent crashes when running both autopilot and unit tests for
  webbrowser-app.

  Steps to reproduce, on a system running xenial+overlay:
$ bzr branch lp:webbrowser-app
$ cd webbrowser-app
$ cmake . && make
$ ./tests/unittests/qml/tst_QmlTests -input 
tests/unittests/qml/tst_UbuntuWebView02.qml -import src

  
  Here is a stacktrace I get:

  #0  0x76ffa84a in QV4::Value::as (this=0x7fffd8965e40) 
at jsruntime/qv4managed_p.h:192
  #1  QV4::RuntimeHelpers::toPrimitive (typeHint=0, value=...) at 
jsruntime/qv4runtime_p.h:266
  #2  QV4::RuntimeHelpers::addHelper (engine=0x7dd970, left=..., right=...) at 
jsruntime/qv4runtime.cpp:516
  #3  0x7fffe001f964 in ?? ()
  #4  0x7fffc82101c8 in ?? ()
  #5  0x77082c45 in QQmlPropertyCapture::registerQmlDependencies 
(engine=0x7dd970, compiledFunction=) at 
qml/qqmljavascriptexpression.cpp:328
  #6  0x76fa0b3b in QV4::SimpleScriptFunction::call (that=, callData=0x7fffd8965d08) at jsruntime/qv4functionobject.cpp:577
  #7  0x770817d4 in QV4::Object::call (d=0x7fffd8965dc8, 
this=0x7fffe800de58)
  at 
../../include/QtQml/5.6.1/QtQml/private/../../../../../src/qml/jsruntime/qv4object_p.h:324
  #8  QQmlJavaScriptExpression::evaluate (this=this@entry=0x1f283c0, 
callData=callData@entry=0x7fffd8965dc8, 
isUndefined=isUndefined@entry=0x7fff2a2c)
  at qml/qqmljavascriptexpression.cpp:189
  #9  0x77081c71 in QQmlJavaScriptExpression::evaluate 
(this=this@entry=0x1f283c0, isUndefined=isUndefined@entry=0x7fff2a2c)
  at qml/qqmljavascriptexpression.cpp:149
  #10 0x7708952e in QQmlBinding::update (this=0x1f283c0, flags=...) at 
qml/qqmlbinding.cpp:187
  #11 0x77089a3e in QQmlBinding::refresh (this=) at 
qml/qqmlbinding.cpp:403
  #12 0x77060b7e in QQmlNotifier::emitNotify (endpoint=, 
a=a@entry=0x0) at qml/qqmlnotifier.cpp:94
  #13 0x7700c55c in QQmlData::signalEmitted (object=0x1f27e70, 
index=52, a=0x0) at qml/qqmlengine.cpp:773
  #14 0x76a3d2c0 in QMetaObject::activate (sender=0x1f27e70, 
signalOffset=, local_signal_index=, 
argv=argv@entry=0x0)
  at kernel/qobject.cpp:3616
  #15 0x77006d25 in QQmlVMEMetaObject::activate 
(this=this@entry=0x1f28150, object=, index=, 
args=args@entry=0x0)
  at qml/qqmlvmemetaobject.cpp:1196
  #16 0x77008229 in QQmlVMEMetaObject::metaCall (this=0x1f28150, 
o=, c=, _id=, a=)
  at qml/qqmlvmemetaobject.cpp:748
  #17 0x7708f631 in QV4::QQmlValueTypeWrapper::write 
(this=this@entry=0x7fffd8965db8, target=0x1f27e70, propertyIndex=64) at 
qml/qqmlvaluetypewrapper.cpp:299
  #18 0x770888ac in QQmlBinding::write (this=this@entry=0x1f28580, 
core=..., result=..., isUndefined=, flags=...) at 
qml/qqmlbinding.cpp:259
  #19 0x770895ea in QQmlBinding::update (this=0x1f28580, flags=...) at 
qml/qqmlbinding.cpp:191
  #20 0x77089a3e in QQmlBinding::refresh (this=) at 
qml/qqmlbinding.cpp:403
  #21 0x77060b7e in QQmlNotifier::emitNotify (endpoint=, 
a=a@entry=0x0) at qml/qqmlnotifier.cpp:94
  #22 0x7700c55c in QQmlData::signalEmitted (object=0xacbf40, index=5, 
a=0x0) at qml/qqmlengine.cpp:773
  #23 0x76a3d2c0 in QMetaObject::activate (sender=0xacbf40, 
signalOffset=, local_signal_index=, argv=0x0) at 
kernel/qobject.cpp:3616
  #24 0x7fffd8126af5 in 
OxideQQuickTouchSelectionController::boundsChanged() () from 
/usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0
  #25 0x7fffd8100384 in 
OxideQQuickTouchSelectionController::onTouchSelectionChanged(OxideQQuickTouchSelectionController::Status,
 QRectF const&, bool, bool) ()
     from /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0
  #26 0x7fffd811b373 in 
oxide::qquick::ContentsView::TouchSelectionChanged(oxide::qt::TouchSelectionControllerActiveStatus,
 QRectF const&, bool, bool) ()
     from /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0
  #27 0x7fffbeb40a1a in oxide::qt::ContentsView::TouchSelectionChanged () 
at ../../oxide/qt/core/browser/oxide_qt_contents_view.cc:563
  #28 0x7fffc0f45696 in oxide::WebContentsView::TouchSelectionChanged () at 
../../oxide/shared/browser/oxide_web_contents_view.cc:717
  #29 0x7fffc0f50777 in oxide::WebView::CommonInit () at 
../../oxide/shared/browser/oxide_web_view.cc:235
  #30 0x7fffc0f5098c in oxide::WebView::WebView () at 
../../oxide/shared/browser/oxide_web_view.cc:1012
  #31 0x7fffbeb5f47b in oxide::qt::WebView::WebView () at 
../../oxide/qt/core/browser/oxide_qt_web_view.cc:1162
  

[Ubuntu-webapps-bugs] [Bug 1637187] Re: Add support for testing Ubuntu UITK components in UbuntuWebView

[Chris Coulson]

** 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/1637187

Title:
  Add support for testing Ubuntu UITK components in UbuntuWebView

Status in Oxide:
  Fix Released

Bug description:
  We need support for testing the auxilliary UI components in
  UbuntuWebView. I guess this will use autopilot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1637187/+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 1645909] [NEW] Loading media in to a webview produces a weird set of load events

[Chris Coulson]

Public bug reported:

Whilst writing a test for the context menu that opens media in a
background tab, I noticed that even though the media loads successfully,
the load event sequence ends with a Stopped event rather than a
Succeeded event.

** 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/1645909

Title:
  Loading media in to a webview produces a weird set of load events

Status in Oxide:
  New

Bug description:
  Whilst writing a test for the context menu that opens media in a
  background tab, I noticed that even though the media loads
  successfully, the load event sequence ends with a Stopped event rather
  than a Succeeded event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1645909/+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 1640542] Re: oops error when navigating a website from facebook or twitter

[Chris Coulson]

** Changed in: oxide/1.19
   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/1640542

Title:
  oops error when navigating a website from facebook or twitter

Status in Canonical System Image:
  New
Status in Oxide:
  Fix Released
Status in Oxide 1.18 series:
  Fix Committed
Status in Oxide 1.19 series:
  Fix Released

Bug description:
  /*\ only with silo 2148 installed

  Environment: 
  current build number: 227
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-11-09 16:48:22
  version version: 227
  version ubuntu: 20161109
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions: have a fb or twitter account registered

  Steps to reproduce:

  1º Open Facebook or twitter
  2º Scroll down until you see a post/link to another website(an article or so)
  3º Navigate through the main sections of the website and return to home page

  Current result: "oops, something went wrong" message appears randomly
  when navigating through the site

  Expected result: no error should appear when trying to load pages

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640542/+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 1637609] Re: OxideQQuickNavigationHistory shouldn't have a public constructor

[Chris Coulson]

** Changed in: oxide/1.19
   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/1637609

Title:
  OxideQQuickNavigationHistory shouldn't have a public constructor

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Fix Released

Bug description:
  The constructor of OxideQQuickNavigationHistory is public, and it
  shouldn't be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1637609/+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 1638915] Re: Fails to build on trusty

[Chris Coulson]

** Changed in: oxide/1.19
   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/1638915

Title:
  Fails to build on trusty

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Fix Released

Bug description:
  make[3]: Entering directory `/<>/obj-x86_64-linux-gnu'
  /usr/bin/cmake -E cmake_progress_report 
/<>/obj-x86_64-linux-gnu/CMakeFiles 80
  [ 86%] Building CXX object 
oxide/qt/qmlplugin/CMakeFiles/qmloxideplugin.dir/oxide_qml_plugin.cc.o
  cd /<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin && 
/usr/bin/x86_64-linux-gnu-g++   -DLEGACY_QMLVALUE_TYPES -DOS_LINUX 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -Dqmloxideplugin_EXPORTS -std=c++11 
-fPIC -I/<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin 
-I/<>/oxide/qt/qmlplugin -I/<>/oxide 
-I/usr/include/qt5/QtCore/5.2.1 -I/usr/include/qt5/QtCore/5.2.1/QtCore 
-I/usr/include/qt5/QtQml/5.2.1 -I/usr/include/qt5/QtQml/5.2.1/QtQml 
-I/usr/include/qt5/QtNetwork/5.2.1 -I/usr/include/qt5/QtNetwork/5.2.1/QtNetwork 
-I/usr/include/qt5 -I/usr/include/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I/usr/include/qt5/QtQml 
-I/usr/include/qt5/QtNetwork -I/usr/include/qt5/QtQuick 
-I/usr/include/qt5/QtGui -I/<>/oxide/qt/core/api/includes 
-I/<>/oxide/qt/quick/api/includes-fno-rtti -o 
CMakeFiles/qmloxideplugin.dir/oxide_qml_plugin.c
 c.o -c /<>/oxide/qt/qmlplugin/oxide_qml_plugin.cc
  /usr/bin/cmake -E cmake_progress_report 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
  [ 86%] Building CXX object 
oxide/qt/qmlplugin/CMakeFiles/qmloxideplugin.dir/oxide_qml_download_request.cc.o
  cd /<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin && 
/usr/bin/x86_64-linux-gnu-g++   -DLEGACY_QMLVALUE_TYPES -DOS_LINUX 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -Dqmloxideplugin_EXPORTS -std=c++11 
-fPIC -I/<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin 
-I/<>/oxide/qt/qmlplugin -I/<>/oxide 
-I/usr/include/qt5/QtCore/5.2.1 -I/usr/include/qt5/QtCore/5.2.1/QtCore 
-I/usr/include/qt5/QtQml/5.2.1 -I/usr/include/qt5/QtQml/5.2.1/QtQml 
-I/usr/include/qt5/QtNetwork/5.2.1 -I/usr/include/qt5/QtNetwork/5.2.1/QtNetwork 
-I/usr/include/qt5 -I/usr/include/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I/usr/include/qt5/QtQml 
-I/usr/include/qt5/QtNetwork -I/usr/include/qt5/QtQuick 
-I/usr/include/qt5/QtGui -I/<>/oxide/qt/core/api/includes 
-I/<>/oxide/qt/quick/api/includes-fno-rtti -o 
CMakeFiles/qmloxideplugin.dir/oxide_qml_download
 _request.cc.o -c 
/<>/oxide/qt/qmlplugin/oxide_qml_download_request.cc
  Linking CXX executable tst_oxideqquicknavigationitem
  cd 
/<>/obj-x86_64-linux-gnu/oxide/qt/tests/unit/oxideqquicknavigationitem
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/tst_oxideqquicknavigationitem.dir/link.txt --verbose=1
  /usr/bin/x86_64-linux-gnu-g++-std=c++11-fuse-ld=gold 
CMakeFiles/tst_oxideqquicknavigationitem.dir/tst_oxideqquicknavigationitem.cc.o 
CMakeFiles/tst_oxideqquicknavigationitem.dir/tst_oxideqquicknavigationitem_automoc.cpp.o
  -o tst_oxideqquicknavigationitem -rdynamic 
../../../../../chromium/libOxideQtCore.so.0 
../../../../../out/lib/libOxideQtQuick.so.0 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Test.so.5.2.1 
../../../../../chromium/libOxideQtCore.so.0 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.2.1 
  ../../../../../out/lib/libOxideQtQuick.so.0: error: undefined reference to 
'glGenTextures'
  ../../../../../out/lib/libOxideQtQuick.so.0: error: undefined reference to 
'glBindTexture'
  ../../../../../out/lib/libOxideQtQuick.so.0: error: undefined reference to 
'glDeleteTextures'
  collect2: error: ld returned 1 exit status
  make[3]: *** 
[oxide/qt/tests/unit/oxideqquicknavigationitem/tst_oxideqquicknavigationitem] 
Error 1
  make[3]: Leaving directory `/<>/obj-x86_64-linux-gnu'
  make[2]: *** 
[oxide/qt/tests/unit/oxideqquicknavigationitem/CMakeFiles/tst_oxideqquicknavigationitem.dir/all]
 Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1638915/+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 1644460] [NEW] Fails to build because of media-hub, again

[Chris Coulson]

Public bug reported:

AILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
obj/oxide/shared/shared/oxide_content_renderer_client.o.d 
-DOXIDE_SUBPROCESS_PATH=\"oxide-qt/oxide-renderer\" 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DOXIDE_SHARED_IMPLEMENTATION 
-DENABLE_MEDIAHUB -DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS 
-DENABLE_PDF=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC 
-DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DUSE_PROPRIETARY_CODECS 
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL 
-DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DENABLE_HYBRIS 
-DENABLE_HYBRIS_CAMERA -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DOXIDE_BUILD 
-DOXIDE_BUILD -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 
-DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE 
-DSK_IGNORE_DW_GRAY_FIX -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS 
-DSK_SUPPORT_GPU=1 -DGOOGLE_PROTOBUF_NO_RTTI 
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DOXIDE_BUILD 
-DV8_USE_EXTERNAL_STARTUP_DATA -DOPUS_FIXED_POINT -DMESA_EGL_NO_X11_HEADERS 
-I../.. -Igen -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../../oxide -Igen/oxide 
-I../../third_party/khronos -I../../gpu -I../../third_party/libwebp 
-I../../third_party/re2/src -Igen/oxide/shared -I../../third_party/ced/src 
-I../../third_party/icu/source/common -I../../third_party/icu/source/i18n 
-I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c 
-I../../third_party/skia/include/config -I../../third_party/skia/include/core 
-I../../third_party/skia/include/effects 
-I../../third_party/skia/include/images -I../../third_party/skia/include/lazy 
-I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf 
-I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports 
-I../../third_party/skia/include/utils -I../../third_party/skia/include/gpu 
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl 
-I../../third_party/protobuf/src -Igen/protoc_out 
-I../../third_party/protobuf/src -I../../third_party/libwebm/source 
-I../../third_party/opus/src/include -I../../third_party/boringssl/src/include 
-I/usr/include/nss -I/usr/include/nspr -Igen -I../../third_party/WebKit 
-Igen/third_party/WebKit -I../../v8/include -Igen/v8/include -I../../v8/include 
-Igen/v8/include -I../../third_party/mesa/src/include 
-I../../third_party/ffmpeg/chromium/config/Chrome/linux/arm-neon 
-I../../third_party/ffmpeg -I/usr/include/dbus-1.0 
-I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -mfpu=neon 
-mthumb -Wall -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -g1 -fvisibility=hidden 
-fno-threadsafe-statics -fvisibility-inlines-hidden 
-fno-delete-null-pointer-checks -std=gnu++11 -Wno-narrowing -fno-rtti 
-fno-exceptions -c ../../oxide/shared/renderer/oxide_content_renderer_client.cc 
-o obj/oxide/shared/shared/oxide_content_renderer_client.o
In file included from 
../../oxide/shared/renderer/oxide_content_renderer_client.cc:53:0:
../../oxide/shared/renderer/media/oxide_web_media_player.h:170:8: error: 
conflicting return type specified for ‘virtual void 
oxide::WebMediaPlayer::OnSuspendRequested(bool)’
   void OnSuspendRequested(bool must_suspend) override;
^
In file included from 
../../oxide/shared/renderer/media/oxide_web_media_player.h:21:0,
 from 
../../oxide/shared/renderer/oxide_content_renderer_client.cc:53:
../../media/blink/webmediaplayer_delegate.h:37:18: error:   overriding ‘virtual 
bool media::WebMediaPlayerDelegate::Observer::OnSuspendRequested(bool)’
 virtual bool OnSuspendRequested(bool must_suspend) = 0;
  ^
ninja: build stopped: subcommand failed.

** 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/1644460

Title:
  Fails to build because of media-hub, again

Status in Oxide:
  New

Bug description:
  AILED: /usr/bin/arm-linux-gnueabihf-g++ -MMD -MF 
obj/oxide/shared/shared/oxide_content_renderer_client.o.d 

[Ubuntu-webapps-bugs] [Bug 1637609] Re: OxideQQuickNavigationHistory shouldn't have a public constructor

[Chris Coulson]

** 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/1637609

Title:
  OxideQQuickNavigationHistory shouldn't have a public constructor

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Triaged

Bug description:
  The constructor of OxideQQuickNavigationHistory is public, and it
  shouldn't be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1637609/+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 1638915] Re: Fails to build on trusty

[Chris Coulson]

** 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/1638915

Title:
  Fails to build on trusty

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Triaged

Bug description:
  make[3]: Entering directory `/<>/obj-x86_64-linux-gnu'
  /usr/bin/cmake -E cmake_progress_report 
/<>/obj-x86_64-linux-gnu/CMakeFiles 80
  [ 86%] Building CXX object 
oxide/qt/qmlplugin/CMakeFiles/qmloxideplugin.dir/oxide_qml_plugin.cc.o
  cd /<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin && 
/usr/bin/x86_64-linux-gnu-g++   -DLEGACY_QMLVALUE_TYPES -DOS_LINUX 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -Dqmloxideplugin_EXPORTS -std=c++11 
-fPIC -I/<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin 
-I/<>/oxide/qt/qmlplugin -I/<>/oxide 
-I/usr/include/qt5/QtCore/5.2.1 -I/usr/include/qt5/QtCore/5.2.1/QtCore 
-I/usr/include/qt5/QtQml/5.2.1 -I/usr/include/qt5/QtQml/5.2.1/QtQml 
-I/usr/include/qt5/QtNetwork/5.2.1 -I/usr/include/qt5/QtNetwork/5.2.1/QtNetwork 
-I/usr/include/qt5 -I/usr/include/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I/usr/include/qt5/QtQml 
-I/usr/include/qt5/QtNetwork -I/usr/include/qt5/QtQuick 
-I/usr/include/qt5/QtGui -I/<>/oxide/qt/core/api/includes 
-I/<>/oxide/qt/quick/api/includes-fno-rtti -o 
CMakeFiles/qmloxideplugin.dir/oxide_qml_plugin.c
 c.o -c /<>/oxide/qt/qmlplugin/oxide_qml_plugin.cc
  /usr/bin/cmake -E cmake_progress_report 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
  [ 86%] Building CXX object 
oxide/qt/qmlplugin/CMakeFiles/qmloxideplugin.dir/oxide_qml_download_request.cc.o
  cd /<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin && 
/usr/bin/x86_64-linux-gnu-g++   -DLEGACY_QMLVALUE_TYPES -DOS_LINUX 
-DOXIDE_GETTEXT_DOMAIN=\"oxide-qt\" -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -Dqmloxideplugin_EXPORTS -std=c++11 
-fPIC -I/<>/obj-x86_64-linux-gnu/oxide/qt/qmlplugin 
-I/<>/oxide/qt/qmlplugin -I/<>/oxide 
-I/usr/include/qt5/QtCore/5.2.1 -I/usr/include/qt5/QtCore/5.2.1/QtCore 
-I/usr/include/qt5/QtQml/5.2.1 -I/usr/include/qt5/QtQml/5.2.1/QtQml 
-I/usr/include/qt5/QtNetwork/5.2.1 -I/usr/include/qt5/QtNetwork/5.2.1/QtNetwork 
-I/usr/include/qt5 -I/usr/include/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I/usr/include/qt5/QtQml 
-I/usr/include/qt5/QtNetwork -I/usr/include/qt5/QtQuick 
-I/usr/include/qt5/QtGui -I/<>/oxide/qt/core/api/includes 
-I/<>/oxide/qt/quick/api/includes-fno-rtti -o 
CMakeFiles/qmloxideplugin.dir/oxide_qml_download
 _request.cc.o -c 
/<>/oxide/qt/qmlplugin/oxide_qml_download_request.cc
  Linking CXX executable tst_oxideqquicknavigationitem
  cd 
/<>/obj-x86_64-linux-gnu/oxide/qt/tests/unit/oxideqquicknavigationitem
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/tst_oxideqquicknavigationitem.dir/link.txt --verbose=1
  /usr/bin/x86_64-linux-gnu-g++-std=c++11-fuse-ld=gold 
CMakeFiles/tst_oxideqquicknavigationitem.dir/tst_oxideqquicknavigationitem.cc.o 
CMakeFiles/tst_oxideqquicknavigationitem.dir/tst_oxideqquicknavigationitem_automoc.cpp.o
  -o tst_oxideqquicknavigationitem -rdynamic 
../../../../../chromium/libOxideQtCore.so.0 
../../../../../out/lib/libOxideQtQuick.so.0 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Test.so.5.2.1 
../../../../../chromium/libOxideQtCore.so.0 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.2.1 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.2.1 
  ../../../../../out/lib/libOxideQtQuick.so.0: error: undefined reference to 
'glGenTextures'
  ../../../../../out/lib/libOxideQtQuick.so.0: error: undefined reference to 
'glBindTexture'
  ../../../../../out/lib/libOxideQtQuick.so.0: error: undefined reference to 
'glDeleteTextures'
  collect2: error: ld returned 1 exit status
  make[3]: *** 
[oxide/qt/tests/unit/oxideqquicknavigationitem/tst_oxideqquicknavigationitem] 
Error 1
  make[3]: Leaving directory `/<>/obj-x86_64-linux-gnu'
  make[2]: *** 
[oxide/qt/tests/unit/oxideqquicknavigationitem/CMakeFiles/tst_oxideqquicknavigationitem.dir/all]
 Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1638915/+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 1642381] Re: Single process mode creates a zygote process

[Chris Coulson]

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** 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/1642381

Title:
  Single process mode creates a zygote process

Status in Oxide:
  Fix Released

Bug description:
  I just noticed this when debugging another issue - running Oxide in
  single process mode still results in a zygote process being spawned

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642381/+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 1643428] Re: Fling scroll happens upwards even if finger movement is downwards

[Chris Coulson]

** 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/1643428

Title:
  Fling scroll happens upwards even if finger  movement is downwards

Status in Oxide:
  Fix Released

Bug description:
  In M10, with any page, if we scroll rapidly( flick page with finger
  up), page moves opposite direction of finger movement. This is quite
  visible in all sites.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1643428/+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 1643548] Re: Make it obvious that Oxide.Ubuntu is experimental

[Chris Coulson]

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** 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/1643548

Title:
  Make it obvious that Oxide.Ubuntu is experimental

Status in Oxide:
  Fix Released

Bug description:
  1.20 will ship with an incomplete implementation of UbuntuWebView. It
  should be obvious that this is experimental, so we should probably add
  a warning message that appears at module import for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1643548/+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 1570828] Re: Multiple Web Apps crashes when returning from a linked page

[Chris Coulson]

** Changed in: oxide/1.19
   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/1570828

Title:
  Multiple Web Apps crashes when returning from a linked page

Status in Oxide:
  Fix Released
Status in Oxide 1.18 series:
  Fix Committed
Status in Oxide 1.19 series:
  Fix Released
Status in webapps-sprint:
  In Progress

Bug description:
  This bug seems affect Twitter, Facebook and Gmail Web App, so it could
  be a webbrowser bug. All of those apps crash when returning from a
  linked page.

  Steps to reproduce:
  - Open Twitter/Facebook/Gmail web app
  - On the Twitter/Facebook timeline or on an email, tap on a external link (a 
web page, an article from a magazine, ...)
  - A new external page pops up from the bottom
  - _Magnify_ the text on the page / article
  - Tap the button at the top left to return to Twitter/Facebook/Gmail app
  - Twitter/Facebook/Gmail crashes instantly.

  When you restart the crashed web app, it starts with the external page
  / article.

  It happens on a Meizu MX4 with OTA 10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1570828/+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 1640542] Re: [oxide 1.18] oops error when navigating a website from facebook or twitter

[Chris Coulson]

** Also affects: oxide/1.18
   Importance: Undecided
   Status: New

** Also affects: oxide/1.19
   Importance: Undecided
   Status: New

** Changed in: oxide/1.18
   Importance: Undecided => Critical

** Changed in: oxide/1.19
   Importance: Undecided => Critical

** Changed in: oxide/1.18
   Status: New => Triaged

** Changed in: oxide/1.19
   Status: New => Triaged

** Changed in: oxide/1.19
Milestone: None => 1.18.5

** Changed in: oxide/1.18
Milestone: None => 1.18.5

** Changed in: oxide/1.19
Milestone: 1.18.5 => 1.19.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/1640542

Title:
  [oxide 1.18] oops error when navigating a website from facebook or
  twitter

Status in Canonical System Image:
  New
Status in Oxide:
  Fix Released
Status in Oxide 1.18 series:
  Triaged
Status in Oxide 1.19 series:
  Triaged

Bug description:
  /*\ only with silo 2148 installed

  Environment: 
  current build number: 227
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-11-09 16:48:22
  version version: 227
  version ubuntu: 20161109
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions: have a fb or twitter account registered

  Steps to reproduce:

  1º Open Facebook or twitter
  2º Scroll down until you see a post/link to another website(an article or so)
  3º Navigate through the main sections of the website and return to home page

  Current result: "oops, something went wrong" message appears randomly
  when navigating through the site

  Expected result: no error should appear when trying to load pages

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640542/+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 1640542] Re: [oxide 1.18] oops error when navigating a website from facebook or twitter

[Chris Coulson]

I still can't make any test case trigger this bug, but this fixes it in
any case:
https://git.launchpad.net/oxide/commit/?id=8c6ebc3f5b827652236438632a5434a5e20aa5cc

** Changed in: oxide
Milestone: None => branch-1.20

** Changed in: oxide
   Status: Confirmed => 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/1640542

Title:
  [oxide 1.18] oops error when navigating a website from facebook or
  twitter

Status in Canonical System Image:
  New
Status in Oxide:
  Fix Released
Status in Oxide 1.18 series:
  Triaged
Status in Oxide 1.19 series:
  Triaged

Bug description:
  /*\ only with silo 2148 installed

  Environment: 
  current build number: 227
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-11-09 16:48:22
  version version: 227
  version ubuntu: 20161109
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions: have a fb or twitter account registered

  Steps to reproduce:

  1º Open Facebook or twitter
  2º Scroll down until you see a post/link to another website(an article or so)
  3º Navigate through the main sections of the website and return to home page

  Current result: "oops, something went wrong" message appears randomly
  when navigating through the site

  Expected result: no error should appear when trying to load pages

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640542/+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 1643547] [NEW] Make it obvious that Oxide.Ubuntu is experimental

[Chris Coulson]

Public bug reported:

1.20 will ship with an incomplete implementation of UbuntuWebView. It
should be obvious that this is experimental, so we should probably add a
warning message that appears at module import for now.

** 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/1643547

Title:
  Make it obvious that Oxide.Ubuntu is experimental

Status in Oxide:
  New

Bug description:
  1.20 will ship with an incomplete implementation of UbuntuWebView. It
  should be obvious that this is experimental, so we should probably add
  a warning message that appears at module import for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1643547/+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 1643548] [NEW] Make it obvious that Oxide.Ubuntu is experimental

[Chris Coulson]

Public bug reported:

1.20 will ship with an incomplete implementation of UbuntuWebView. It
should be obvious that this is experimental, so we should probably add a
warning message that appears at module import for now.

** Affects: oxide
 Importance: High
 Status: Triaged

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
Milestone: None => branch-1.20

-- 
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/1643548

Title:
  Make it obvious that Oxide.Ubuntu is experimental

Status in Oxide:
  Triaged

Bug description:
  1.20 will ship with an incomplete implementation of UbuntuWebView. It
  should be obvious that this is experimental, so we should probably add
  a warning message that appears at module import for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1643548/+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 1642682] [NEW] Provide a script for setting up remote debugging environment

[Chris Coulson]

Public bug reported:

If you need to debug something that's specific to a mobile device,
pretty much your only option here for various reasons (lack of disk
space, lack of memory) is using gdbserver and debugging it from another
host. However, every time I do this I have to search Google to relearn
how to get it working when using separate debug files, then set up an
environment on the host and then spend hours going around in circles,
tryinh to make it work.

We should just have a tool that does this automatically.

** 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/1642682

Title:
  Provide a script for setting up remote debugging environment

Status in Oxide:
  Triaged

Bug description:
  If you need to debug something that's specific to a mobile device,
  pretty much your only option here for various reasons (lack of disk
  space, lack of memory) is using gdbserver and debugging it from
  another host. However, every time I do this I have to search Google to
  relearn how to get it working when using separate debug files, then
  set up an environment on the host and then spend hours going around in
  circles, tryinh to make it work.

  We should just have a tool that does this automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642682/+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 1642381] [NEW] Single process mode creates a zygote process

[Chris Coulson]

Public bug reported:

I just noticed this when debugging another issue - running Oxide in
single process mode still results in a zygote process being spawned

** Affects: oxide
 Importance: Medium
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
Milestone: None => branch-1.20

-- 
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/1642381

Title:
  Single process mode creates a zygote process

Status in Oxide:
  Triaged

Bug description:
  I just noticed this when debugging another issue - running Oxide in
  single process mode still results in a zygote process being spawned

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1642381/+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 1642318] [NEW] arm64 xenial build fails

[Chris Coulson]

Public bug reported:

FAILED: /usr/bin/aarch64-linux-gnu-gcc -MMD -MF 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o.d 
-DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PDF=1 
-DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DNO_TCMALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 
-DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 
-DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../.. -Igen -I../../third_party/libvpx/source/config 
-I../../third_party/libvpx/source/config/linux/arm64 
-I../../third_party/libvpx/source/libvpx -Igen/third_party/libvpx 
-I../../third_party/libvpx/source/libvpx -fno-strict-aliasing 
--param=ssp-buffer-size
 =4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g1 
-fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function 
-Wno-sign-compare  -c 
../../third_party/libvpx/source/libvpx/vpx_dsp/arm/idct32x32_34_add_neon.c -o 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o
{standard input}: Assembler messages:
{standard input}: Error: unaligned opcodes detected in executable segment
ninja: build stopped: subcommand failed.
oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
make[4]: *** [oxide/CMakeFiles/build_all] Error 1
make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu'
CMakeFiles/Makefile2:267: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/obj-aarch64-linux-gnu'
dh_auto_build: make -j4 returned exit code 2
debian/rules:26: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:20: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

** Affects: oxide
 Importance: Critical
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
Milestone: None => branch-1.20

-- 
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/1642318

Title:
  arm64 xenial build fails

Status in Oxide:
  Triaged

Bug description:
  FAILED: /usr/bin/aarch64-linux-gnu-gcc -MMD -MF 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o.d 
-DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PDF=1 
-DENABLE_SPELLCHECK=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_PANGO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DNO_TCMALLOC -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
-DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 
-DUSE_PROPRIETARY_CODECS -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 
-DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../.. -Igen -I../../third_party/libvpx/source/config 
-I../../third_party/libvpx/source/config/linux/arm64 
-I../../third_party/libvpx/source/libvpx -Igen/third_party/libvpx 
-I../../third_party/libvpx/source/libvpx -fno-strict-aliasing 
--param=ssp-buffer-si
 ze=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g1 
-fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function 
-Wno-sign-compare  -c 
../../third_party/libvpx/source/libvpx/vpx_dsp/arm/idct32x32_34_add_neon.c -o 
obj/third_party/libvpx/libvpx/idct32x32_34_add_neon.o
  {standard input}: Assembler messages:
  {standard input}: Error: unaligned opcodes detected in executable segment
  ninja: build stopped: subcommand failed.
  oxide/CMakeFiles/build_all.dir/build.make:60: recipe for target 
'oxide/CMakeFiles/build_all' failed
  make[4]: *** [oxide/CMakeFiles/build_all] Error 1
  make[4]: Leaving directory '/<>/obj-aarch64-linux-gnu'
  CMakeFiles/Makefile2:267: recipe for target 
'oxide/CMakeFiles/build_all.dir/all' failed
  make[3]: *** [oxide/CMakeFiles/build_all.dir/all] Error 2
  

[Ubuntu-webapps-bugs] [Bug 1570828] Re: Multiple Web Apps crashes when returning from a linked page

[Chris Coulson]

** Also affects: oxide/1.19
   Importance: Undecided
   Status: New

** Also affects: oxide/1.18
   Importance: Undecided
   Status: New

** Changed in: oxide/1.18
Milestone: None => 1.18.5

** Changed in: oxide/1.19
Milestone: None => 1.19.1

** Changed in: oxide/1.18
   Status: New => Fix Committed

** Changed in: oxide/1.19
   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/1570828

Title:
  Multiple Web Apps crashes when returning from a linked page

Status in Oxide:
  Fix Released
Status in Oxide 1.18 series:
  Fix Committed
Status in Oxide 1.19 series:
  Fix Committed
Status in webapps-sprint:
  In Progress

Bug description:
  This bug seems affect Twitter, Facebook and Gmail Web App, so it could
  be a webbrowser bug. All of those apps crash when returning from a
  linked page.

  Steps to reproduce:
  - Open Twitter/Facebook/Gmail web app
  - On the Twitter/Facebook timeline or on an email, tap on a external link (a 
web page, an article from a magazine, ...)
  - A new external page pops up from the bottom
  - _Magnify_ the text on the page / article
  - Tap the button at the top left to return to Twitter/Facebook/Gmail app
  - Twitter/Facebook/Gmail crashes instantly.

  When you restart the crashed web app, it starts with the external page
  / article.

  It happens on a Meizu MX4 with OTA 10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1570828/+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 1641116] [NEW] Expose via webview

[Chris Coulson]

Public bug reported:

This is already exposed via content, so should be fairly trivial.

** 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/1641116

Title:
  Expose  via webview

Status in Oxide:
  Triaged

Bug description:
  This is already exposed via content, so should be fairly trivial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1641116/+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 1640825] Re: Investigate why Scheduler::pending_submit_frames is never zero

[Chris Coulson]

This appears to be actually working correctly, although what is
displayed in chrome://tracing/ doesn't appear correct

** Changed in: oxide
   Importance: High => Undecided

** Changed in: oxide
   Status: Triaged => Invalid

** Changed in: oxide
Milestone: branch-1.20 => None

** Changed in: oxide
 Assignee: Chris Coulson (chrisccoulson) => (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/1640825

Title:
  Investigate why Scheduler::pending_submit_frames is never zero

Status in Oxide:
  Invalid

Bug description:
  Rendering appears fairly janky on my desktop, so I took a look at
  chrome://tracing/ and noticed that Scheduler::pending_submit_frames in
  the browser compositor is never zero. I'm pretty sure that this is a
  bug (although not necessarily related to my original problem).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1640825/+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 1640825] [NEW] Investigate why Scheduler::pending_submit_frames is never zero

[Chris Coulson]

Public bug reported:

Rendering appears fairly janky on my desktop, so I took a look at
chrome://tracing/ and noticed that Scheduler::pending_submit_frames in
the browser compositor is never zero. I'm pretty sure that this is a bug
(although not necessarily related to my original problem).

** Affects: oxide
 Importance: High
 Assignee: Chris Coulson (chrisccoulson)
 Status: Triaged

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide
Milestone: None => branch-1.20

-- 
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/1640825

Title:
  Investigate why Scheduler::pending_submit_frames is never zero

Status in Oxide:
  Triaged

Bug description:
  Rendering appears fairly janky on my desktop, so I took a look at
  chrome://tracing/ and noticed that Scheduler::pending_submit_frames in
  the browser compositor is never zero. I'm pretty sure that this is a
  bug (although not necessarily related to my original problem).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1640825/+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