music xray is in the process of a major overhaul to both our backend and frontend technologies. One move we decided to make was to start using webcomponents. As you may know, web components is not fully supported on every browser. That’s where webcomponents.js comes in. Webcomponents.js attempts to polyfill old browsers until they implement the web components specification.

Everything seemed to be going well until we included the facebook sdk on the page. Just placing these two libraries on the page leads to following error using Internet Explorer 11.

SCRIPT5022: InvalidCharacterError
File: webcomponents.js, Line: 3940, Column: 9

The error seemed cyptic and when you click on it you are taken to a function in the webcomponents library. After a ton of digging I finally figured out why. Webcomponents.js overwrites the document.createElement function in it’s effort to polyfill for old browsers. Facebook on the other hand, assumes that you are on the standard document.createElement function. This assumption means that facebook blows up in the presence of webcomponents.js

The answer that was given by the folks over at webcomponents.js was that facebook is calling old code and they should fix it. Well unfortunately in the meantime I need the site to actually work, so I put on my hacker hat and monkey patched document.creatElement to handle the junky call by the facebook sdk.

If you look at the debug version of the facebook sdk you will see the following javascript code about a quarter of the way down to page.

if (hasNamePropertyBug()) {
  frame = document.createElement('<iframe name="' + name + '"/>');
} else {
  frame = document.createElement("iframe"); = name;

The problem with the code comes from trying to create the iframe element using an html tag literal. With a proper version of createElement, this operation is no longer supported, thus the error. To fix this issue, I load the following code immediately following webcomponents.js

  var old_function = document.createElement;
  document.createElement = function(argument){
    var matcher = /^<iframe/g;
      var dummy =,'div');
      dummy.innerHTML = argument;
      var retel = dummy.querySelector('iframe'); =;
      return retel;
      return old_function.apply(document,arguments);

Basically we wrap the document.createElement function calling the existing version under normal circumstances and our custom code to compensate for facebook’s shitty code when needed. Notice how we make a dummy element and set the innerHTML. This is done so that we don’t have to acutally try and parse html code with regular expressions, which can be difficult, we then find the element we are looking for and return it.

I understand that this code is a bit ugly, but desperate times call for desperate measures. Please feel free to comment if you find this solution helpful. I know that having this article available would have saved me quite a bit of time.