d804881151
pdfjschildbootstrap.js will always be run, but pdfjschildbootstrap-enabled.js will only be run if PdfJs.enabled is true. This will let us avoid some work in the child process in the next patch. This will need to be landed in the mozilla-central repository at the same time as a change to nsBrowserGlue.js. See bug 1352218.
28 lines
954 B
JavaScript
28 lines
954 B
JavaScript
/* Copyright 2014 Mozilla Foundation
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
/* globals Components, PdfjsContentUtils */
|
|
|
|
"use strict";
|
|
|
|
/*
|
|
* pdfjschildbootstrap.js loads into the content process to take care of
|
|
* initializing our built-in version of pdfjs when running remote.
|
|
*/
|
|
|
|
Components.utils.import("resource://pdf.js/PdfjsContentUtils.jsm");
|
|
|
|
// init content utils shim pdfjs will use to access privileged apis.
|
|
PdfjsContentUtils.init();
|