e.originalTarget not set for WebKit and Opera on start/stop handlers

The start and stop handlers appear to not pass e.originalTarget in WebKit and Opera browsers. In the example below IE and FireFox correctly see e.originalTarget as the dragged child element:

        $("#divBookListWrapper").sortable(
        {
            opacity: 0.7,
            revert: true,
            scroll: true,
            containment: "parent",
            start: function(e) {
                // have to remvoe click handler off item so drop doesn't click
                $(e.originalTarget).unbind("click");
                //$(".bookitem").unbind("click");
        },
            stop: function(e) {
                $(ctl).data("Sort", "1");
                $(ctl).html($(ctl).html().replace("Sort List", "Update Sort"));

                // reattach the item click handler
                $(e.originalTarget).click(itemClickHandler);
                //$(".bookitem").click(itemClickHandler);
            }
        });    

The layout for this setup is a <div id="divListWrapper"> with a set of <div class="bookitem"> children that are draggable.

In FireFox

{{{

$("#divBookListWrapper").sortable(

{

opacity: 0.7,

revert: true,

scroll: true,

containment: "parent",

start: function(e) {

have to remvoe click handler off item so drop doesn't click

$(e.originalTarget).unbind("click");

$(".bookitem").unbind("click");

},

stop: function(e) {

$(ctl).data("Sort", "1");

$(ctl).html($(ctl).html().replace("Sort List", "Update Sort"));

reattach the item click handler

$(e.originalTarget).click(itemClickHandler);

$(".bookitem").click(itemClickHandler);

}

});

}}

The layout is an outer <div id="divBookListWrapper"> with a set of <div class="bookitem"> children that are sortable.

It would also be nice if sortable had some optional facility to keep it from passing mouse events to the dragged item. The above code is necessary to prevent the item's click event handler to fire on drop, which is not the expected behavior.