Closed ghost closed 11 years ago
Hi, in a super-simple test it seems to work, I think I'll need a proper example.
A couple of questions:
Cheers, Andrea
Hi Andrea,
to answer your questions:
However, non of these caused my issue, but simply a duplicated id on an <a>
tag.
Now, the second dialog opens from the first one. The only issue I couldn't fix yet is that the second dialog's ui doesn't enhance even after calling
$(backboneView.el).trigger("create");
However, routing works as expected.
To wrap this up, there was nothing wrong with routing. However, chaining dialogs seem to work either only with the standard implementation or programmatically. Mixing both approaches causes the second dialog not being enhanced properly.
Uhm, I thought I saw everything that jQM could do to drive a developer crazy, I'm glad I missed this one...
I can't seem to be able to reproduce this strange behavior, it would be funny to see a test case (and maybe report the issue to jQM guys). It's quite strange because jQM should enhance the page when it's first visited, regardless of the source of the page change.
I open a dialog like so:
which works as expected. When opening another dialog from the first one in the click event handler like so:
it seem to break the router, I can't go anywhere from here.
Can't see any exceptions or errors thrown in Chrome dev tools.