Custom Query (18300 matches)


Show under each result:

Results (22 - 24 of 18300)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#11660 wontfix OnmouseEnter/Leave ComboBox bug sjmiles zladivliba

Hi guys !

I found a real nasty bug using onmouseEnter/Leave (and onmouseover) inside a widget. Here's how to reproduce :

  • define these events for a div
  • adding Comboboxes or FilteringSelect? inside this div

Now when the user mouse pointer will onmouseOver the comboBox/FilteringSelect, the onMouseLeave event will fire on.

That means : while your pointer *is still inside the div*, where the events were defined orignally, the onmouseLeave will fire.

This should not happen when the mouse pointer is still inside the original div.

Here's a widget that will show you the problem :

<div class="F1" dojoAttachEvent="onmouseenter:ShowOptions, onmouseleave:HideOptions">

<div class="F1"> </div> <div class="F1 " dojoAttachPoint="Options" style="display:none">

<div class="F1 " dojoAttachPoint="Description"> Description

</div> <div class="F1" dojoAttachPoint="SelectItem?"></div> <div class="F4 " dojoAttachPoint="Add"></div>





dojo.require("dijit._Widget"); dojo.require("dijit._Templated"); dojo.require(""); dojo.require(""); dojo.require("dijit.form.FilteringSelect?"); dojo.require("dijit.form.ComboBox?"); dojo.require("dijit.InlineEditBox?"); dojo.require("dijit.form.Textarea"); dojo.require(""); dojo.require("dijit.form.Button"); dojo.require("dojo.fx");


[dijit._Widget,dijit._Templated], {

widgetsInTemplate:true, Mode:"Stopped", StartDate:"", Intval:"", EditTimer:null, ItemsStore:null, Store:null, DescriptionStore:null, State:"Closed", ItemsSelect:null, DescriptionBox:null,

templatePath: dojo.moduleUrl("dgets","templates/Timesheet.html"),

postMixInProperties: function(){

this.ItemsStore? = new{ url: "/te/teee"


this.DescriptionStore? = new{

url: "/te/t"


this.Store = new{

target:"/t", idAttribute:"id"



postCreate: function(){

this.ItemsSelect? = new dijit.form.FilteringSelect?({

store: this.ItemsStore?, searchAttr:"name", autoComplete:true, highlightMatch:"all", labelType:"html", required:false, onFocus: function(data){

this.State = "Opened"; console.log(this.State);

}, onBlur: function(data){

this.State = "Closed"; console.log(this.State);



this.DescriptionBox? = new dijit.form.ComboBox?({

store: this.DescriptionStore?, searchAttr:"name", autoComplete:true, hasDownArrow:false

}).placeAt(this.Description, "last");

Create the button to add the timesheet

new dijit.form.Button({

label: "Add timesheet", onClick: dojo.hitch(this, function() {





ShowOptions?: function(){



node: this.Options, duration: 500



HideOptions?: function(event){




node: this.Options, duration: 500




#11678 patchwelcome Use the TimeTextBox widget for time mesurement dante zladivliba

One of the possible use of the TimeTextBox could also be for time mesurement (aka timesheets). The widget is nearly usable in it's current state for this except one details. It allows only a 24h view.

Time mesurment would need an high or infinite time period.

I think this could be done really simply by adding a "TimeMesurement mode" in wich the widget would not scroll from 0 to 24 hours but from 0 to x hours.

This would allow another great usage for this widget !

#11824 wontfix dojo.charting not working with FF 3.5.3 for Ubuntu Eugene Lazutkin zladivliba

I've had a LOT of problems using FF under linux with dojo.charting. Usually the bugs are that nothing is shown inside a graphic. I'm parsing this piece of code :


makeCharts = function(){

        var chart1 = new dojox.charting.Chart2D("simplechart");
        chart1.addPlot("default", {type: "Lines"});
        chart1.addAxis("y", {vertical: true});
        chart1.addSeries("Series 1", [1, 2, 2, 3, 4, 5, 5, 7]);


and nothing appears inside the graph (I see the axes though). I've tested the same thing under chrome and it works.

It seems also that using an array makes the navigator bug (I never get to see the array of elements inside a graph, only the first elements).

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.