- Screen name: rdworth
rdworth's Profile
72 Posts
4200 Responses
16
Followers
Show:
- Expanded view
- List view
Private Message
- 03-Sep-2011 06:50 AM
- Forum: Using jQuery UI
hilbert00 reports:I have found this strange behaviour when using ui.position. I have a widget designed in a column wise manner and I was thinking to use the position utility to position the left and right cols and their position.
The problem is that after the positioning of the right col to the right, the height of the container box is much heigher than needed as it would contain the left and right divs one after the other.
This is the link to the jsFiddle test case: http://jsfiddle.net/hilbert00/sAbxS/
- 23-Mar-2010 11:02 PM
- Forum: Developing jQuery UI
Example: you want to submit a patch to the Datepicker file, jquery.ui.datepicker.js, but you heard svn is out and git is in.
Step 1: Sign up for GitHub (jump on it)- https://github.com/signup/free
- Enter Username, Email Address, Password, (ignore the SSH Public Key field)
- Click "I agree, sign me up!"
Step 2: Fork the jQuery UI repository (become a committer of your very own copy of jQuery UI)- http://github.com/jquery/jquery-ui
- Click "Fork"
Step 3: Modify your fork through the GitHub web interface (commit your change without knowing git)- http://github.com/{your-username}/jquery-ui
- Click on the folder and file you want to modify
- click "ui/"
- click "jquery.ui.datepicker.js"
- When you're viewing the contents of the file you want to change, click "edit"
- Make changes to the file in the editor
- Enter a Commit Message to summarize the changes you've made and why you've made them. This should include a reference to a Trac ticket, formatted like so
- "Changed ... and ... datepicker done right. Fixes #3945 - Datepicker does not respond to any click events in AIR"
- Click "Commit"
Step 4: Submit a Pull Request (tell the jQuery UI team why your change rocks)- http://github.com/{your-username}/jquery-ui/blob/{id-of-commit}/ui/jquery.ui.datepicker.js
- Click "Pull Request"
- Enter a Message that will go with your commit to be reviewed by core committers
- Click "Send Pull Request"
Step 5: Add a link to your commit to the ticket in Trac (tell everyone you're on the case)- http://dev.jqueryui.com/ticket/3945
- Add a comment that includes a hyperlink to the url of your commit from Step 4
Step 6: Eat a cookie (yum)- Note: this step is :not(optional)
Note: if you need to change multiple files as part of one commit, the web interface will not be the way to go. In that case you'll want to learn a little more about github and git. You can start here:- Learn GitHub: http://help.github.com/
- Learn Git: http://progit.org/book/
The third release candidate for jQuery UI 1.8 is out and live on jqueryui.com. You can download it here:
Download
File Downloads
- Development Bundle: http://jquery-ui.googlecode.com/files/jquery-ui-1.8rc3.zip
Svn
Changelog
See the 1.8rc3 Changelog for what’s been fixed since 1.8rc2. For a list of all issues fixed since 1.7.2, see previous 1.8 changelogs.
Upgrade Guide
A full Upgrade Guide for easing the transition between 1.7 and 1.8 is in the works. This will be ready in time for the final release. In the meantime, one of the more significant (and breaking) changes in 1.8 already documented there is a refactor of the widget factory. This means anyone that has built their own plugin that uses the widget factory will need to make a number of changes for compatibility with 1.8. For a view of these changes, see the widget factory section of the Upgrade Guide. Also, see this sample implementation of a simple widget with both the 1.7 and 1.8 widget factories, and the differences, by Scott González.
Plan for 1.8 final
We hope to release jQuery UI 1.8 final after a couple days, assuming there aren’t any blocking issues present in this release candidate.
Thanks
A big thanks to all that have worked on all the bug fixes and other improvements that have gone into this release. We’ll have a proper listing of all contributors in the final release announcement.
How to report issues
If you find any issues in this release, please post them in the Developing jQuery UI Forum. Thank you.
- 19-Feb-2010 02:38 AM
- Forum: About the jQuery Forum
Each time I add or remove a tag from a post the number of views goes up once or twice. This can really start to add up when (for example) removing 3 tags and adding 2 tags. It would be great if this didn't happen, since it would keep the number of views at a more realistic value. Thanks!- 31-Jan-2010 09:20 AM
- Forum: Developing jQuery UI
There are times when you're moving a slider across a big range but with lots of small steps and it's difficult, if possible, to select a precise value. Imagine two values are only 1px apart, or even sharing the same pixel position. Here's an idea. We could enable the user to hold down the Ctrl-key (Option-key on a Mac) while dragging a slider handle and the effect of the same movement of the mouse would be slowed down 5-10 times. So you could really dial in between a couple numbers that are really close together. This idea comes to me from some Adobe Creative Suite controls that have this behavior and also this thread:
http://forum.jquery.com/topic/using-slider-with-times- The first release candidate for jQuery UI 1.8 is out and is live on http://jqueryui.com/demos/ . You can download it here:
Downloads
File Downloads
Development Bundle: http://jquery-ui.googlecode.com/files/jquery-ui-1.8rc1.zip
Svn
Tag: http://jquery-ui.googlecode.com/svn/tags/1.8rc1/
Changelog
See the 1.8rc1 Changelog for full details on what’s included in this release since 1.8b1.
Barring any catastrophic problems this code will become jQuery UI 1.8.
NOTE: If you’re using jQuery UI 1.8rc1 and you run into an error please make sure that you’re using the regular version (not the minified version) of the code, it’ll make it easier to spot where the error is occurring.
How can I help?
To start, try dropping the above un-minified version of jQuery UI 1.8rc1 into a live application that you’re running. Although, before doing so, make sure you look at the changelogs up to this release to make sure there are no potential conflicts with your code. If you hit an exception or some weirdness occurs immediately post on the Developing jQuery UI forum. Be sure to mention that you hit the bug in jQuery UI 1.8rc1!- I just tracked down an issue that was causing the jQuery UI Datepicker to be incompatible with ASP.Net validator controls. Here's the ticket:
<a href="http://dev.jqueryui.com/ticket/4071" target="_blank">http://dev.jqueryui.com/ticket/4071</a>
and a visual test page:
<a href="http://jquery-ui.googlecode.com/svn/trunk/tests/visual/datepicker/datepicker_ticket_4071.html" target="_blank">http://jquery-ui.googlecode.com/svn/trunk/tests/visual/datepicker/datepicker_ticket_4071.html</a>
The issue is occurring when a date (an A element) in the datepicker is clicked, it calls $(INPUTelement).change() and when the event handler bound to that element is triggered, it gets the click event on the A instead of a change event on the input.
It seems when an event is triggered programatically in IE, and the event handler was bound via the onchange attribute (whether html or javascript) instead of attachEvent, a new event object isn't created if you call elem.oneventname() but one is if you call elem.fireEvent('oneventname'). Here's a minimal test page:
<a href="http://jsbin.com/oliwi" target="_blank">http://jsbin.com/oliwi</a>
source: <a href="http://jsbin.com/oliwi/edit" target="_blank">http://jsbin.com/oliwi/edit</a>
It seems it could be solved easily by using .fireEvent if it exists inside of .trigger():
elem.fireEvent && elem.fireEvent( type ) || elem[ type ]();
Thoughts?
- Richard
References:
Jquery datepicker popup not closing on select date in IE8
<a href="http://stackoverflow.com/questions/1704398/jquery-datepicker-popup-not-closing-on-select-date-in-ie8" target="_blank">http://stackoverflow.com/questions/1704398/jquery-datepicker-popup-not-closing-on-select-date-in-ie8</a>
Fire the onchange event the browser independent way
<a href="http://www.rakshith.net/blog/?p=35" target="_blank">http://www.rakshith.net/blog/?p=35</a>
Event class for jQuery
<a href="http://groups.google.com/group/jquery-dev/msg/1d7ab35fa59fa053">http://groups.google.com/group/jquery-dev/msg/1d7ab35fa59fa053</a>--
- blog post:
<a href="http://blog.jqueryui.com/2009/12/jquery-ui-18a2/">http://blog.jqueryui.com/2009/12/jquery-ui-18a2/</a>
changelog:
<a href="http://jqueryui.com/docs/Changelog/1.8a2">http://jqueryui.com/docs/Changelog/1.8a2</a>
- Richard
Richard D. Worth
jQuery UI Release Manager--
- I couldn't find a commit notification to reply to, but r3473 caused a regression. See
<a href="http://jquery-ui.googlecode.com/svn/trunk/tests/unit/position/position.html">http://jquery-ui.googlecode.com/svn/trunk/tests/unit/position/position.html</a>
Compare to
<a href="http://jquery-ui.googlecode.com/svn/tags/1.8a1/tests/unit/position/position.html">http://jquery-ui.googlecode.com/svn/tags/1.8a1/tests/unit/position/position.html</a>
- Richard--
- 23-Dec-2009 09:32 AM
- Forum: Developing jQuery Core
<div>Please review.</div><div>
</div><div><a href="http://dev.jquery.com/ticket/5706">http://dev.jquery.com/ticket/5706</a></div><div>
</div><div>Ticket has full description as well as two patches on github, one for jQuery, one for Sizzle. Thanks.</div>
<div>
</div><div>- Richard</div><div>
</div>--
- <div>Scott G and I came up with an idea yesterday, to solve a common problem.</div><div>
</div><div><b>Problem</b></div><div>
</div>Many jQuery UI plugins wrap the element on which the .pluginname() init is called, or provide a different element altogether. Some plugins do this always, such as Dialog:<div>
</div><div> <p id="dialog">jQuery UI Dialog</div><div>after $('#dialog').dialog() becomes</div><div> <div class="ui-dialog">[...]<p id="dialog" class="ui-dialog-content">jQuery UI Dialog[ ... ]</div></div>
<div>
</div><div>Other plugins do it sometimes. Resizable doesn't wrap a div:</div><div>
</div><div> <div id="resizable">jQuery UI Resizable</div></div><div>after $('#resizable').resizable() becomes</div>
<div> <div id="resizable" class="ui-resizable">jQuery UI Resizable [ ... handles ... ]</div></div><div>
</div><div>but wraps iframes and imgs, among others:</div><div>
</div><div> <iframe></iframe> or <img></div>
<div>after $('iframe, img').resizable() become</div><div> <div class="ui-resizable"><iframe></iframe> [ ... handles ... ] </div></div><div> <div class="ui-resizable"><img> [ ... handles ... ] </div></div>
<div>
</div><div>as those elements can't contain the resize handles, so they need a wrapper. But if a wrapper isn't needed, it isn't created.</div><div>
</div><div>In the case of datepicker called on an input, the element created is not a wrapper, but some external div.</div>
<div>
</div><div>In all these cases it can be useful to get access to that generated element from the original element and plugin instance. For people to hide the dialog titlebar, for example, one recommendation is:</div>
<div>
</div><div>jQuery 1.2.6:</div><div>$('#dialog').parents('.ui-dialog:first').find('ui-dialog-titlebar').hide();</div><div>jQuery 1.3:</div><div>$('#dialog').closest('.ui-dialog').find('ui-dialog-titlebar').hide();</div>
<div>
</div><div>This got a little better with 1.3, especially as you have to worry about nested plugins when using .parents(). Not applicable here as dialogs are never nested. But this doesn't address outside elements, like that created by datepicker.</div>
<div>
</div><div><b>Proposal</b></div><div>
</div><div>Create a new common method for all jQuery UI plugins called 'element'. This will always return the associated element with the ui-pluginname class, whether original or generated, so you could do</div>
<div>
</div><div>$('#msg').dialog('element').find('ui-dialog-titlebar').hide();</div><div>
</div><div>$('div').resizable('element').animate({ width: '500px' });</div><div>
</div><div>$('img').resizable('element').height(300);</div><div>
</div><div>$('input.date').datepicker('element').show('slow');</div><div>
</div><div>We currently use this.element internally in the jQuery UI widget factory and all widget internal implementations to mean the original element on which .pluginname() init was called. So as to avoid confusion, this.element will be deprecated in favor of this.elem. As these (method element and this.element) will never conflict, just be a source of confusion, there's no rush to remove the deprecated this.element. Maybe at 2.0.</div>
<div>
</div><div>Thoughts?</div><div>
</div><div>- Richard</div><div>
</div>- <div>Paul and I had a good chat and cleared up a couple issues that have been bothering me a bit with the current spec and implementation. Currently there's a closest option, which is a boolean. First, I think if there's an option, really any variable, that's a boolean, it should be *obvious* from it's name alone, what it means when that boolean holds true vs. false. Unfortunately, this fails both tests. So, I think the name could use some help. Anyway, currently when closest is false, the default, you select in DOM order when using the arrow keys. When closest is true, you select in position order when using the arrow keys. The thing that's weird is when closest is true and you press for example (while holding shift), down+down+right+right, it adds to the selection each item it passes the focus over, creating an L. I call this a snake. You can arrow all around the place (while holding shift) and draw a really long snake. It will even erase portions of itself that it crosses. Fun game. But it's inconsistent. Selection with keyboard arrows should be the same as mouse selection. So if you shift+down+down+right+right, it should draw a lasso from the item you started on, to the one you ended on, selecting all 9 items, not just the 5 the arrow keys navigated the focus over. The other thing that's really odd about the current implementation is that when closest is set to false, the down and up arrow keys act the same as the left and right arrow keys, going next and prev (in dom order), instead of to the items below and above (in layout order).</div>
<div>
</div><div>So, there's two separate things here. I propose:</div><div>1. arrow keys should always move the focus up, down, left, right. That is, it should always be location/position based, never dom based.</div>
<div>2. selection mode can either be dom mode or position/lasso/rectangle mode. Whether you're using the mouse or the keyboard, should be the same</div><div>
</div><div>So the first point can be handled by taking the current arrow nav logic from closest:true and applying it always.</div>
<div>
</div><div>The second point can be handled by removing the 'closest' option, and adding a 'mode' option, with two possible values: 'dom' | 'box'. Dom mode would select all items between the first selected item and the currently focused item, in dom order. Box mode would draw a rectangle between the first selected item and the currently focused item, selecting all items the box touches, based on tolerance.</div>
<div>
</div><div>This will handle the most common selection scenarios. For example:</div><div>
</div><div>text selection, windows explorer = mode: 'dom'</div><div>grid, spreadsheet, graphics program = mode: 'box'</div>
<div>
</div><div>As for the snake, if people think it's valuable, it could be mode:'pen', or maybe mode:'cursor'. And it should support keyboard as well as mouse. This would allow you to "draw" a selection of any shape. I don't see this as being nearly as fundamental as 'dom' and 'box' modes, so if it doesn't happen until a later version, I think that's fine.</div>
<div>
</div><div>Thoughts?</div><div>
</div><div>- Richard</div><div>
</div>- <div>blog post:</div><div><a href="http://blog.jqueryui.com/2009/08/jquery-ui-18a1/">http://blog.jqueryui.com/2009/08/jquery-ui-18a1/</a></div><div>
</div><div>changelog:</div><div><a href="http://jqueryui.com/docs/Changelog/1.8a1">http://jqueryui.com/docs/Changelog/1.8a1</a></div>
<div>
</div><div>- Richard</div><div>
</div><div>Richard D. Worth</div><div>jQuery UI Release Manager</div><div>
</div>- How about we add a class to each generated dialog button:<div>
</div><div>ui-dialog-button-{lcase-text-of-the-button-spaces-replaced-with-hyphen}</div><div>
</div><div>So if you had</div><div>
</div><div>$("#myDiv").dialog({</div>
<div> buttons: {</div><div> "Ok": function() { ... },</div><div> "Cancel": function() { ... }</div><div> }</div><div>});</div><div>
</div><div>then you could target those buttons, whether you wanted to hide them, show them, disable them:</div>
<div>
</div><div>$(".ui-dialog-button-ok").hide();</div><div>
</div><div>$(".ui-dialog-button-cancel").attr("disabled", "disabled");</div><div>
</div><div>Currently you have to do this using the ordinal position and index of the button in the pane. Thoughts?</div>
<div>
</div><div>- Richard</div><div><span class="Apple-style-span" style="border-collapse: collapse; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><span class="Apple-style-span" style="border-collapse: separate; white-space: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px;">
</span></span></div>- I'm starting to clean up /branches/dev/. Long overdue. A few notes. It should:
- contain only plugins that the team has given a priority of 1-3 (low, med, high)
- contain a separate branch for each plugin
Each separate sub branch should:
- have the same name as the plugin it contains
- be a complete branch of the trunk
- contain a representation of every change that should be made to the
trunk in order to merge that plugin to the trunk. For example, if you
delete a file from a branch, this communicates that this file should be
deleted once that plugin is merged to the trunk.
- have the trunk merged up to it regularly to keep up with changes
I'll try and stay on top of that last point. I got behind the last few months. Let me know if you have any questions. Thanks.
- Richard- See blog post:
This Week in jQuery UI vol. 7
- Richard
<a href="http://blog.jqueryui.com/2009/04/this-week-in-jquery-ui-vol-7/">http://blog.jqueryui.com/2009/04/this-week-in-jquery-ui-vol-7/</a>
- blog post:
<a href="http://blog.jqueryui.com/2009/04/jquery-ui-16/">http://blog.jqueryui.com/2009/04/jquery-ui-16/</a>
changelog:
<a href="http://jqueryui.com/docs/Changelog/1.6">http://jqueryui.com/docs/Changelog/1.6</a>
- Richard
Richard D. Worth
jQuery UI Release Manager- See blog post:
This Week in jQuery UI vol. 5
<a href="http://blog.jqueryui.com/2009/04/this-week-in-jquery-ui-vol-5/">http://blog.jqueryui.com/2009/04/this-week-in-jquery-ui-vol-5/</a>
- Richard- See blog post:
This Week in jQuery UI vol. 4
<a href="http://blog.jqueryui.com/2009/04/this-week-in-jquery-ui-vol-4/">http://blog.jqueryui.com/2009/04/this-week-in-jquery-ui-vol-4/</a>
- Richard- If you fix a ticket in the trunk for 1.8 (see 1.8 Closed report: <a href="http://dev.jqueryui.com/report/20">http://dev.jqueryui.com/report/20</a>) and feel it should be considered for inclusion in 1.7.2, please add it to this list:
<a href="http://wiki.jqueryui.com/Proposed-tickets-for-172">http://wiki.jqueryui.com/Proposed-tickets-for-172</a>
The 1.7.2 release will be finalized tomorrow (Wed.) night. Thanks.
- Richard- The legacy preview release, jQuery UI 1.6rc2.6, is ready for download and testing. See
<a href="http://blog.jqueryui.com/2009/03/jquery-ui-16rc26/">http://blog.jqueryui.com/2009/03/jquery-ui-16rc26/</a>
Development bundle:
<a href="http://jquery-ui.googlecode.com/files/jquery.ui-1.6rc2.6.zip">http://jquery-ui.googlecode.com/files/jquery.ui-1.6rc2.6.zip</a>
Svn:
<a href="http://jquery-ui.googlecode.com/svn/tags/1.6rc2.6/">http://jquery-ui.googlecode.com/svn/tags/1.6rc2.6/</a>
Please file any issues found in the bug tracker:
<a href="http://dev.jqueryui.com/newticket">http://dev.jqueryui.com/newticket</a> (note: requires registration)
and be sure to set the 'version' to '1.6rc2.6' and the 'milestone' to '1.6'. Thanks.
- Richard
Richard D. Worth
jQuery UI Release Manager- See blog post:
This Week in jQuery UI vol. 2
<a href="http://blog.jqueryui.com/2009/03/this-week-in-jquery-ui-vol-2/">http://blog.jqueryui.com/2009/03/this-week-in-jquery-ui-vol-2/</a>
- Richard- blog post:
<a href="http://blog.jqueryui.com/2009/03/jquery-ui-171/">http://blog.jqueryui.com/2009/03/jquery-ui-171/</a>
changelog:
<a href="http://jqueryui.com/docs/Changelog/1.7.1">http://jqueryui.com/docs/Changelog/1.7.1</a>
- Richard
Richard D. Worth
jQuery UI Release Manager- See blog post:
This Week in jQuery UI vol. 1
<a href="http://blog.jqueryui.com/2009/03/this-week-in-jquery-ui-vol-1/">http://blog.jqueryui.com/2009/03/this-week-in-jquery-ui-vol-1/</a>
Also, check out the first in a similar series (by Karl Swedberg), over on the jQuery blog:
This Week in jQuery vol. 1
<a href="http://blog.jquery.com/2009/03/13/this-week-in-jquery-vol-1/">http://blog.jquery.com/2009/03/13/this-week-in-jquery-vol-1/</a>
- Richard- We released 1.6rc2.5 tonight. See <a href="http://blog.jqueryui.com/2009/03/jquery-ui-16rc25/">http://blog.jqueryui.com/2009/03/jquery-ui-16rc25/</a> . It was based on 1.6rc2 (r709), plus all revisions between r709-r1039 (pre jQuery UI CSS Framework). After that I merged only the following revs
<a href="http://ui.jquery.com/bugs/changeset/1045">r1045</a> - Dialog: Fixed <a href="http://dev.jqueryui.com/ticket/3637">#3637</a>: Added role of button to close link.
<a href="http://ui.jquery.com/bugs/changeset/1046">r1046</a> - Core: Removed some UTF-8 BOMs causing problems in the download builder versions of files.
<a href="http://ui.jquery.com/bugs/changeset/1051">r1051</a> - Datepicker: Fixed <a href="http://dev.jqueryui.com/ticket/3610">#3610</a>. Error in French l18n file.
<a href="http://ui.jquery.com/bugs/changeset/1052">r1052</a> - Datepicker: Fixed <a href="http://dev.jqueryui.com/ticket/3598">#3598</a>. Datepicker Japanese translation replacement
<a href="http://ui.jquery.com/bugs/changeset/1053">r1053</a> - Datepicker: Escape text to prevent date info substitution
<a href="http://ui.jquery.com/bugs/changeset/1054">r1054</a> - Datepicker: Fixed <a href="http://dev.jqueryui.com/ticket/3610">#3610</a>. Error in French l18n file.
<a href="http://ui.jquery.com/bugs/changeset/1055">r1055</a> - Datepicker: Fixed <a href="http://dev.jqueryui.com/ticket/3642">#3642</a>. firstDay displays day names incorrectly.
<a href="http://ui.jquery.com/bugs/changeset/1077">r1077</a> - Core: Removed UTF-8 BOM again. Turns out it was added by Notepad.
<a href="http://ui.jquery.com/bugs/changeset/1078">r1078</a> - Core: Removed names from ui.core.js as all contribution credit is given in AUTHORS.txt and <a href="http://ui.jquery.com/about">http://ui.jquery.com/about</a>
<a href="http://ui.jquery.com/bugs/changeset/1079">r1079</a> - effects.core.js: Fixed character encoding so Notepad will stop adding UTF-8 BOM
<a href="http://ui.jquery.com/bugs/changeset/1090">r1090</a> - Dialog: Fixed <a href="http://dev.jqueryui.com/ticket/3638">#3638</a>: Added closeText option (default 'close').
<a href="http://ui.jquery.com/bugs/changeset/1096">r1095</a> - Sortable: fixed containment issue (with 'parent', height was miscalculated due to wrong append order)
<a href="http://ui.jquery.com/bugs/changeset/1096">r1096</a> - Sortable, Draggable: fixed issues with _convertPositionTo, missed from latest re-factor, miscalculated the absolute position including scroll
<a href="http://ui.jquery.com/bugs/changeset/1098">r1098</a> - Sortable: fixed connectToSortable option, wasn't working with Arrays as described in the documentation
<a href="http://ui.jquery.com/bugs/changeset/1136">r1136</a> - removed tree test file from trunk
<a href="http://ui.jquery.com/bugs/changeset/1145">r1145</a> - corrected some invalid html <div/> to <div></div>
<a href="http://ui.jquery.com/bugs/changeset/1156">r1156</a> - Fixed <a href="http://dev.jqueryui.com/ticket/3655">#3655</a> - $.keyCode should be $.ui.keyCode
<a href="http://ui.jquery.com/bugs/changeset/1170">r1170</a> - Sortable: accurateIntersection using outerWidth/outerHeight
<a href="http://ui.jquery.com/bugs/changeset/1171">r1171</a> - Sortable: removed default tolerance "guess" for the simplier (and better working) default mode, and the plain "pointer" intersection
<a href="http://ui.jquery.com/bugs/changeset/1173">r1173</a> - release build: Fix for <a href="http://dev.jqueryui.com/ticket/3577">#3577</a>; also fixed min target to set correct charset (UTF-8)
<a href="http://ui.jquery.com/bugs/changeset/1183">r1183</a> - Dialog: Fixed <a href="http://dev.jqueryui.com/ticket/3564">#3564</a>: Proper positioning in Opera.
<a href="http://ui.jquery.com/bugs/changeset/1184">r1184</a> - Dialog: Fixed <a href="http://dev.jqueryui.com/ticket/3221">#3221</a>: Use outerWidth/Height for positioning.
<a href="http://ui.jquery.com/bugs/changeset/1189">r1189</a> - functional demos: show instructions when navigating back to no-hash
<a href="http://ui.jquery.com/bugs/changeset/1211">r1211</a> - fixed my name and Scott's in AUTHORS.txt
<a href="http://ui.jquery.com/bugs/changeset/1212">r1212</a> - Build: Fix for <a href="http://dev.jqueryui.com/ticket/3576">#3576</a>, adding headers to minified and packed files; current solution is rather ugly, need to refactor; also removed unnecessary files from old build scripts, while adding ant-contrib-0.6.jar
<a href="http://ui.jquery.com/bugs/changeset/1213">r1213</a> - Build: Fix for <a href="http://dev.jqueryui.com/ticket/3576">#3576</a>, adding headers to minified and packed files; current solution is rather ugly, need to refactor; also removed unnecessary files from old build scripts, while adding ant-contrib-0.6.jar
<a href="http://ui.jquery.com/bugs/changeset/1214">r1214</a> - Build: Added back packed folder to replace version
<a href="http://ui.jquery.com/bugs/changeset/1245">r1245</a> - fixed alsoResize to also accept vanilla DOM nodes ( fixes <a href="http://dev.jqueryui.com/ticket/3693">#3693</a>: Resizable errors when alsoResize option is a jQuery object )
<a href="http://ui.jquery.com/bugs/changeset/1246">r1246</a> - fixed alsoResize to also accept vanilla DOM nodes ( fixes <a href="http://dev.jqueryui.com/ticket/3693">#3693</a>: Resizable errors when alsoResize option is a jQuery object )
<a href="http://ui.jquery.com/bugs/changeset/1287">r1287</a> - Adding email to AUTHORS.txt
<a href="http://ui.jquery.com/bugs/changeset/1293">r1293</a> - Fixed <a href="http://dev.jqueryui.com/ticket/3708">#3708</a> - Resizable: all classes added should have 'ui-' prefix, 'proxy' should be 'ui-resizable-helper'
<a href="http://ui.jquery.com/bugs/changeset/1319">r1319</a> - droppable: missing default for option 'accept' (set to "*" = everything)
<a href="http://ui.jquery.com/bugs/changeset/1324">r1324</a> - draggable: changed default for scroll option to true
<a href="http://ui.jquery.com/bugs/changeset/1336">r1336</a> - draggable: made connectToSortable work fine with helper: 'original' (by removing top/left properties at sort end)
<a href="http://ui.jquery.com/bugs/changeset/1375">r1375</a> - Resizable containment acurrate - Fixed <a href="http://dev.jqueryui.com/ticket/3714">#3714</a>
<a href="http://ui.jquery.com/bugs/changeset/1439">r1439</a> - release/build.xml: corrected build to place additional folder level in zip file
<a href="http://ui.jquery.com/bugs/changeset/1313">r1313</a> - draggable: fixed positioning issue with relative positioned elements relative to the body during scroll
<a href="http://ui.jquery.com/bugs/changeset/1325">r1325</a> - draggable: containment doesn't respect margins anymore (logical, and fixes <a href="http://dev.jqueryui.com/ticket/3538">#3538</a>: Sortable elements not staying inside container)
<a href="http://ui.jquery.com/bugs/changeset/1326">r1326</a> - sortable: merged draggable fixes into sortables (<a href="http://ui.jquery.com/bugs/changeset/1313">r1313</a>, <a href="http://ui.jquery.com/bugs/changeset/1325">r1325</a>)
as the rest were related to the jQuery UI CSS Framework, refactors, or new demos. That bring us up to 1.6rc3 (r1440), except for the following revs, which I wasn't able to merge
<a href="http://ui.jquery.com/bugs/changeset/1222">r1222</a> - Dialog: Setting the correct element for alsoResize.
<a href="http://ui.jquery.com/bugs/changeset/1223">r1223</a> - Dialog visual test: Removing duplicate ids.
<a href="http://ui.jquery.com/bugs/changeset/1224">r1224</a> - Dialog: Passing in a DOMElement instead of a jQuery object for alsoResize to avoid resizable bug.
<a href="http://ui.jquery.com/bugs/changeset/1225">r1225</a> - Dialog: Move to top on mousedown instead of mouseup.
<a href="http://ui.jquery.com/bugs/changeset/1226">r1226</a> - Dialog: Removed unnecessary call to moveToTop in drag start.
<a href="http://ui.jquery.com/bugs/changeset/1249">r1249</a> - Resizable: Partial fix for supporting jQuery objects in alsoResize. Dialog: Fixed bug with content resizing.
We should take a look at these over the next two weeks, as well as any others that need to be cherry-picked from the rc3-rc6 timeframe (as long as it doesn't include API or markup changes, just critical bug fixes). Thanks.
- Richard- «Prev
- Next »
Moderate user : rdworth
© 2013 jQuery Foundation
Sponsored by
and others.