jQuery Forum

This fails to append anything because 'newElement' was created under window.document rather than xmlDocument. I thought I had found a way around this by writing a plugin which would import (via .importNode()) elements I want to append to a document.

Example of plugin at work: http://jsfiddle.net/6dBr4/10/

Unfortunately, .importNode() (and it's sister, .adoptNode()) drop the element name to lower case, causing the 'newElement' I created to become 'newelement' in xmlDocument. I could work around this if it were limited to the client side, but I have to ship this XML back to the server where the format is expected to have camel cased tags. (Camel casing tags is NOT my preference, but it is what it is and there are a TON of existing documents on this server in this format, and lots of existing server code expecting it).

I have gotten around it for now by dropping to regular DOM manipulation methodologies and creating the element a-la xmlDocument.createElement(), but I would MUCH rather stick to the jQuery way of doing things.

So can I use jQuery to create an element in a context other than window.document?

Thanks,

Jim

We're using Malsup's form plugin v2.82 and jQuery core 1.6.2. We're having issues in IE7 where, on a form with file upload, form fields are being dropped before the form is submitted to the server.

We tracked it down to the `fileUpload` function, specifically line 196 where each field in the form data has `.attr('disabled',false)` run against it.  If we change this to `.prop('disabled',false)` it all works fine.

I don't see a clearly marked place to submit bug reports for the form plugin, and wanted to verify that others see this as well, so I am asking here first...

Anyone see this? Should I report on https://github.com/malsup/form/issues or somewhere else?

Thanks,

Jim

I am wracking my brain trying to figure this out and am not getting anywhere.  I've Googled, Binged, IRCed, searched the forums and bug reports, debugged and attempt to reproduce with no effect...

We have a Drag and Drop interaction on a page which is set up like this: http://jsfiddle.net/JAAulde/hgzvk/2/

In our system, when using the page with the DnD in IE7 (only in IE7--no other browser, not even IE8 in 7 compat mode) the first drag of any particular draggable is fine, but any subsequent drag causes IE to crash.  We traced it all the way down through the creation of the clone helper and into the call to removeAttr() which is made against the clone for stripping off the ID. Inside of removeAttr(), the check for `jQuery.support.getSetAttribute` comes up false, so jQuery attempts to clear the attribute and then retrieve it from the DOM to pass it to `elem.removeAttributeNode()`.  That call to `elem.removeAttributeNode` is where IE crashes.

As I said, I cannot reproduce it, so I understand there is limited help that can be offered. For the same reason, I am quite hesitant to open a bug.

I just wonder if anyone has ever seen anything like it or has any troubleshooting tips for me.

Thanks,

Jim

I wrote a javascript cookies library back in Nov of 2005 and released it as open source. I've maintained it over the years and added jQuery bindings to it a couple of years ago. While the cookie support works perfectly without jQuery, the bindings let you connect HTML elements to cookies and vice/versa. For example, a form input's value can be stored to cookie by `$( 'input#someInput' ).cookify();` or the input can be filled from cookie by `$( 'input#someInput' ).cookieFill();` This all worked fine until I started getting bugs reported for radio and checkbox elements. I had completely neglected the fact that they act quite unique to each other and other input elements--so the library is VERY limited in its ability to handle those. I would reeeeeally like to straighten that out, but my time is limited and every time I do sit down to think it out I get wrapped around the axel and give up again.

Specifically, I need to figure out how to handle the fact that checkboxes can represent an array of values, and radios can act as mutually exclusive to other radios. I need these cases to be handled correctly even when only one of the elements is encountered by the plugin.

The library can be found at http://code.google.com/p/cookies/ .  The whole thing is in that project--reported issues, source code in SVN, documentation, etc, etc. Anyone interested in working on it should have a firm grasp of jQuery and cookies and the intricacies of radio and checkbox interaction. You should read the docs on this library and play with it in the test suite (uses the Firebug plugin, FireUnit). Ask questions here too--i know I haven't given all possible info.

You'll also need a Google Code account, which, upon my acceptance of your solution, will be granted commit access and co-ownership of the project.

If anyone has any ideas for how to handle this but doesn't want to be part of the project, please feel free to make suggestions here.

Thanks all!

Jim A.

Thanks a lot,

Jim