React Error: Target Container is not a DOM Element

I figured it out! After reading this blog post I realized that the placement of this line: was wrong. That line needs to be the last line in the <body> section, right before the </body> tag. Moving the line down solves the problem. My explanation for this is that react was looking for the id in between the <head> tags, instead of in … Read more

Possible to extend types in Typescript?

The keyword extends can be used for interfaces and classes only. If you just want to declare a type that has additional properties, you can use intersection type: UPDATE for TypeScript 2.2, it’s now possible to have an interface that extends object-like type, if the type satisfies some restrictions: It does not work the other way round – UserEvent must be declared … Read more

SecurityError: Blocked a frame with origin from accessing a cross-origin frame

Same-origin policy You can’t access an <iframe> with different origin using JavaScript, it would be a huge security flaw if you could do it. For the same-origin policy browsers block scripts trying to access a frame with a different origin. Origin is considered different if at least one of the following parts of the address isn’t maintained: protocol://hostname:port/… Protocol, hostname and … Read more

XML Parsing Error: no root element found Location in Console FF

Check this link for more information Based on my research, the error message is only generated by FireFox when the render page is blank in Internet. For some reason, .NET generates a response type of “application/xml” when it creates an empty page. Firefox parses the file as XML and finding no root element, spits out the error … Read more