Public bug reported:
The mobile context menu has a "Cancel" button, but the string doesn't
appear to be in the pot file
** Affects: oxide
Importance: High
Status: Triaged
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Status: New => Triaged
--
** Changed in: oxide
Milestone: None => branch-1.20
** 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/1570828
Title:
https://git.launchpad.net/oxide/commit/?id=b20811838c735ae8e79ece1430b1c490b8b9f125
** 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.
or
context menu initiated calls. We don't want the application to block
these (it should create a new tab / window unconditionally)
** Affects: oxide
Importance: High
Assignee: Chris Coulson (chrisccoulson)
Status: Triaged
** Changed in: oxide
Importance: Undecided => Hig
** Changed in: oxide/1.18
Status: Confirmed => Fix Committed
** Changed in: oxide
Status: New => Won't Fix
** Changed in: oxide
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed
: 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_oxideqquicknavigationite
Public bug reported:
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
** Package changed: oxide-qt (Ubuntu) => oxide
--
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/1638663
Title:
Segfault on arm64 dragonboard
Status in Oxide:
New
Status in
Public bug reported:
I want to experiment with a fix for bug 1607411, but to do this I need
to make a fairly large architectural change. Essentially, I want to:
- With the exception of qt/core/api, rename qt/core to qt/lib
- Rename qt/lib/glue to qt/lib/public (it's only "glue" because "public"
Public bug reported:
We should move it to /usr/share/oxide-qt/doc instead
** 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
** Changed in: oxide
Milestone: branch-1.19 => branch-1.20
** Also affects: oxide/1.19
Importance: Undecided
Status: New
** Changed in: oxide/1.19
Importance: Undecided => High
** Changed in: oxide/1.19
Status: New => Triaged
--
You received this bug notification
This is sort-of fixed now - we assume that the presence of a mouse
implies windowed mode, and adjust the behaviour of the webview
accordingly.
** Changed in: oxide
Status: Triaged => Fix Released
** Changed in: oxide
Milestone: branch-1.19 => branch-1.20
--
You received this bug
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/1631184
Title:
Location bar is hidden for tabs opened via window.open
Sta
https://git.launchpad.net/oxide/commit/?id=e5de434df5a3f32122b967de3b58acbafa2d5b67
** Changed in: oxide
Status: New => In Progress
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
*
** Changed in: oxide
Status: Triaged => Fix Released
** Changed in: oxide
Milestone: None => branch-1.20
** Changed in: oxide
Assignee: (unassigned) => Santosh (santoshbit2007)
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which
Public bug reported:
The constructor of OxideQQuickNavigationHistory is public, and it
shouldn't be.
** Affects: oxide
Importance: High
Assignee: Chris Coulson (chrisccoulson)
Status: Triaged
** Affects: oxide/1.19
Importance: High
Status: New
** Changed
Public bug reported:
With UbuntuWebView responsible for handling context menus, we need an
additional API to allow applications to add custom entries to it.
** Affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
Whilst UbuntuWebView will be responsible for displaying JS dialogs, we
want an API to allow applications to intercept requests to display a
dialog so that they can block the default dialog and display their own.
** Affects: oxide
Importance: Undecided
Status:
Public bug reported:
UbuntuWebView should provide a file picker. I'm not sure how this should
work on systems without content hub though.
** Affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
WebApps bug
Public bug reported:
UbuntuWebView needs support for displaying context menus using the UITK.
** 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.
Public bug reported:
We need support for testing the auxilliary UI components in
UbuntuWebView. I guess this will use autopilot.
** Affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking,
Public bug reported:
For https://blueprints.launchpad.net/oxide/+spec/ubuntu-webview-
implementation, we need to create a new QML module, library and WebView
class.
** Affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
** 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/1503639
Title:
Stop reference counting BrowserContext
Status in
** 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/1625122
Title:
Building oxide in debug mode does not run
** 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/1448079
Title:
Don't run the event loop after QGuiApplication
** 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/1625484
Title:
webbrowser-app: new tab view fills entire window,
Targetting at 1.18 as it's a pre-requisite for another change that needs
to be backported.
** Also affects: oxide/1.18
Importance: Undecided
Status: New
** Changed in: oxide/1.18
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
** Changed in: oxide/1.18
Milestone: N
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/1503639
Title:
Stop reference counting BrowserContext
Status in Oxide:
Fix Rel
** Changed in: oxide/1.17
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/1625122
Title:
Building oxide in debug mode does not run
https://git.launchpad.net/oxide/commit/?id=07869181066803f43f6f6d831306d887953edb50
** Changed in: oxide
Status: Triaged => Fix Released
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
** Changed in: oxide
Milestone: None => branch-1.19
Public bug reported:
Chromium initializes content::ImageTransportFactory, the implementation
of which is provided by GpuProcessTransportFactory. This class spins up
a thread (via cc::SingleThreadTaskGraphRunner) that we never use in
Oxide.
** Affects: oxide
Importance: Medium
Public bug reported:
This occurs in debug builds with OXIDE_PROCESS_MODEL=site-per-process
[1007/182712:FATAL:render_frame_impl.cc(2325)] Check failed: frame_.
#0 0x7fc42b2e26b1 base::debug::StackTrace::StackTrace()
#1 0x7fc42b33e5e3 logging::LogMessage::~LogMessage()
#2 0x7fc428ac5783
Public bug reported:
- Launch webbrowser-app with OXIDE_PROCESS_MODEL=site-per-process
- Navigate to http://csreis.github.io/tests/cross-site-iframe.html
- Click on one of the "Go cross-site.." buttons.
Notice that the iframe appears to be blank, but it works in Chromium and
without
Public bug reported:
Chrome's unresponsive renderer dialog groups unresponsive tabs that are
hosted in the same process. webbrowser-app wouldn't be able to do this
because we don't provide the ability to determine which webviews are
sharing a process.
** Affects: oxide
Importance: Low
There's not much point in keeping this bug open (see my last comment),
so I'm going to close it for now. Feel free to reopen if you this might
be a bug in Oxide
** Changed in: oxide
Status: New => Invalid
** No longer affects: webbrowser-app (Ubuntu)
--
You received this bug
Public bug reported:
I guess this is a regression from recent changes to the location bar
controller. New tabs created via window.open appear with the locationbar
hidden, which makes the browser on desktop almost unusable
** Affects: oxide
Importance: Critical
Assignee: Chris Coulson
https://git.launchpad.net/oxide/commit/?id=090a4397744d3d6e105d9a3f79518be69888aed6
** 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.
** 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/1567974
Title:
tst_LocationBarController is flaky
Status in Oxide:
Fix
https://git.launchpad.net/oxide/commit/?id=70bf36cb9edd314c0939fd1fc73ace9bdc354744
** 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.
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Status: New => Triaged
** No longer affects: webbrowser-app (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
Public bug reported:
The webview compositor uses a full LayerTreeHost, but we effectively
only have a single layer (and that's a SurfaceLayer). We should be able
to do away with the LayerTreeHost entirely, using only a cc::Display and
passing the renderer compositor's Surface directly to it.
https://git.launchpad.net/oxide/commit/?id=5358532bbf0915c25e779ddb5bf919b0ceaee9c6
** 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.
Running it in valgrind gives a clue:
==19941== Invalid read of size 4
==19941==at 0x6604DA4: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1)
==19941==by 0x1877174F: ???
==19941==by 0xFFFD: ???
==19941==by 0x2483D3FE: ??? (in
Public bug reported:
There's quite a bit of functionality in here that's otherwise difficult
to test, so we should have some unit tests for this. This will require
making oxide::BrowserContext completely abstract though.
** Affects: oxide
Importance: Medium
Status: Triaged
**
Public bug reported:
WebPreferences::sanSerifFontFamily should be
WebPreferences::sansSerifFontFamily
** Affects: oxide
Importance: Low
Status: Triaged
** Changed in: oxide
Importance: Undecided => Low
** Changed in: oxide
Status: New => Triaged
--
You received this
Public bug reported:
There are several scenarios where we should request that the browser
doesn't hide its UI when in auto mode, including:
- SecurityStatus.securityLevel indicates a degraded status.
- The renderer is unresponsive.
We should also review some of the conditions in
Public bug reported:
We currently don't provide any indication if a renderer hangs, and we
should.
This will probably also require a public API for killing the hung
process (essentially turning the private test API we have in to a public
API).
** Affects: oxide
Importance: Medium
** 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/1625664
Title:
Component build is broken (DevToolsHttpHandler isn't defined)
** 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/1503639
Title:
Stop reference counting BrowserContext
Status in Oxide:
** Changed in: oxide
Milestone: None => branch-1.19
** 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/1599771
Title:
** Changed in: oxide/1.16
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1605365
Title:
Front camera is inverted on BQ E5 hardware
Status in
It turned out to be something ridiculous
https://git.launchpad.net/oxide/commit/?id=9fc616d54895eaf0d1b92289c110dd0457227260
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Status: New => Triaged
** Changed in: oxide
Assignee: (unassigned) => Chri
Public bug reported:
This isn't exported from content because it's not a public API, but
we're using it in Oxide for the per-WebContext remote debugging instance
(see also bug 1622247).
** Affects: oxide
Importance: Critical
Assignee: Chris Coulson (chrisccoulson)
Status
Public bug reported:
These both currently default to false, but this is silly. The default
configuration should be something that is sane enough to use for a web
browser, and turning off local storage by default really doesn't make
sense.
** Affects: oxide
Importance: Undecided
Public bug reported:
This would be a nice addition alongside our existing user script
messaging.
** 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://git.launchpad.net/oxide/commit/?id=3c93634af8a7e498925123c9ae7422531438b84f
** 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.
Public bug reported:
We expose a C++ API for these, but they can't really be used from C++.
This is because the callbacks all require JS callables (using QJSValue).
In addition to that ScriptMessageHandler requires driving
QQmlParserStatus::componentComplete
** Affects: oxide
Importance:
Public bug reported:
This is something I noticed when documenting the API. Setting these
string properties to an empty string should probably restore the system-
dependent default.
** Affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
In frameAdded, the frame's parent should be valid and it should appear
in its parent's list of children.
In frameRemoved, the frame's parent should be null and it should not
appear in its parent's list of children.
This isn't tested anywhere AFAICT.
** Affects: oxide
Public bug reported:
The permission request signals pass the request wrapped in a QJSValue,
which relies on the webview being exposed to the QML engine. This was
done as a way to transfer and share ownership of the request instance
across multiple slots.
Essentially, this is working around the
Public bug reported:
This is like bug 1623428, but for OxideQQuickWebView.
** 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.
Public bug reported:
This is like bug 1623428, but for OxideQQuickUserScript
** 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://git.launchpad.net/oxide/commit/?id=3e4bf15a8f665b45392eb384279574922df513cc
** Changed in: oxide
Milestone: None => branch-1.19
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
** Changed in: oxide
Status: Triaged => In Progress
*
Public bug reported:
There's a C++ API but there's not a nice way to construct this outside
of QML (you have to manually call the QQmlParserStatus methods to do it
properly).
There should be a new constructor for this that takes the construct
parameters (dataPath etc) which can only be called
https://git.launchpad.net/oxide/commit/?id=0e630bbdbb18b00c5743c1226377f7a6af688cf1
** Changed in: oxide
Status: In Progress => Fix Released
** Changed in: oxide
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
You received this bug notification because you are a
Public bug reported:
This appears to be a regression due to a Chromium change in trunk, but
animated scrolling is currently broken there.
** Affects: oxide
Importance: High
Assignee: Chris Coulson (chrisccoulson)
Status: In Progress
** Changed in: oxide
Importance
This one appears to have been fixed in Chromium
** Changed in: oxide
Status: Triaged => Invalid
** Changed in: oxide
Milestone: branch-1.18 => None
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
** Changed in: oxide
Milestone: branch-1.18 => branch-1.19
** Also affects: oxide/1.18
Importance: Undecided
Status: New
** Changed in: oxide/1.18
Importance: Undecided => High
** Changed in: oxide/1.18
Status: New => Triaged
--
You received this bug notification
Public bug reported:
Oxide has no API reference documentation, which is fairly rubbish for
application developers. We should add some.
** Affects: oxide
Importance: High
Assignee: Chris Coulson (chrisccoulson)
Status: In Progress
** Changed in: oxide
Importance: Undecided
Public bug reported:
Per-WebContext remote debugging hasn't worked correctly for a long time,
since a Chromium change meant that all WebContents in a process were
debuggable on all remote debugging HTTP endpoints.
Since
Public bug reported:
There are no tests for non-overridable certificate errors that affect
the main-frame. We need to verify that they result in:
- the load being stopped (as opposed to failing).
- a blank transient page being loaded until the error is destroyed.
** Affects: oxide
Public bug reported:
The OxideQCertificateError::Error enum has an "OK" value. It seems to be
a mistake that this exists (I'm not going to document it). We should
assert that this value is never used.
** Affects: oxide
Importance: Low
Status: Triaged
** Changed in: oxide
Public bug reported:
Currently a lot of errors are lumped in to ErrorDomainConnection, such
as various SSL related errors. These could probably get their own error
type (eg, ErrorDomainSSL). This would be distinct from
ErrorDomainCertificate, which is basically currently unused (main frame
Public bug reported:
This is currently untested, although I was aware it wasn't complete yet
- I was just reminded whilst writing documentation.
Basically, we need to implement
ContentRendererClient::GetNavigationErrorStrings and then add some tests
for this.
** Affects: oxide
Importance:
Public bug reported:
As I write some documentation, I realized we should provide a single
header so that apps can just do:
#include
or
#include
** Affects: oxide
Importance: Low
Status: Triaged
** Changed in: oxide
Importance: Undecided => Low
** Changed in: oxide
** Changed in: oxide/1.17
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/1260103
Title:
oxide should use an app-specific path for shared
** Changed in: oxide/1.17
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/1616595
Title:
Fails to build with Qt 5.2
Status in Oxide:
Fix
** Changed in: oxide/1.17
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/1615832
Title:
Fails to build with Qt 5.6
Status in Oxide:
Fix
There are 1.17 builds building in https://launchpad.net/~oxide-
builds/+archive/ubuntu/oxide-next/ with this workaround
** Changed in: oxide/1.17
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is
** Changed in: oxide/1.17
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/1618530
Title:
Ozone platform isn't included with switch to GN
https://git.launchpad.net/~oxide-developers/oxide/+git/chromium/commit/?h=oxide/dev/cr2837=076c7d60d24229c83c23124b7d5fceef581b3a15
https://git.launchpad.net/oxide/commit/?id=e08e7d7f8460307c21514330e92b0a2769ba02a4
** Changed in: oxide
Status: In Progress => Fix Released
--
You received
https://git.launchpad.net/oxide/commit/?id=d6c45ddaf11e0a079782d0c83f8ae0ce6191fae4
** 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.
ide
Status: New => Fix Released
** Changed in: oxide
Milestone: None => branch-1.18
** 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 subscri
Not going to fix this for 1.16, as it needs a different change and 1.17
is less than a fortnight away from being the next stable update.
** Changed in: oxide/1.16
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which
** Also affects: oxide/1.17
Importance: Undecided
Status: New
** Also affects: oxide/1.16
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
** Changed in: oxide/1.17
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/1601887
Title:
Camera image is rotated by 90° on M10 because Qt
** Changed in: oxide/1.16
Status: Fix Committed => Fix Released
** Changed in: oxide/1.17
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.
The new bug is bug 1618589. Would be great if someone could investigate
that.
** Changed in: oxide/1.16
Status: Fix Committed => Fix Released
** Changed in: oxide/1.17
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Changed in: oxide/1.17
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/1615683
Title:
Oxide 1.17 breaks tab navigation between input
https://git.launchpad.net/oxide/commit/?id=3fd8a83d04c89065d8dce8e4770ae285dbb3e8f5
** 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.
** 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/1613258
Title:
Web browser can't browse anything - "The rendering
/keyboard_code_conversion.cc:303:10: error:
‘Key_MicVolumeUp’ is not a member of ‘Qt’
case Qt::Key_MicVolumeUp:
^
ninja: build stopped: subcommand failed.
** Affects: oxide
Importance: Critical
Assignee: Chris Coulson (chrisccoulson)
Status: Triaged
** Affects: oxide/1.17
Importance
https://git.launchpad.net/~oxide-developers/oxide/+git/oxide-
tools/commit/?id=4266c76beb6b686531561fb87b7ea5b3e04dd1b5
** Changed in: oxide
Status: New => Triaged
** Changed in: oxide
Status: Triaged => Fix Released
** Changed in: oxide/1.17
Status: New => Fix Released
--
** No longer affects: oxide/1.16
--
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/1616537
Title:
Just use Google's GN binaries
Status in Oxide:
New
Status in Oxide 1.17 series:
New
Public bug reported:
We currently compile our own GN binaries (well, binary, because we only
compile it for linux64 at the moment) and provide it in lp:~oxide-
developers/oxide/+git/oxide-tools. GN changed recently in a backwards-
incompatible way which makes it difficult to provide binaries that
https://git.launchpad.net/oxide/commit/?id=b9755bb6f0e1fbed61e4d01b22ff9cbc4a51c57a
** 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.
** Also affects: oxide/1.16
Importance: Undecided
Status: New
** Also affects: oxide/1.17
Importance: Undecided
Status: New
** Changed in: oxide
Milestone: None => branch-1.18
** Changed in: oxide/1.16
Milestone: None => 1.16.9
** Changed in: oxide/1.17
** 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/1505746
Title:
Browser detection is broken for many WebRTC demos
Status in
r-yakkety/CMakeFiles/CMakeError.log".
It seems that Qt5PlatformSupport.pc no longer exists
** Affects: oxide
Importance: Critical
Assignee: Chris Coulson (chrisccoulson)
Status: Triaged
** Affects: oxide/1.17
Importance: Critical
Status: Triaged
** Changed in: ox
Importance: Undecided => Critical
** Changed in: oxide
Status: New => Triaged
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
** Also affects: oxide/1.17
Importance: Undecided
Status: New
** Changed in: oxide/1.17
Importance:
101 - 200 of 805 matches
Mail list logo
