Previously, I was attempting to help terryscc with an issue related to iframe content not rendering properly in Canvas and the Canvas mobile app. To see our initial discourse, checkout Iframe links on mobile app. From these communications, I gathered information related to the issue, and I think that I have devised a solution for it. Before I get too far into it however, I wanted to first details what we are attempting to do here and why we are attempting to do it.
Figure 1. We are attempting to upload a .html file and then embed it into an iframe on a page.
Rather than creating a simply link or anchor tag to the file, we are attempting to embed it in a page of the Canvas course. Why would we want to do this? Well there are a couple of advantages that come with embedding an HTML file including:
Pros to embedding an html document in an iframe
You have control over they layout of all of the elements of the file, giving you a greater level of how they are laid out with regards to one another.
You can add a <style> tag to the <head> of your html document, giving you a wider range of options with regards to how the elements look, feel, and even behave on the page. The styles options that are available via this method are wider than inline styles.
While this may seem like a favorable option, before we begin, I must point out that there can be some unforeseen complications that arise when attempting to put any content into an iframe.
Cons & Complications to embedding an html document in an iframe
Any content that originates from a url that begins with http instead of https will not be allowed to render in your Canvas course. This is a security protection measure.
While the iframe will render the content, depending upon the width of the origin page, the content may render in a way that requires vertical scrolling, horizontal scrolling, or both.
If you don't have access to the origin file (.html) for the iframe, then any links clicked in the iframe will lead to their designated pages, but those pages will render in the iframe itself. This can lead to some very weird/unexpected/non-ideal renderings of pages, from your Canvas course or otherwise, in the iframe itself.
If the file referenced in the iframe originates from your Canvas course, it will render in a weird sort of way (see item 3) unless you acquire the path to it correctly.
I have created a simple solution to demonstrate the possibilities when the four complications are addressed appropriately. If you are more comfortable with HTML and CSS, then feel to take the information here and run with it to your heart's content. If you aren't so familiar with HTML and CSS, never fear. I will provide you with all of the materials so that you can at least play around with this and maybe learn a thing or two.
If you would like to watch a video of me talking through this, it is directly below. If you instead prefer to follow along on the page, then simply skip the video for now.
What We Will Need
A .html document. If you would like to borrow one from me, you can find it here.
A text editor so that you can open the .html document and modify the code. I prefer Sublime, but choose the one that you are comfortable with.
A new page in a Canvas to which we will add the iframe.
A basic understanding of the HTML editor in Canvas. If you have embedded YouTube iframes using it, then you are good.
A little bit of free time and patience.
Getting the .html File Ready for Upload
Before we upload it, there are a couple of things that we want to make sure of when it comes to our .html file. I have detailed them below:
Open the .html file in your text editor.
Make sure that you have added urls for the anchor tags <a> in either your .html file or the one that I provided you with. If you need to know where to put the url, locate the three anchor tags that I have added on lines 134-136 and paste you links over where it reads yourLinkGoesHere. Make sure your link is between the two quotes.
<aclass="button is-1"href="yourLinkGoesHere">Go to Page</a> <aclass="button is-2"href="yourLinkGoesHere">Go to Syllabus</a> <aclass="button is-3"href="yourLinkGoesHere">Go to Modules</a>
Locate the closing head tag in your .html file. If you are using my example, it should be around line 131, and it will look like this:
Place your cursor right before the < of the </head> tag and hit return/enter to add a blank line. In that blank line, add the following code:
Note: if the code is already there, you may skip step 4.
Go to the Files section of your Canvas course and upload the .html file.
Before we proceed, I want to talk about the importance of step 4. When we go to embed our .html document into our Canvas page, what we will really be doing is placing our document inside of an <iframe> element which is, itself, inside of another .html document. Essentially we are performing the Inception of web design. Essentially, when the page is fully loaded the code is going to look something like this:
<!DOCTYPE html> <html> <head> <!-- Canvas' HEAD content --> </head> <body> <!-- Canvas' BODY content, including our ... --> <iframe> #document <!DOCTYPE html><!-- this is actually the start of our .html file --> <html> <head> <!-- The HEAD content from our .html file --> </head> <body> <!-- The BODY content, including the buttons, from our .html --> </body> </html> </iframe> </body> </html>
Why does this matter?
Well, the problem that can arise is that if the iframe is rendering a separate html document from the Canvas one that the browser you are using is rendering, then any links that exist, and are clicked, within the iframe html document will only open new tabs and windows within the iframe's document. To correct this behavior, we introduce the <base> parameter in the head. This sets a base behavior for all clicked links originating from our .html file. The target="_parent" piece of the base code essentially says, "when a link is clicked, the base behavior is to open that link in the parent window." Had we not done this, we would expect to have aberrant behavior on link clicks, where windows would load inside of windows, and you would most likely get something that looks like this:
Figure 2. When a page in your Canvas course becomes Inception.
Notice how both the global nav and the course nav are still rendered in my iframe. That is not the behavior that I want, and this is the behavior that the <base> parameter corrects.
Creating the <iframe>
First, we need to get the link to our .html file, so click on Files in the Canvas course menu.
Locate the .html file and click on it. This should open up a preview window.
Make sure the developer console is enabled in your browser, right click on any are of the preview window where your file is currently rendered and choose Inspect Element from the list of options. Use my Verifying Mobile Friendly Web Content tutorial if you have forgotten how to access the developer console.
In the source code that appears, you should be able to locate an <iframe> that has the following parameters:
By setting the width to 100%, the iframe will behave in a responsive manner, always growing or shrinking to fill whatever space is actually allotted to it. You may need to experiment with the height, depending upon how tall your container will be. If you have a lot of buttons and text, you will need to increase the height parameter until everything is visible (you will see the cutoff if you didn't make your iframe tall enough). The overflow parameter is a personal preference on my part. I choose to make my iframes tall enough so that all of their content is visible with needing to scroll within them. If you don't set your overflow, you may find that you, or your students, have to scroll either horizontally or vertically within the iframe to see all of its content. This will involve scrolling ON TOP of the scrolling that is already happening in the main window as a result of Canvas' html.
Finally, modify the iframe by adding scrolling="no" just before the > of the opening <iframe> tag. Your finalized code should look something like this:
This scrolling parameter is a fallback for the overflow style that we added in step 9, and ensures that there is no scrolling allowed in the iframe. Again, this is a personal preference, but you are welcome to not utilize this if you feel it is unnecessary.
Save the page.
You should be good to go! Check your page on both the desktop and mobile versions of Canvas, and click all of your links to ensure that they are opened in the main browser window.
As you can see, this opens the door for instructional designers and instructors to build out content that is not based solely on inline css styles or the stylesheets provided by Instructure. I am excited to see what you all choose to do with this information, and as always, please feel free to contact me if you have questions or concerns about getting this up and running.
I'm a Texan, born and raised, though I spent all of my years in college and graduate school in the northeast. I attended MIT, where I obtained a BS in Biology, and then received a MS in Cell and Molecular Biology from UPenn.
After leaving the northeast, I moved back to the Dallas area to be a bit closer to my family, and landed a job at Collin College. Initially, I was lab staff, and prepped and taught biology labs. I recognized early on in during my tenure that students across our campuses needed a consistent lab experience.
To address this, I set to work filming video lectures and reviews and posting them to YouTube. The problem then was disseminating the information to students, and not just those in my classes. To develop a central repository of these videos, and other content, I taught myself to code in HTML and CSS.
Over the last eight years, I have worked to better my understanding of web and graphic design. Along the way, I have picked up additional skills that have helped me to achieve this.
Now, as I work on new strategic initiatives and projects, I do so with very distinct objectives: create functional, student facing assets, AND, ensure that those assets are clean, concise and well designed.