I'm building a grid component as a UI Widget. What I'm tending to do is store selected rows as jQuery objects in widget property array. Is it a potentially bad practice?
When resetting a selecton on the whole grid I basically do a - arr = []. Is it enough to free up the memory occupied by it?
I've got custom made widget, which is derived from UI Dialog (nothing special), some additional logic on header and footer. Now I try to "shake" it in specific cases with $.effect("shake") and it is does as expected, but when the effect ends UI Dialog is destroyed. Is there any way to prevent this?
I'm using animate with some easing to move an element from out of the viewport into the view (on page load), but people notice it being jerky. I notice it sometimes too. Is it a known problem, or I'm doing something wrong? Are there any precautions that one must take to avoid these?
In my case UI Dialog fails to create a dialog from a node that contains <script> tag. That node may or may not contain <script> tag, it depends on apps logic. Is it meant to work in general?
The most illustrative case would be creating a dialog from a third party form, which may contain additional logic passed from remote server through a hybrid local/remote javascript (like Aweber does for example).
We're developing a WordPress plugin, that has jQuery UI widget, which inherits from UI Dialog.
In WordPress, in order to avoid multiple instances of same js libraries on one page, there is implemented a special queueing mechanism, which resolves dependences, loads libraries in proper order and makes sure that they are loaded only once.
Now, since we are basing our widget on UI Dialog, which also depends on UI Draggable, UI Resizable, etc, we would like to concatenate all these libraries into one, jQuery UI Custom file just like it is usually done on jQuery UI site. But... this approach may cause a conflict with other WordPress plugins, that may use WordPresses native API and hence load their own versions of UI widgets.
Is there any way we can isolate our customized file from the rest of js environment, that potentially maybe pretty crowded with various libraries and multiple jQuery UI widgets of various versions?
We are not using UI Dialog directly, but it's self-made extension. While some functions are overloaded, close method stays the same. Now if we place youtube video into the Dialog and then close it, it continues to play in IE. It stops in all other browsers.
Building some custom widgets on top of jQuery UI, now when I try to destroy jQuery UI Dialog on top on which I have my widget, I see in FireBug that corresponding elements get stacked on top of html element.
I've attached a screenshot.
Is it how it is meant to be? Why?
I noticed similar behavior in the past with jQuery effects. Could not find a reason to it though, so I thought it was just my fault, of some kind.
This forum lacks accessibility. Especially for new comers. I had to actually look trough the DOM with FireBug to find New Post button. My eyes and mind just weren't realizing that ever-fixed content of jQuery top menu had changed!
I think it's wrong decision to put it there. Why not to replace it with original jQuery menu, to which everyone is hugely used. We could put forum menu just on top of forums, where that wasteful JQUERY FORUM title is right now (I bet everyone expects it to be there)! Everyone already knows that they are on the JQUERY FORUM, why you would need to remind them?
I wonder if I can see somewhere what events are binded to a DOM element (in FireBug maybe). Maybe it's obvious, but I just don't know yet if it's even possible.
Are there any good resources about effective RIA (using jQuery UI) DOM programming? Lot's of elements, dispatching various events, routing them to each other, updating through Ajax etc. Generally I'd like to draw some kind of limits. For example how many DOM there could be, how many events attached, until user experience gets slow, can I detect that such limit is close from inside browser, etc. Books, docs, articles? Does anyone know of any good resource on this topic?
Dialog window looks very bad when it's dragged in FF. Movement is not smooth at all. It feels like all the contents tend to jump out of it's boundaries. Not a good experience indeed. I would like to leave only a thin frame on move event. Is it possible?
I want to store a reference to a particular object using jQuery.data on another object, can it potentially lead to memory leaks? And another question. Those objects at some point are dynamically removed and if that happens will the connection and associated data automatically be released, or we got to do it manually?
I'm trying to get my mind around getter/setter functionality. I probably do not understand their purpose properly. What is the exact difference between setting a property as: this.someProperty = someValue; and setting it as: this._setData ('someProperty', someValue); What's the point in other words?
I'm building some of my own widgets, but I'm not yet confident with all those references and closures. Thus, using and passing them here and there. Is there a convenient tool or something to tell whether I'm leaking memory?
I'm trying to create a custom progressbar, which among others is of 5px height. It is ok with all other browsers, except IE6 (I know it dies out, etc, but according to current stats it's still more then Safari+Chrome+Opera altogether). It looks and feels like something is keeping it from shrinking to 5px, it does become thinner a bit, but then it stays constant (approximately at 30px of height)... ? Any help appreciated.
I know Internet Explorer sucks. It causes a lot of unobvious obstacles that one should always take by some trickery and dark magic. But now a HUGE problem comes from our favorite and faithful companion - Firefox. And the problem is that jerky animation during the movement of the Dialog box. What's that? Doesn't it suck as much as a whole IE6? Why?
Dropping IE6 I thought whoa - at last or something like that and now here is IE7. I'm not sure what the problem is, so I'll just describe it. We got a dialog box with some uploading stuff happening in it - progressbars, list of files being uploaded etc. Once file is uploaded, corresponding item becomes expandable (it show some file properties, actions that might be applied to it and so on). Now the problem - once we expand two or three entries, content becomes bigger then the dialog and logically forces scrollbars to appear. In all major browsers like FF, Opera, Safari, everything acts and scrolls smoothly. It's only IE that causes the problems. Content doesn't scroll at all. Scrollbars moves, but content doesn't and then suddenly it does, but appears on top of the titlebar. Very wierd. One specific that may be causing this is that we use animate to expand items smoothly. Although I do not know why it should affect anything at all anywhere :( Any idea? Has anyone encountered anything like this? Any solutions?
I've got several map tags with custom areas defined and corresponding images with usemap attributes. The problem is that those images are covered with transparent div. I manually intercept events on that div and route them to the images underneath it. But maps do not seem to react to routed events anymore. Is it correctable somehow? Or maybe I'm doing something wrong? The structure cannot be altered, transparent div must be on top and images and their corresponding maps must get the click event somehow :( Any suggestions?
"New in jQuery 1.3: All triggered events now bubble up the DOM tree. For example if you trigger an event on a paragraph then it will trigger on that element first, then on the parent element, and its parent, and so on up to the document. The event object will have a .target property equal to the original triggered element. You can prevent the bubbling by calling stopPropagation() or by returning false from your callback." http://docs.jquery.com/Events/trigger#eventdata In other words triggered event should bubble up to it's parent container, should it? If yes, then I want to catch it on parents level and trigger it on another child of choice, and so on. But it doesn't seem to bubble... :( Any help appreciated.