Custom Query (18300 matches)
Results (145 - 147 of 18300)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#9203 | fixed | BorderContainer: rendering of dijit splitter in tundra is better to be restyled to don't use background image | ||
Description |
Hi! dijit splitter component, that is used with dijit.BorderContainer? for example, uses simple background image that looks like a simple gray line. It can be restyled without an image to look the same. For example, I would like to suggest to restyle vertical splitter .tundra .dijitSplitterV .dijitSplitterThumb { BorderContainer.css (line 53) background:transparent url(../images/splitContainerSizerV-thumb.png) no-repeat scroll 0 0; height:19px; left:1px; width:5px; } to .tundra .dijitSplitterV .dijitSplitterThumb { background:#B0B0B0 none; height:19px; left:2px; width:1px; } New splitter has the same same look as the original, but doesn't produce unnecessary HTTP image request. It is common to use horizontal and vertical spliiters, so such restyling can save 2 HTTP requests. |
|||
#9367 | invalid | #5252 resurrection | ||
Description |
Hi all! It seems that #5252 is reappeared in (at least) dojo 1.3.1. Check the test case: http://bugs.dojotoolkit.org/attachment/ticket/5252/test.html - startup fires twice! |
|||
#9567 | duplicate | BorderContainer doesn't renders properly when instantiated from inside of other widget template | ||
Description |
Hi! Please, take a look into attached test file. It creates a new widget with dojo.declare(), based on [dijit._Widget, dijit._Templated], with widgetsInTemplate:true and templateString set to a string with dijit.layout.BorderContainer? widget inside. When the widget is instatiated it is distorted and requires a call to resize() method of inner dijit.layout.BorderContainer? object instance. Try to press a button 'Call bc.resize()' to see, that after resize() instance of dijit.layout.BorderContainer? is rendered OK. This test case also demonstrates another ticket with dijit.Tooltip, that I'm going to fill in next. |