| Page 1 of 1 | [ 3 posts ] |
|
Because of the way we use YUI in our products we ship a distribution rather than rely on the hosted versions of the files. We also distribute our own widgets which are built on top of YUI's widgets (enforcing behavior as mandated by our UX team, etc.). A consequence of this is that we include resources like this:
Code: <script src="/yui-2.6/yahoo-dom-event/yahoo-dom-event.js" type="text/javascript"></script> and things get a bit confused because Yeti is running on a different port (e.g. 8088), i.e. yahoo-dom-event.js is being served on port 80, and can't be found relative to port 8088. What is the recommended way of dealing with this? |
|
Yeti v0.1.0 won't be able to handle this out of the box. But, I'd love to help make a future version work for you.
That code snippet is using an absolute path, not a relative one. Yeti is designed to work with paths that would work if you opened your test with the file:// protocol. This includes relative paths and fully-qualified paths that start with http://. A future version of yeti could try to route an undefined route like /yui-2.6 to /projects/your/path/here/yui-2.6. I'm hesitant to implement this, because some paths are reserved by Yeti ("/results", "/tests", "/projects", "/inc", "/dyn") and I'd hate for people to get confused by behavior that doesn't work all of the time. The best solution would be making your tests work with file://, i.e. when opening them with `open test.html`. I apologize for the delay in responding-- I just added this forum's RSS feed to my reader |
|
You could try including a BASE tag in your HEAD.
|
| Page 1 of 1 | [ 3 posts ] |
| You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum |
© 2006-2013 Yahoo! Inc. All rights reserved.
All code on this site is licensed under the BSD License unless stated otherwise.
About This Site · Security Contact Info
Powered by phpBB® Forum Software © phpBB Group