Env.js and ExtJS causes uncaught JavaScript runtime exception: TypeError: Cannot read property "0.0" from null
Reported by LindsayK | September 25th, 2009 @ 07:17 PM | in 1.2.x
Context
I'm attempting to test our client code built with Ext JS V3.0.0 within Rhino using Env.js.
Problem
When ExtJS V3.0.0 attempts to set the following flag on its global Ext object:
isSecure = /^https/i.test(window.location.protocol); (Ext.js, V3.0, line 88)
this exception is thrown:
uncaught JavaScript runtime exception: TypeError: Cannot read property "0.0" from null
Workaround Hack
I modified Ext.js, changing line 88 to:
isSecure = false;
just to move past that assignment for the purpose of our tests.
Comments and changes to this ticket
-
Steven Parkes October 16th, 2009 @ 05:39 AM
I have a patch for this as part of working to integrate qunit which has a similar issue, so it should be in at some point.
-
Thatcher March 2nd, 2010 @ 07:50 AM
- Assigned user set to “Thatcher”
- State changed from “new” to “resolved”
- Tag set to “location, location.port”
- Milestone set to “1.2.x”
this should be fixed in 1.2.x, see test/specs/xhr/spec.js
We run through all the location attributes in our unit tests now.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
a javascript browser environment
LindsayK
Thatcher