1.8rc1 Autocomplete Example on the site
Hello, I'd like to report a bug in the example of autocomplete's remote function on the website. The error is that the data is not beeing read from the server, because the search page ("search.php") is not well JSON-formatted. In JSON, all the parameters should be double-quoted, and the results from the php is being served as single quoted. Thank you, Tyron.
jquery UI 1.8rc1 build routine misses effects
Line 89 of build.xml in jQuery UI 1.8rc1 misspells the file names for effects so they are missed form the full build. <fileset dir="${src.dir}/" includes="jquery.ui.*.js, effects.*.js" excludes="${core.files}" /> should be <fileset dir="${src.dir}/" includes="jquery.ui.*.js, jquery.effects.*.js" excludes="${core.files}" />
Reopening a Trac bug for jQuery UI
I have a bug, #3930, that was closed as a dupe. I think there was an error in that though, because the dupe that is referenced is nothing like the bug in question. I am posting here because I don't seem to have permission to re-open tickets, and there's already a fair amount of information for that ticket that I didn't want to create a new one. Please advise -- thanks!
ui rc1: Autocomplete: JS Error, Menu sjowing top left corner
Hi guys, love the new version, but got a small issue. No idea if its my fault, got following js error: Error: ul.addClass("ui-autocomplete-menu").appendTo(parent).menu({focus: function (event, ui) {var item = ui.item.data("item.autocomplete");if (false !== self._trigger("focus", null, {item: item})) {self.element.val(item.value);}}, selected: function (event, ui) {var item = ui.item.data("item.autocomplete");if (false !== self._trigger("select", event, {item: item})) {self.element.val(item.value);}self.close(event);self.previous
1.8rc1 sortable#over method bugged -- called along with #sort instead of on mouseover
jQuery UI 1.8 (all versions, including the new RC1) call #over (seemingly) at the same time as #sort. #sort gets called very often since it's hooked into mousemove, so for #over which supposed to be called only occasionally this is quite a problem. 1.7.2 behaviour calls #over only when the mouse enters the draggable/droppable/sortable area, as expected. EDIT - Apologies, I meant to say sortable, not draggable. EDIT - Here is an example of the problem: 1.8rc1: http://jsbin.com/uxilo3/edit 1.7.2: http://jsbin.com/uxilo3/2/edit
blut.button not working correctly (modal dialog)
I am working with a modal dialog, containing two buttons (submit/cancel). When I use the tab key to cycle through all the buttons, for some reason the leftmost button stays in its focus state. When I check the button using Firebug, it still has the ui-state-focus class. The blur event does not seem to happen. When I change blur.button to focusout.button in the code however, all seem to work correctly. Cheers, Steven Roebert
UI Tabs 1.8rc1 ignores "ui-tabs-selected" when intialising
If, for example, the third tab has a class of "ui-tabs-selected" then tabs 1.8rc1 always selects tab index 0 instead of 2. This seems to be caused by line 176: o.selected = o.selected || this.lis.length ? 0 : -1; ...it accidentally changes o.selected from the desired index to a value of 0. The problem can be fixed by adding parentheses like this: o.selected = o.selected || ( this.lis.length ? 0 : -1 ); Hope this helps. George
IE shows black background for PNG-24 images on show
Any plans to fix Ticket #3791 - IE shows black background for PNG-24 images on drag event (http://dev.jqueryui.com/ticket/3791) ? I have this issue with show() using IE8 (and entered a bug report with core jQuery http://dev.jquery.com/ticket/5946 - since it seems show() is part of core not UI). I am guessing these are really the same bug. Stephen
1.8rc1 iconed Buttons with submit inputs
Hello, I'm still testing the Button feature. It seems that inputs of type "submit" don't accept icons. According to this quote from the official overview, adding an icon could be possible : Button enhances standard form elements like button, input of type submit or reset or anchors to themable buttons with appropiate mouseover and active styles. I ran the following code : <p> <button class="button" type="button">Button</button> </p> <p> <input class="button" type="checkbox" id="checkbox" />
JQueryUI downloaded demo not working with 1.8rc1
Hi, The demo included in the downloaded, index.html, does not seem to be working when I download the latest version of JQueryUI (1.8rc1) to use with JQuery 1.4. Firstly, the index.html file seems to point to JQuery 1.3. When I corrected this some of the demo page started to work (e.g. the date picker) but many still do not (slider and progress bar for example). Is this a know issue and is it possible to temporarily use an older version of JQueryUI with jQuery 1.4 - the download page seems to imply
UI Demos in IE are not RC (1.8rc1)
I found several demo issues. Would be glad to start posting them but figured it would be better to not have 20 plus people filling the same issues. portlets jump when I drag item out of middle column for instance in sortable select demo highlights stuff when doing multiple selects (but select works right) the bird auto select was not showing any content.
1.8rc1 - Draggable stack option no longer as useful
In 1.8rc1 the stack option has changed from hash to selector losing the option to set the z-order min. In my opinion this is mistake. The old way you could have two types of draggables, type A and type B, and keep all type A's on top of type B's by setting B's min to 0 and A's min to be slightly higher then the number of B elements you could reasonably expect. Each time a drag of type B occurred the z-order of all the B elements was recalculated starting at 0, never approaching the A min. The new
jQuery UI 1.8rc1 bug in $.ui.position collision "flip"
The collision handling code for flipping left can be found on line 8319 of jquery.ui.js. At the very top of the function is this check: if (data.at[0] == 'center') return;which causes the flip to fail if we want to position some element at the horizontal center of the target. I believe this check should be: if (data.my[0] == 'center') return; which would cause the flip to fail if we're positioning my horizontal center, in which case a horizontal flip would not change the position. Consider
Potential problem with nested droppable
I think this may be a problem. I have nested droppables. The inner droppables are greedy so if I drop on an inner one the outer one doesn't get dropped on. This works as expected. Both inner and outer accept the same draggables. The draggables I'm using have revert option set to invalid. I notice that when I drop the draggable is always reverted even though the drop succeeds. This seems wrong. It doesn't happen when there is no nesting. I think the problem is in ui.ddmanager.drop. The dropped var
Testing jQueryUI 1.8rc on Chrome - losts of errors
Where's the test matrix for jQuery 1.8? I'm getting a bunch of errors when running the unit tests locally. I'd like to know if there are tracked, how they are being resolved, etc. I'd assume 100% would be the goal for a release. Just trying to understand how that works.
jQuery-UI 1.8RC1 : sortable list doesn't allow drop at first and last position depending where the mouse gets clicked-to-drag on
This is in 1.8RC1 (and seems to be a regression from 1.7): (using jQuery 1.4.1) If you have a sortable ul-li with 2 items at least, the dropping before the first item and after the last item doesn't work if you click to drag on the opposite side in the item to move: - if you click in upper part to drag the first item after the last one doesn't work - if you click in lower part to drag the first item after the last one WORKS - if you click in upper part to drag the last item after the last one WORKS
A Strategy for localizing jQuery UI plugins
I have to support several locales for the jQuery UI plugins I am creating and am trying to think of a consistent way to support localization of numeral characters and any strings that may be embedded in the plugin. I think the mechanism I have in mind may be useful to the larger jQuery UI set of plugins. To clarify, this proposal is mean to support localization of numeral characters and strings embedded in a plugin, not dates or currency formats ($ 1.000,00 vs. 1,000.00) but it could conceivable
Documenting bound events as part of specifications
Here is something we should do in the future, and where time is available, add for existing components: Document all the events that are bound as part of the functional specification, including details of event-object properties that are read. For example, Autocomplete binds, among various others, a keydown-event to the element, and checks the keyCode event property for various values. This could make code reviews much more effective, and even better yet, would server as documentation on how to script
Enhancement, allowing animateClass to affect other nodes.
Right now the animateClass functionality is limited to only animating the node(s) you change the class on. I'd like the ability to use animateClass/switchClass/etc... in a way that affects other nodes. For example in the case of putting classes on the body to depict states that parts of the page is in (fairly common practice in flexible apps at times) I'd like to be able to have the change in class affect those other nodes. For example, pretending that there is a div in the page with an id of #sidebar
Dialog widget beforeClose event -- crashing change
I am sorry if this has been covered before but in 1.7.2 the event is named "beforeclose". In 1.8pre it is named "beforeClose" (camelCase). Two things: First, that needs to be thoroughly documented. Second, WTF? This gratuitous breaking of user-code is, to my eye, really, really rookie. ESPECIALLY considering how trivial it would be to support both, at least for a time. **--** Steve
Plan for November
I'd like to propose the following plan for the remainder of the month. Spend the first half of the month focusing on bug fixes. We currently have over 200 bugs marked for 1.8. This number is growing at a much slower rate than it was a few months ago, but we really need to get this number down. While blockers and criticals are the most important, they're not necessarily the tickets we should be focusing on right now. These tickets are often the hardest to track down and/or the most time consuming
Draggable inline element still moves at twice the speed in webkit in 1.8b1
Is this ticket: http://dev.jqueryui.com/ticket/4824 going to be fixed in 1.8 final?
Proposed patch: Datepicker appendTo option
We want to use the Datepicker widget in conjunction with a Bubble widget we developed. The Bubble widget is a bit like Dialog, except that the bubble is dismissed when the user clicks anywhere outside it. The problem is, since Datepicker always appends to the document body, it always appears to be outside of our Bubble. Thus, clicking on the datepicker closes the bubble. We want, therefore, to patch Datepicker to append to any element. We have already successfully added an appendTo option to the
Grabbing content via AJAX in tabs does not work
After having a lot of trouble with tabs, I went back to the demo code that is included in the download. When loading jQuery jquery-1.3.2.js, it works. When loading jQuery jquery-1.4.1.js, it does not. Clicking a tab simply adds "#ui-tabs-[object Object]" to the end of the current URL. Are these not compatible? Here is the mark-up: <!doctype html> <html lang="en"> <head> <title>jQuery UI Tabs - Content via Ajax</title> <link type="text/css" href="../../themes/base/ui.all.css" rel="stylesheet" /> <script
ui tabs broke(completely) after hiding the div they are in with an animation
the discussion of the problem started at http://groups.google.com/group/jquery-ui-layout/browse_thread/thread/12627ef6f2d489fb the plugin author has put up a page on which you can see the problem: http://layout.jquery-dev.net/demos/tabs_jq14_test.html Kevin Dalman: This *is* a bug in the Effects, but it does NOT affect slideToggle() or toggle('slow'), which is why your test page did not reproduce it. However Layout uses the .hide('slide') syntax so that it can easily specify different effects and
ui.core.js/1.7.2/line 447
Hi, I'm new here and not sure how to go about checking the progress of the development code to see whether what seems to me a bug has already been picked up. I was trying to follow thru with the debugger why a scroll event does not appear to propagate up the food chain in IE6 when I stumbled across this piece of code at line 447 in ui.core.js (1.7.2): $(document) .bind('mousemove.'+this.widgetName, this._mouseMoveDelegate) .bind('mouseup.'+this.widgetName, this._mouseUpDelegate); Judging by the textual
ui.tabs AJAX error handling
Hi, I am sure there is a big push for 1.8 final, but I am wondering if it would be possible to land this patch before the final version is released, or shortly thereafter for 1.8.1. It simply extends support of the ui.tabs AJAX loader to enable custom event handling in the cases when there is an error loading an ajax tab, similar to the custom handling already available for a successful AJAX load. The patch is on ticket 5070 in Trac (I would link to it here but the RTE’s link button seems to be broken).
In the Dialog, auto focus on first tabbable element should be a configuration option
We have some Dialog windows that when opened we do not want any elements to be focused. A good example of this is if we use textbox hints (text displayed in the textbox giving information on when that textbox does) in a dialog. When the textbox is focused, it clears the hint. When we open the dialog we would prefer it if the textbox hint was not cleared until the user selects the box. Technically there are other ways to get around this problem but it would be nice if an option was added indicating
Bug in theme roller? Calendar icons disappearing when changing their color
Hello everybody, When I try to change the color of the icons in the "Header/Toolbar" section of Themeroller, they disappear and are only visible in hover state. I'm trying to gather more info before filing a ticket...Regards, Louis-Rémi Babé
Effects Broken with jQuery 1.4 And/Or UI 1.8.a2
There are numerous problems with the UI Effects with the new versions of both jQuery and UI. I've created sample pages to illustrate the problems with each combination of library... NOTE: Links below have been fixed - were originally broken jQuery 1.3.2 + UI 1.7.2 : http://layout.jquery-dev.net/demos/test_jq13_ui17.html Everything works correctly jQuery 1.4 + UI 1.7.2 : http://layout.jquery-dev.net/demos/test_jq14_ui17.html Default toggle(speed) effect works correctly All other effects also work,
Using hide('slide') will DESTROY most UI Widgets!
If a UI widget like Tabs or Accordion is inside a DIV that is hidden and reshown using $(elem).hide('slide') and $(elem).show('slide'), the widget is completely destroyed - ie, all widgets styles and events are removed. This bug does not occur when using slideToggle(). Here is a demo page that shows the issues: http://layout.jquery-dev.net/demos/tabs_jq14_test.html This is a repost from the old DEV forum: http://groups.google.com/group/jquery-dev/browse_thread/thread/f1eb7202a82836a5#
Developing special-purpose Widgets, should I post my questions here or in Using JQuery UI forum?
I will be spending a lot of time developing custom set of widgets for managing simple games, like scoreboard, timer, feedback, etc. The code will be MIT-licensed. Should I post my questions related to these widgets to this forum or to the Using jQuery UI forum?
Fwd: [jquery-ui] Draggable inside accordion
This problem actually popped up during a jQuery UI workshop. Is there an alternative to the appendTo solution? Whatever the best approach, we should document it, eg. add a accordion-with-draggable-content demo. Jörn
UI Widgets developed within my master thesis
Hey, I developed some widgets with help of the jQuery widget factory and the jQuery UI CSS Framework within my master thesis at the University of Applied Science GieÃen-Friedberg, Germany and Martin Kliehm suggested to post it in here and the wiki. I dont like to spam your wiki, so i decided to ask how to contribute the best way. Perhaps you could use some of my work or just give me some feedback. My goal was to provide some accessible, usable and easy to implement widgets to improve quality and
ui.tabs initialization request
Hi, An initial page load renders DOM with all content for a selected tab, which is great for people with no scripting. I want to use ui.tabs widget. My tabs are built with the ajax requirement where the <a> element href points to the desired url for loading tab content. I also use the option where the <a> element's title attribute is used to reference the container for tab content. eg: <a href="/foo/bar?=open" title="tab content">Lalala</a> <div id="tab_content"/> If I listen to the DOM loaded event
r3621 committed - Merged in /branches/dev r3251:3620 (excluding autocomplete, modal, too...
Revision: 3621 Author: scott.gonzalez Date: Wed Jan 6 19:19:50 2010 Log: Merged in /branches/dev r3251:3620 excluding autocomplete, modal, tooltip, menu; including menu static tests . http://code.google.com/p/jquery-ui/source/detail?r=3621 Added: /trunk/demos/button /trunk/external/jquery.metadata.js /trunk/tests/static/button /trunk/tests/static/menu /trunk/tests/unit/button /trunk/tests/unit/widget /trunk/tests/visual/button /trunk/themes/base/images/ui-anim.basic.16x16.gif /trunk/themes/base/ui.button.css
Should button be re-entrant?
I've been experimenting with the new button widget. Man, what a sweet widget. If you haven't tried it, you're going to love it. Question: Should button be re-entrant. Step 1: $ "#fooAnchor" .button { label : "foo" } // makes a button that says "foo" Step 2: $ "#fooAnchor" .button { label : "bar" } // button still says "foo" !? My expectation: We should be able to use the .button interface to modify a pre-button'd button. What do you think? Open a ticket? **--** Steve --
r3620 committed - Merged in trunk r3567:3582.
Revision: 3620 Author: scott.gonzalez Date: Wed Jan 6 10:01:07 2010 Log: Merged in trunk r3567:3582. http://code.google.com/p/jquery-ui/source/detail?r=3620 Added: /branches/dev/tests/visual/datepicker/datepicker_ticket_4071.html Modified: /branches/dev /branches/dev/demos/slider/colorpicker.html /branches/dev/demos/slider/default.html /branches/dev/demos/slider/hotelrooms.html /branches/dev/demos/slider/multiple-vertical.html /branches/dev/demos/slider/range-vertical.html /branches/dev/demos/slider/range.html
r3619 committed - autocomplete: renaming result-property to value-property, matching sel...
Revision: 3619 Author: joern.zaefferer Date: Wed Jan 6 09:56:20 2010 Log: autocomplete: renaming result-property to value-property, matching selectmenu widget and the related dom attribute http://code.google.com/p/jquery-ui/source/detail?r=3619 Modified: /branches/dev/demos/autocomplete/combobox.html /branches/dev/demos/autocomplete/remote-jsonp.html /branches/dev/demos/autocomplete/remote-with-cache.html /branches/dev/demos/autocomplete/remote.html /branches/dev/tests/visual/autocomplete/combobox.html
autocomplete behaviour
I am struggling a little bit with the intended behaviour of the autocomplete widget. Currently possible items have a value which the plugin calls the 'result' currently and a label. The label is shown in the suggestions menu. Once you select an item its value is shown in the input field. This approach is problematic for systems where you want to use an internal value such as a database id. Currently in those situations you will end up with a UI like this: ---------------------- Select your city:
Next Page