self.chooseFileSystemEntries() throws DOMException

Bug #1837292 reported by guest271314
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

Chromium version: 77.0.3854.3 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (32-bit) (https://launchpad.net/~chromium-daily/+archive/ubuntu/dev)

Worked at: Chromium version 77.0.3833.0

Context: Executed at chrome-extension: protocol

Revision history for this message
guest271314 (guest271314) wrote :
Revision history for this message
guest271314 (guest271314) wrote :
Revision history for this message
guest271314 (guest271314) wrote :

Fixed.

Using status = await handle . requestPermission({ writable = true }) which requires granting permission at two consectutive prompts

1) "Let sites read this folder";
2) "Save changes to original files"

Additionally, substituted removeEntry() for remove().

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

Closing per last comment and per upstream bug status (https://bugs.chromium.org/p/chromium/issues/detail?id=986060).

@guest271314: please note that ppa:chromium-team/dev is not recommended for end users, nor is it supported in any way. It's mostly used for build testing purposes. Bug reports against versions of chromium in that PPA are welcome of course, but packages in there might break in unexpected ways at any time.

Changed in chromium-browser (Ubuntu):
status: New → Invalid
Revision history for this message
guest271314 (guest271314) wrote :

@osomon

> nor is it supported in any way

> Bug reports against versions of chromium in that PPA are welcome of course

Does that mean that the team which publishes ppa:chromium-team/dev do not try to fix source code of the published Chromium package when bug reports point out specific code run in the browser crashes the tab as well, that is, similar to https://github.com/web-platform-tests/wpt/issues/17960

> We don't provide support for Chromium. If the crash doesn't reproduce in Chrome you're on your own unfortunately

?

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

This means that packaging issues will be looked at, but issues with the browser's behaviour should be reported upstream (and yes upstream as a vendor doesn't officially support Chromium, only Chrome, so it's likely that the first thing that they will ask is whether the issue is reproducible with Chrome).

https://launchpad.net/~chromium-team mostly handles Ubuntu-specific packaging, and bug triaging and forwarding to upstream, on a best-effort basis, because of limited manpower.

Revision history for this message
guest271314 (guest271314) wrote :

Should this bug Issue 943484: Tab crashes when HTMLMediaElement.captureStream() is called on <video> with MediaSource Blob URL set at src https://bugs.chromium.org/p/chromium/issues/detail?id=943484 be filed here?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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