Samuel Degueldre
6f95be6884
*: auth_password_policy, bus, event, im_livechat, mail, mass_mailing, mrp_subcontracting, point_of_sale, pos_self_order, project, stock, survey, web, web_editor, web_tour, website, website_event, website_forum, website_sale, website_slides, base Historically, the web.assets_common bundle was used to contain assets that were needed by both the frontend and the backend. In practice, this caused a bunch of issues where people would add things in assets common that were not needed by both, and it was also abused as a way to get bootstrap working in unrelated places by only using that bundle's css. Because of this, as a first step, the assets_common stop being used in the frontend, but was left everywhere else. This commit removes the bundle completely, and moves the files that used to be in that bundle in the other bundles that need them, this will allow those bundles to evolve independently going forward. in im_livechat and mail, some of the unneeded legacy code was removed, this allows us to avoind including all of the legacy code from web in the livechat embed bundle and in the dicuss public bundle respectively. closes odoo/odoo#132190 Related: odoo/enterprise#45884 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
68 lines
3.0 KiB
JavaScript
68 lines
3.0 KiB
JavaScript
/** @odoo-module **/
|
|
|
|
import { isMobileOS } from "@web/core/browser/feature_detection";
|
|
|
|
/**
|
|
* Until we have our own implementation of the /web/static/lib/pdfjs/web/viewer.{html,js,css}
|
|
* (currently based on Firefox), this method allows us to hide the buttons that we do not want:
|
|
* * "Open File"
|
|
* * "View Bookmark"
|
|
* * "Print" (Hidden on mobile device like Android, iOS, ...)
|
|
* * "Download" (Hidden on mobile device like Android, iOS, ...)
|
|
*
|
|
* @link https://mozilla.github.io/pdf.js/getting_started/
|
|
*
|
|
* @param {Element} rootElement
|
|
*/
|
|
export function hidePDFJSButtons(rootElement) {
|
|
const cssStyle = document.createElement("style");
|
|
cssStyle.rel = "stylesheet";
|
|
cssStyle.textContent = `button#secondaryOpenFile.secondaryToolbarButton, button#openFile.toolbarButton,
|
|
a#secondaryViewBookmark.secondaryToolbarButton, a#viewBookmark.toolbarButton {
|
|
display: none !important;
|
|
}`;
|
|
if (isMobileOS()) {
|
|
cssStyle.textContent = `${cssStyle.innerHTML}
|
|
button#secondaryDownload.secondaryToolbarButton, button#download.toolbarButton,
|
|
button#secondaryPrint.secondaryToolbarButton, button#print.toolbarButton{
|
|
display: none !important;
|
|
}`;
|
|
}
|
|
const iframe =
|
|
rootElement.tagName === "IFRAME" ? rootElement : rootElement.querySelector("iframe");
|
|
if (iframe) {
|
|
if (!iframe.dataset.hideButtons) {
|
|
iframe.dataset.hideButtons = "true";
|
|
iframe.addEventListener("load", (event) => {
|
|
if (iframe.contentDocument && iframe.contentDocument.head) {
|
|
iframe.contentDocument.head.appendChild(cssStyle);
|
|
}
|
|
});
|
|
}
|
|
} else {
|
|
console.warn("No IFRAME found");
|
|
}
|
|
}
|
|
|
|
/*
|
|
* List of changes made in the library
|
|
* There is no changes to pdf.js in this section, but only a note about changes that has been done in /web/static/lib/pdfjs/.
|
|
*
|
|
* In the module account_invoice_extract, the code need to react to the 'pagerendered' event triggered by
|
|
* pdf.js. However in recent version of pdf.js, event are not visible outside of the library, except if the
|
|
* 'eventBusDispatchToDOM' has been set to true.
|
|
*
|
|
* We tried to set this option from outside of the library but without success, as our pdf viewer is in an iframe.
|
|
* There is no state of the iframe in which we can add an event listener to set the option.
|
|
* pdf.js has an event used to signal when we can set settings, called 'webviewerloaded'.
|
|
* This event is triggered in an EventListener attached to the 'DOMContentLoaded' event.
|
|
* So, to list options we had, we could:
|
|
* a) add an eventListener to the iframe document or window to react to 'webviewerloaded'. This doesn't work as
|
|
* document and windows are not the definitive ones and won't catche the event later.
|
|
* b) add an eventListener to the iframe to react to 'DOMContentLoaded', which doens't work too as our listener will be called
|
|
* after the pdf.js one.
|
|
*
|
|
* Finally the option was choosed to modify the default value of this option directly in pdf.js as no hook worked in the
|
|
* 'account_invoice_extract' module.
|
|
*/
|