Ship directory picking and directory drag and drop

NEW
Unassigned

Status

()

Core
DOM
2 years ago
a day ago

People

(Reporter: jwatt, Unassigned)

Tracking

(Depends on: 1 bug, 4 keywords)

Trunk
dev-doc-needed, DevAdvocacy, feature, meta
Points:
---
Dependency tree / graph
Bug Flags:
qe-verify +

Firefox Tracking Flags

(firefox42 affected)

Details

(Whiteboard: [DevRel:P2], URL)

(Reporter)

Description

2 years ago
Bug 1164310 implemented MS's proposal to support directory picking and directory drag and drop. The "Unofficial Draft" spec is very much a work in progress though and subject to change. Currently our implementation is behind the dom.input.dirpicker pref (enabled only in Nightly). This bug will track any issues that need to be resolved before the pref can be flipped to true for release.
(Reporter)

Updated

2 years ago
Depends on: 1164310, 1188818
(Reporter)

Updated

2 years ago
(Reporter)

Updated

2 years ago
Depends on: 907707
(Reporter)

Comment 1

2 years ago
We should consider pushing for and implementing bug 1173320 too.
Depends on: 1173320
(Reporter)

Updated

2 years ago
Depends on: 1186932
(Reporter)

Updated

2 years ago
Depends on: 1201106
OS: Unspecified → All
Hardware: Unspecified → All
Keywords: dev-doc-needed

Comment 2

2 years ago
Do you have a demo page (with a server side) to test Directory Upload?

Comment 3

2 years ago
(In reply to Loic from comment #2)
> Do you have a demo page (with a server side) to test Directory Upload?

https://jwatt.org/blog/2015/09/14/directory-picking-and-drag-and-drop give this links https://jwatt.org/tmp/directory.html
Keywords: feature, meta

Comment 4

2 years ago
When a user selects a directory, are they aware of the potentially sensitive contents of the directory?  For example, if the user selects ~/.config , should the browser really send out all application configuration data?  What about ~/.ssh or ~/.gpg (i.e. the recent targets of the pdf.js vulnerability)?

uploading arbitrary files is risky.  recursively uploading entire directories seems far riskier.  There is no security analysis at https://wicg.github.io/directory-upload/proposal.html .  Has anyone done one?
Daniel, that is being discussed in bug 907707.
Keywords: DevAdvocacy
webcompat issue related to this.

Updated

a year ago

Updated

a year ago

Updated

a year ago
Duplicate of this bug: 1257179
Depends on: 1258694, 1263992
Depends on: 1264236
I think we'll want some manual testing before releasing this (after implementation is complete), so setting the qe-verify+ flag.

Test suggestions/scenarios are appreciated.
Flags: qe-verify+

Updated

a year ago
Depends on: 1266531
(Reporter)

Updated

a year ago
No longer depends on: 1266531
Whiteboard: [DevRel:P2]

Updated

11 months ago
Depends on: 1274959

Updated

10 months ago
Flags: platform-rel?

Updated

10 months ago
platform-rel: --- → ?
Depends on: 1288677
Depends on: 1288681

Updated

9 months ago
Depends on: 1289255, 1289254

Updated

9 months ago
Depends on: 1288683
platform-rel: ? → ---

Updated

8 months ago
See Also: → bug 1293949
Duplicate of this bug: 1293949
Depends on: 1331637
(Reporter)

Updated

a day ago
Assignee: jwatt → nobody
You need to log in before you can comment on or make changes to this bug.