Faster Web is Here: HTTP/2

HTTP/2 standard has been finalized, paving the way for a faster Web


HTTP/2 will enable faster page loads, it is binary instead of textual (more efficient and less error-prone), it is fully multiplexed (to improve network performance), uses header compression and ‘Server Push’ (to reduce overhead).

Google has announced its plans to adopt HTTP/2 for Chrome and we also know that Microsoft’s Project Spartan has built-in support for the new standard.

If you are a web developer you can already test HTTP/2 in Firefox and Chrome with a few downloadable test servers. More information on that can be found here.


Google Chrome issues with D2L

Per MnSCU System Office:

Update on D2L issues in Chrome browser:

Chrome 32 has resolved the issue with miniature-sized frames inside some D2L tools.

Chrome 32 has introduced a new issue with D2L at screens that bring up a separate window with a list of options, such as “Insert Quicklinks”. After a lengthy wait time, a blank window displays in the pop-up and does not populate with information.

D2L has identified this as a browser bug that Google Chrome intends to fix in version 33, but preliminary testing of the current beta version of Chrome 33 shows that the issue still exists.

D2L recommends using a different browser until Google Chrome has a release that resolves this issue.

Further questions and inquiries? Please address to:
Follow us on Twitter: @scsutechinstruc #d2l
Follow the IMS blog:

Google Chrome issues with D2L discussion: Scroll window is small and have to scroll down to see all the posts

Customer was having problems with D2L in Google Chrome. Client was not able to see discussion posts in D2L. However, it seems to be fine in Internet Explorer or Mozilla Firefox.

Scroll window is small and have to scroll down to see all the posts


This is a known issue with Chrome.

To display the full discussion screen, simply grab the vertical frame divider (click and drag it) and move it a little.  The rest of the screen will sort itself out.

Here’s a short screen recording about this issue which shows the workarounds in action: