1334288 - Some devtools tests read files from the profile from the content process

Status: RESOLVED DUPLICATE of bug 1332522

(Core :: Security: Process Sandboxing, defect)

Description

[Haik Aftandilian [:haik]]

The following tests copy a file to the profile directory and then attempt to read it from the editor running in the content process.

  devtools/client/styleeditor/test/browser_styleeditor_filesave.js
  devtools/client/styleeditor/test/browser_styleeditor_import.js
  devtools/client/styleeditor/test/browser_styleeditor_inline_friendly_names.js
  devtools/client/styleeditor/test/browser_styleeditor_sourcemap_watching.js

We'll soon be removing filesystem read privileges from the content sandbox which will include reading from the profile dir.

On Mac, reading from the base of profile dir is already prevented on Nightly, but, due to bug 1333681, that restriction didn't work for automated tests.

Comment 1

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

If these tests are specifically meant to simulate the user interacting with content loaded from a file:/// URIs, maybe they should be using a file content process?

Comment 2

[Haik Aftandilian [:haik]]

(In reply to Jed Davis [:jld] {⏰UTC-7} from comment #1)
> If these tests are specifically meant to simulate the user interacting with
> content loaded from a file:/// URIs, maybe they should be using a file
> content process?

It turns out they are being loaded in a file content process, but the loads were failing due to bug 1332522. As long as the file content process is enabled, these tests shouldn't fail due to reading from the profile dir.