Issue 355 in iui: iui.busy remains true after following non-iui fragments

2 views
Skip to first unread message

i...@googlecode.com

unread,
Sep 9, 2013, 7:22:18 PM9/9/13
to iui-i...@googlegroups.com
Status: New
Owner: ----

New issue 355 by ted.godd...@gmail.com: iui.busy remains true after
following non-iui fragments
http://code.google.com/p/iui/issues/detail?id=355

What steps will reproduce the problem?
1. Use iUI screens
2. Use other technique that makes use of URL #fragment
3. iUI view seen to be null but remains in busy state

What is the expected output? What do you see instead?
Expect view navigation to occur.

What version of the product are you using? On what operating system?
Safari, iOS

Please provide any additional information below.

We are using iUI in conjunction with ICEmobile-SX. It is an external
native app that makes use of the URL #fragment to return data to the web
application (such as a scanned QR code value or a preview image from the
camera. This is currently in development.) I have not tested the following
with general iUI use, but it fixes the incompatibility with ICEmobile-SX.
If the "intended view" is null (such as a #fragment that does not refer to
a view within the page) then the attempted view change should be aborted.

nodeId = view;
node = $(nodeId);
}
- if (!node) log("gotoView: node is null");
+ if (!node) {
+ log("gotoView: node is null");
+ return false;
+ }
if (!iui.busy)
{
iui.busy = true;


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages