Custom Query (7259 matches)


Show under each result:

Results (52 - 54 of 7259)

Ticket Resolution Summary Owner Reporter
#4702 duplicate themes dosent support rtl AlmogBaku

all the themes by default build for ltr. for using in rtl website i need to edit the themes files..

#7121 wontfix Sortable: Document and support the object version of the placeholder option Altreus

I have used the following hack in order to customise the placeholder that Sortable uses:

  placeholder: {
    element: function(currentItem) {
    update: function(container,p) {

This hack works in all versions of UI since 1.7.2 - the one I'm using. I got the hack from StackOverflow here:

This is actually extremely useful in a variety of situations and I think it should be officially part of the API. I would suggest tweaks to this: the currentItem, for example, is not the ui.item we get in other functions. So, a bit of tweaking of the interface would be needed, but this is so amazingly useful I think it would be worth it.

#7167 wontfix Draggable: dropOnEmpty option or Sortable: repurpose same Altreus

I found a (brief!) discussion on whether dropOnEmpty should exist on Sortable. The answer was no.

It is useful; but it's the wrong way around. Currently in order to prevent a connected Draggable from being dropped on an empty sortable you have to disable the sortable whenever it becomes empty and re-enable it if it gains content (on the theory that drag+drop is not the only way of creating DOM content).

I would propose that dropOnEmpty should apply to the sortable itself, as to whether it will accept a droppable if it is empty; rather than whether its own items can be dropped onto empty others.

Alternatively, the options to Draggable should have a dropOnEmpty that does the same thing as Sortable's; i.e. prevents this draggable being dropped on an empty sortable.

The former, while preferable in my mind, has the disadvantage of not being backward-compatible.

Note: See TracQuery for help on using queries.