When I click on the blue button take me to latest Gmail, the page keeps loading and it gives no response. When I click to use HTML Gmail, it goes to the HTML view. I'm very uncomfortable reading emails in HTML view. How can I set it to standard view?
Related
We have a web admin panel in which the agents can see conversations with customers.
Those conversations are the result of importing normal emails thru an IMAP connection. We grab the "untouched" mailbox files and we store them in a database. Then we post-process the files to index by "from", "to", "date" and so on and so forth.
Up to here, okey. We can seek all the emails involved with a client and render them at will.
Then when the agent looks for a customer in the web admin panel and opens it, the full email conversation appears. And we display the HTML version of the email within an iframe (or the text version if the html version is not there). 90% of the customers send HTML.
What happens? Upon the agent opening the email in our web, the iframe loads the "full html" and renders it. This makes "remote loading" (images, sounds, styles if so, and whatever) to be downloaded. This allows customers to "track" if we opened the email by appending tracking id's to the assets (typical http://track.example.com/image.jpg?id=123456789)
I've tried the "sandbox" attribute of the iframe html tag with no luck (it still downloads the images).
Question
How can I programmatically tell the iframe to not load ANY remote content, and just render the initial HTML without any remote call?
Mozilla's iframe documentation listing all available attributes for the is here: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe
If you look at "sandbox" there is no restriction specific to image or other includes, just restrictions on things like running JavaScript. There are no other attributes that would restrict images and includes.
To solve the problem of images and includes in your HTML you will need to filter the HTML either at the server before sending it or in the client after it arrives.
Server:
Before storing it into the database.
In the code that retrieves the HTML and returns it to the iframe.
Client:
Use AJAX to fill the iframe with the HTML, with code that filters a
response. With this approach you could also use a div instead of an
iframe if that works better for your layout.
If all of your users will use Chrome or Firefox, you could look at writing a browser extension
I am unable to understand how forms work in shopware. I need to update the contact page with my own style but when I add content into the contact page cannot see that content on page when I browse it.
Could you please let me know how to create a page and what need to be done to add a form to that page?
You are aware that the contact form is handled via configuration that can be done in the shopware backend's content > form section? there you will find a list of existing forms that can be modified by clicking the pen icon. A window will open where you can configure the forms name, the recipient email address, subject, email template as well as the form html content that will be shown in the frontend and the message that appears after submitting the form.
If you intend to change the layout (html and/or css) of the forms you need to override the forms template files:
frontend/forms/elements.tpl
frontend/forms/header.tpl
frontend/forms/index.tpl
Kind regards!
I'm making a chrome extension which displays desktop notifications on particular events. I am receiving and displaying the desktop notifications just fine, but the problem comes when I try to put attribute tags into notification. Instead of being the text as tags to be appended to the notififcation's DOM, Chrome seems to just interpret them as plaintext, resulting in the content of the notification being just html source code.
Is there any way that I can have the body of my messages be appended as HTML instead of just text or am I just out of luck?
It used to be possible, but now it's not. But you could use a "Rich Notification" and put the link on a button. See https://stackoverflow.com/a/13328513/488287 for details.
How do I open a document in XPages mobile controls from a URL?
My application notifies users about pending review using an embedded URL link in an email. The requirement is to open the document in mobile controls (SinglePage/App Page). As of now I get a grey page on ipad when the link is clicked from the email.
However I am able to edit the same document using a button and <moveTo> tag. The following is a sample URL when loaded to a browser renders a grey page.
http://175.x.y.z/db.nsf/MN.xsp#newRequest&docId=123761231653&action=openDocument
The #newRequest part of the URL needs to be moved to the END of the url string. Nothing after the # symbol in a URL is transfered to the server so the server never gets the docId or action parameters.
The XPages Mobile Controls provide an easy way to mobilize Notes/Domino data. However, if you have say 3 different views that help point a user to a specific record, the "Back" button you add to your appPage that allows users to view/edit the document can only be pointed back to a specific appPage. What's the best way to create a programmable Back button taking into account the view that the user came in via.
The back button on a mobile page can be computed dynamically just like any other XPage property.
Try this for example where you can set the scope to a mobile page you've navigated from to the current mobile page.
<xp:this.moveTo>
<![CDATA[#{javascript:var from = sessionScope.get(“from”); return
from;
}]]>
</xp:this.moveTo>
This is the same technique that is used in the Discussion XL and TeamRoom XL templates for their mobile apps.
To set the scope use the rendered property in the heading control for each 'view' mobile page so every time these pages are loaded or swapped to the scoped variable is set. Try the following link to get the full demo markup from OpenNTF XSnippets
computed back button demo markup on XSnippets