Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#each not working #507

Closed
yeldarby opened this issue May 2, 2013 · 8 comments
Closed

#each not working #507

yeldarby opened this issue May 2, 2013 · 8 comments

Comments

@yeldarby
Copy link

yeldarby commented May 2, 2013

I posted this topic over at stackoverflow. After messing with it for the better part of the day I'm convinced the bug is with handlebars rather than my integration with it.

It seems to be isolated only to within a UIWebView on iOS; my JS Fiddle works in Native Safari (and on the desktop) but the same code fails when trying to run inside my UIWebView.

I posted Handlebars debug output in the comments from RC1 (where I could get it to trigger an error) and 1.0.10 (where it simply didn't output the correct thing).

Some screenshots are also included in the post. I'd be happy to do any other debugging that anybody would like but I'm not familiar enough with the handlebars codebase to even suggest what could be going on.

If you look at the logs on the last pastebin I posted on SO there are some (3) where it works and some (~14) where it doesn't all on the same page in succession. No commonalities that I can see between the ones that work and the ones that don't. Do a search for "star unstarred" vs "star " and it should help you tell the difference.

http://stackoverflow.com/questions/16343321/handlebars-js-each-not-working

Also as a sidenote: another weird thing is that if I connect Safari to remotely debug it magically starts working on all cases. No idea why this is but maybe someone else has some insights here.

@kpdecker
Copy link
Collaborator

Please try rc3 or the code currently in master. This sounds awfully similar to #440 (comment)

@yeldarby
Copy link
Author

This bug is still present in both RC3 and master (it performs incorrectly without throwing an error; see screenshot on stack overflow).

RC1 was only mentioned because not only did it fail even worse but it also threw an error.

@kpdecker kpdecker reopened this May 10, 2013
@kpdecker
Copy link
Collaborator

Is there any sort of bug reduction that you can create that exhibits the problem?

I've reached out to trigger.io team to see what their recommendations are for debugging here are as well. Right now I don't have access to an account so I'm slightly hindered in testing this in that environment :/

@yeldarby
Copy link
Author

Wow didn't realize they had completely dropped their free account. Do you have an iOS device? I could create a test case in an ad-hoc .ipa and send via testflight.

@kpdecker
Copy link
Collaborator

I do.

@yeldarby
Copy link
Author

Ok let me pull something together. I will follow up off-list.

@yeldarby
Copy link
Author

I can no longer reproduce this. It appears to be working now.

@kpdecker
Copy link
Collaborator

OK great. Feel free to ping if it happens again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants