hi Steve,

fill issue for that (either as issue/bug or enhancement):
http://code.google.com/p/iui/issues/list
and attach your code as patch for use or later inclusion in iui
sources,
see also
http://groups.google.com/group/iui-issues

regards,
peter

On Jan 29, 7:59 pm, "Steve Finkelstein" <[EMAIL PROTECTED]> wrote:
> I suppose this issue was half my fault, half iUI's imo.  The problem
> was my container div in the containing file being pulled in with XHR,
> aka foo.php in this example, did not have an id attribute. I haven't
> had time to look through iUI's source, but there's probably something
> there which checks if an id on the containing div is set -- if it
> isn't it will auto create one for you sequentially with __x+1__
> sequentially.
>
> It probably makes sense to remove the wrapper div, because if you call
> the same file twice, it replicates the entire DOM portion .. thus
> giving me semantically incorrect syntax with multiple IDs. That was
> causing lots of my stuff to break.
>
> I will be patching my personal copy of iUI. Is there a place I can
> share the code to save someone else the hassle?
>
> On 1/28/08, Steve Finkelstein <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
>
> > I'm experiencing what seems to be a really ugly bug in iUI. It's
> > either that, or it's my application. Everytime I click on one of my
> > list items to bring in a new list, I get the following inserting into
> > my DOM.
>
> > <div id="__1__" style="left: 100%;">
>
> > and when I click the back button and click on the same list again,
> > another one gets added:
>
> > <div id="__2__" style="left: 100%;">
>
> > and the one that's selected:
>
> > <div id="__4__" style="left: 0%;" selected="true">
>
> > This is all the same <li> that I keep clicking on that looks something like:
>
> >         <li class="foo"><a href="/ajax/foo.php">Foo</a></li>
>
> > The problem with the above is, it replicates my entire foo.php into
> > these container divs, and then any javascript I have that's using code
> > such as getElementById gets completely broken since you're only
> > supposed to have one id="" per page. I can write some logic to remove
> > those divs, but I'd rather know
>
> > a) How they're happening
> > b) Is it my code that's wrong?
> > c) How to prevent it or submit a fix
>
> > Has anyone else noticed this oddity?
>
> > /sf
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to