Closed
Bug 1345807
Opened 8 years ago
Closed 8 years ago
View Page Source doesn't work on data URI loaded in file content process.
Categories
(Core :: Security: Process Sandboxing, defect)
Core
Security: Process Sandboxing
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: bobowen, Assigned: bobowen)
References
Details
(Whiteboard: sbwc2, sbmc2, sblc3)
Attachments
(2 files)
1.64 KB,
patch
|
Gijs
:
review+
|
Details | Diff | Splinter Review |
3.35 KB,
patch
|
Gijs
:
review+
|
Details | Diff | Splinter Review |
I noticed this while testing bug 1343184.
This isn't necessarily just data URIs, but any URI type that is allowed to load in more that one remoteType, that you can view-source on.
At the moment it picks up the default remoteType, not the one for browser which you are viewing the source of.
I have patches.
Assignee | ||
Comment 1•8 years ago
|
||
Try push with the fix from bug 1343184 included (I've fixed the lint issues locally):
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6c4c17a736362f90ea8287fb6ed43e4b9e553d0d
Assignee | ||
Comment 2•8 years ago
|
||
Attachment #8845398 -
Flags: review?(gijskruitbosch+bugs)
Assignee | ||
Comment 3•8 years ago
|
||
Attachment #8845399 -
Flags: review?(gijskruitbosch+bugs)
Updated•8 years ago
|
Attachment #8845398 -
Flags: review?(gijskruitbosch+bugs) → review+
Comment 4•8 years ago
|
||
Comment on attachment 8845399 [details] [diff] [review]
Part 2: Check that we can view-source on data URI loaded in file content process
Review of attachment 8845399 [details] [diff] [review]:
-----------------------------------------------------------------
Please put the new test in the 'tabs' directory instead of in general/ .
::: browser/base/content/test/general/browser_viewsource_of_data_URI_in_file_process.js
@@ +13,5 @@
> + const uriString = Services.io.newFileURI(dir).spec;
> + let fileTab = yield BrowserTestUtils.openNewForegroundTab(gBrowser, uriString);
> + registerCleanupFunction(function* () {
> + yield BrowserTestUtils.removeTab(fileTab);
> + });
Instead of this, you could do:
yield BrowserTestUtils.withNewTab(uriString, function*(fileBrowser) {
// rest of test in here.
});
Attachment #8845399 -
Flags: review?(gijskruitbosch+bugs) → review+
Assignee | ||
Comment 5•8 years ago
|
||
Thanks for the reviews.
(In reply to :Gijs from comment #4)
> Comment on attachment 8845399 [details] [diff] [review]
> Part 2: Check that we can view-source on data URI loaded in file content
> process
> Please put the new test in the 'tabs' directory instead of in general/ .
Moved locally.
> > + let fileTab = yield BrowserTestUtils.openNewForegroundTab(gBrowser, uriString);
> > + registerCleanupFunction(function* () {
> > + yield BrowserTestUtils.removeTab(fileTab);
> > + });
>
> Instead of this, you could do:
>
> yield BrowserTestUtils.withNewTab(uriString, function*(fileBrowser) {
> // rest of test in here.
> });
Nice.
Pushed by bobowencode@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6ac37612bb04
Part 1: When viewing source of existing browser always use its remoteType. r=Gijs
https://hg.mozilla.org/integration/mozilla-inbound/rev/a89a71a9bb73
Part 2: Check that we can view-source on data URI loaded in file content process. r=Gijs
Comment 7•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6ac37612bb04
https://hg.mozilla.org/mozilla-central/rev/a89a71a9bb73
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•