Ext Js Pathfinder progress report #5

Just a quick update. I solved problems with failing tests after switching to my own example Ext JS page. Apparently, PhantomJS doesn’t like protocol mismatch – I served my page using HTTP, but Ext JS assets were served using Sencha’s CDN with HTTPS.

<link rel="stylesheet" media="screen" href="https://cdn.sencha.com/ext/gpl/4.2.1/packages/ext-theme-classic/build/resources/ext-theme-classic-all.css">
<script src="https://cdn.sencha.com/ext/gpl/4.2.1/ext-all.js"></script>

Removing protocol part from links and letting browser adjust it to page’s url worked like a charm:

<link rel="stylesheet" media="screen" href="//cdn.sencha.com/ext/gpl/4.2.1/packages/ext-theme-classic/build/resources/ext-theme-classic-all.css">
<script src="//cdn.sencha.com/ext/gpl/4.2.1/ext-all.js"></script>

 

0

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.