geary/ui/components-web-view.js

189 lines
6.8 KiB
JavaScript
Raw Normal View History

/*
* Copyright 2016 Michael Gratton <mike@vee.net>
*
* This software is licensed under the GNU Lesser General Public License
* (version 2.1 or later). See the COPYING file in this distribution.
*/
/**
* Application logic for Components.WebView and subclasses.
*/
let PageState = function() {
this.init.apply(this, arguments);
};
Re-implement remote image loading management for WebKit2. * src/client/components/client-web-view.vala (ClientWebView): Register for new remoteImageLoadBlocked message from JS. Add new ::remote_image_load_blocked signal to notify when a remote image load was blocked. Add ::allow_remote_image_loading and ::load_remote_images methods to allow th app to manage image loading state. * src/client/conversation-viewer/conversation-email.vala (ConversationEmail): Determine up front whether the message view should load remote images and flag that, rather than passing through the email flag and the contact store. * src/client/conversation-viewer/conversation-message.vala (ConversationMessage): Rmeove contact_store and always_load_remote_images properties and related code, just let the parent email view advise whether remote images should be initially loaded and act accordingly. Look up to ClientWebView signal and methods to handle manual remote image loading management by the user. Remove some obsolete code. * src/client/web-process/web-process-extension.vala (GearyWebExtension): Replace allow_prefix implementation for remote image management with explicit signalling to/from the application via JavaScript. * ui/client-web-view.js: Add a new PageState object, add props and method to implement remote image loading management. * ui/client-web-view-allow-remote-images.js: Monkeypatch to be used when remote images should be loaded by default. * ui/CMakeLists.txt: Include new JS file. * src/client/conversation-viewer/conversation-web-view.vala, src/client/web-process/util-conversation.vala, src/client/web-process/util-webkit.vala: Remove obsolete code.
2016-11-25 16:30:50 +11:00
PageState.prototype = {
init: function() {
this.isLoaded = false;
this.undoEnabled = false;
this.redoEnabled = false;
this.hasSelection = false;
this.lastPreferredHeight = 0;
let state = this;
// Set up an observer to keep track of modifications made to
// the document when editing.
let modifiedId = null;
this.bodyObserver = new MutationObserver(function(records) {
if (modifiedId == null) {
modifiedId = window.setTimeout(function() {
state.documentModified();
state.checkCommandStack();
modifiedId = null;
}, 1000);
}
});
document.addEventListener("DOMContentLoaded", function(e) {
state.loaded();
});
// Coalesce multiple calls to updatePreferredHeight using a
// timeout to avoid the overhead of multiple JS messages sent
// to the app and hence view multiple resizes being queued.
let queueTimeout = null;
let queuePreferredHeightUpdate = function() {
if (queueTimeout != null) {
clearTimeout(queueTimeout);
}
queueTimeout = setTimeout(
function() { state.updatePreferredHeight(); }, 100
);
};
// Queues an update when the complete document is loaded.
//
// Note also that the delay introduced here by this last call
// to queuePreferredHeightUpdate when the complete document is
2019-05-22 20:47:08 +00:00
// loaded seems to be important to get an accurate idea of the
// final document size.
window.addEventListener("load", function(e) {
queuePreferredHeightUpdate();
}, true); // load does not bubble
// Queues updates for any STYLE, IMG and other loaded
// elements, hence handles resizing when the user later
// requests remote images loading.
document.addEventListener("load", function(e) {
queuePreferredHeightUpdate();
}, true); // load does not bubble
// Queues an update if the window changes size, e.g. if the
// user resized the window. Only trigger when the width has
// changed however since the height should only change as the
// body is being loaded.
let width = window.innerWidth;
window.addEventListener("resize", function(e) {
let currentWidth = window.innerWidth;
if (width != currentWidth) {
width = currentWidth;
queuePreferredHeightUpdate();
}
}, false); // load does not bubble
// Queues an update when a transition has completed, e.g. if the
// user resized the window
window.addEventListener("transitionend", function(e) {
queuePreferredHeightUpdate();
}, false); // load does not bubble
},
getPreferredHeight: function() {
// Return the scroll height of the HTML element since the BODY
// may have margin/border/padding and we want to know
// precisely how high the widget needs to be to avoid
// scrolling.
return window.document.documentElement.scrollHeight;
},
getHtml: function() {
return document.body.innerHTML;
},
loaded: function() {
this.isLoaded = true;
2019-05-22 20:47:08 +00:00
// Always fire a preferred height update first so that it will
// be vaguegly correct when notifying of the HTML load
// completing.
this.updatePreferredHeight();
window.webkit.messageHandlers.contentLoaded.postMessage(null);
},
Re-implement remote image loading management for WebKit2. * src/client/components/client-web-view.vala (ClientWebView): Register for new remoteImageLoadBlocked message from JS. Add new ::remote_image_load_blocked signal to notify when a remote image load was blocked. Add ::allow_remote_image_loading and ::load_remote_images methods to allow th app to manage image loading state. * src/client/conversation-viewer/conversation-email.vala (ConversationEmail): Determine up front whether the message view should load remote images and flag that, rather than passing through the email flag and the contact store. * src/client/conversation-viewer/conversation-message.vala (ConversationMessage): Rmeove contact_store and always_load_remote_images properties and related code, just let the parent email view advise whether remote images should be initially loaded and act accordingly. Look up to ClientWebView signal and methods to handle manual remote image loading management by the user. Remove some obsolete code. * src/client/web-process/web-process-extension.vala (GearyWebExtension): Replace allow_prefix implementation for remote image management with explicit signalling to/from the application via JavaScript. * ui/client-web-view.js: Add a new PageState object, add props and method to implement remote image loading management. * ui/client-web-view-allow-remote-images.js: Monkeypatch to be used when remote images should be loaded by default. * ui/CMakeLists.txt: Include new JS file. * src/client/conversation-viewer/conversation-web-view.vala, src/client/web-process/util-conversation.vala, src/client/web-process/util-webkit.vala: Remove obsolete code.
2016-11-25 16:30:50 +11:00
loadRemoteImages: function() {
window._gearyAllowRemoteResourceLoads = true;
let images = document.getElementsByTagName("IMG");
for (let i = 0; i < images.length; i++) {
let img = images.item(i);
let src = img.src;
Re-implement remote image loading management for WebKit2. * src/client/components/client-web-view.vala (ClientWebView): Register for new remoteImageLoadBlocked message from JS. Add new ::remote_image_load_blocked signal to notify when a remote image load was blocked. Add ::allow_remote_image_loading and ::load_remote_images methods to allow th app to manage image loading state. * src/client/conversation-viewer/conversation-email.vala (ConversationEmail): Determine up front whether the message view should load remote images and flag that, rather than passing through the email flag and the contact store. * src/client/conversation-viewer/conversation-message.vala (ConversationMessage): Rmeove contact_store and always_load_remote_images properties and related code, just let the parent email view advise whether remote images should be initially loaded and act accordingly. Look up to ClientWebView signal and methods to handle manual remote image loading management by the user. Remove some obsolete code. * src/client/web-process/web-process-extension.vala (GearyWebExtension): Replace allow_prefix implementation for remote image management with explicit signalling to/from the application via JavaScript. * ui/client-web-view.js: Add a new PageState object, add props and method to implement remote image loading management. * ui/client-web-view-allow-remote-images.js: Monkeypatch to be used when remote images should be loaded by default. * ui/CMakeLists.txt: Include new JS file. * src/client/conversation-viewer/conversation-web-view.vala, src/client/web-process/util-conversation.vala, src/client/web-process/util-webkit.vala: Remove obsolete code.
2016-11-25 16:30:50 +11:00
img.src = "";
img.src = src;
}
},
setEditable: function(enabled) {
if (!enabled) {
this.stopBodyObserver();
}
document.body.contentEditable = enabled;
if (enabled) {
// Enable modification observation only after the document
// has been set editable as WebKit will alter some attrs
this.startBodyObserver();
}
},
startBodyObserver: function() {
let config = {
attributes: true,
childList: true,
characterData: true,
subtree: true
};
this.bodyObserver.observe(document.body, config);
},
stopBodyObserver: function() {
this.bodyObserver.disconnect();
},
Re-implement remote image loading management for WebKit2. * src/client/components/client-web-view.vala (ClientWebView): Register for new remoteImageLoadBlocked message from JS. Add new ::remote_image_load_blocked signal to notify when a remote image load was blocked. Add ::allow_remote_image_loading and ::load_remote_images methods to allow th app to manage image loading state. * src/client/conversation-viewer/conversation-email.vala (ConversationEmail): Determine up front whether the message view should load remote images and flag that, rather than passing through the email flag and the contact store. * src/client/conversation-viewer/conversation-message.vala (ConversationMessage): Rmeove contact_store and always_load_remote_images properties and related code, just let the parent email view advise whether remote images should be initially loaded and act accordingly. Look up to ClientWebView signal and methods to handle manual remote image loading management by the user. Remove some obsolete code. * src/client/web-process/web-process-extension.vala (GearyWebExtension): Replace allow_prefix implementation for remote image management with explicit signalling to/from the application via JavaScript. * ui/client-web-view.js: Add a new PageState object, add props and method to implement remote image loading management. * ui/client-web-view-allow-remote-images.js: Monkeypatch to be used when remote images should be loaded by default. * ui/CMakeLists.txt: Include new JS file. * src/client/conversation-viewer/conversation-web-view.vala, src/client/web-process/util-conversation.vala, src/client/web-process/util-webkit.vala: Remove obsolete code.
2016-11-25 16:30:50 +11:00
remoteImageLoadBlocked: function() {
window.webkit.messageHandlers.remoteImageLoadBlocked.postMessage(null);
},
/**
* Sends "preferredHeightChanged" message if it has changed.
*/
updatePreferredHeight: function(height) {
if (height === undefined) {
height = this.getPreferredHeight();
}
// Don't send the message until after the DOM has been fully
// loaded and processed by any derived classes. Since
// ConversationPageState may collapse any quotes, sending the
// current preferred height before then may send a value that
// is too large, causing the message body view to grow then
// shrink again, leading to visual flicker.
if (this.isLoaded && height > 0 && height != this.lastPreferredHeight) {
this.lastPreferredHeight = height;
window.webkit.messageHandlers.preferredHeightChanged.postMessage(
height
);
}
},
checkCommandStack: function() {
let canUndo = document.queryCommandEnabled("undo");
let canRedo = document.queryCommandEnabled("redo");
if (canUndo != this.undoEnabled || canRedo != this.redoEnabled) {
this.undoEnabled = canUndo;
this.redoEnabled = canRedo;
window.webkit.messageHandlers.commandStackChanged.postMessage(
this.undoEnabled + "," + this.redoEnabled
);
}
},
documentModified: function(element) {
window.webkit.messageHandlers.documentModified.postMessage(null);
},
selectionChanged: function() {
let hasSelection = !window.getSelection().isCollapsed;
if (this.hasSelection != hasSelection) {
this.hasSelection = hasSelection;
window.webkit.messageHandlers.selectionChanged.postMessage(hasSelection);
}
Re-implement remote image loading management for WebKit2. * src/client/components/client-web-view.vala (ClientWebView): Register for new remoteImageLoadBlocked message from JS. Add new ::remote_image_load_blocked signal to notify when a remote image load was blocked. Add ::allow_remote_image_loading and ::load_remote_images methods to allow th app to manage image loading state. * src/client/conversation-viewer/conversation-email.vala (ConversationEmail): Determine up front whether the message view should load remote images and flag that, rather than passing through the email flag and the contact store. * src/client/conversation-viewer/conversation-message.vala (ConversationMessage): Rmeove contact_store and always_load_remote_images properties and related code, just let the parent email view advise whether remote images should be initially loaded and act accordingly. Look up to ClientWebView signal and methods to handle manual remote image loading management by the user. Remove some obsolete code. * src/client/web-process/web-process-extension.vala (GearyWebExtension): Replace allow_prefix implementation for remote image management with explicit signalling to/from the application via JavaScript. * ui/client-web-view.js: Add a new PageState object, add props and method to implement remote image loading management. * ui/client-web-view-allow-remote-images.js: Monkeypatch to be used when remote images should be loaded by default. * ui/CMakeLists.txt: Include new JS file. * src/client/conversation-viewer/conversation-web-view.vala, src/client/web-process/util-conversation.vala, src/client/web-process/util-webkit.vala: Remove obsolete code.
2016-11-25 16:30:50 +11:00
}
};