#5034 closed defect (fixed)
Putting FilteringSelect in a span causes arrow to stop working
Reported by: | guest | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | 1.0.1 |
Component: | Dijit - Form | Version: | 1.0 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Wrapping a FilteringSelect? in a span tag causes only the very edges of the arrow "button" to work in FireFox? (2.0.0.9). See attched modified /dijit/tests/form/test_FilteringSelect.html
Attachments (1)
Change History (8)
Changed 13 years ago by
Attachment: | test_FilteringSelect.html added |
---|
comment:1 Changed 13 years ago by
Milestone: | → 1.0.1 |
---|---|
Owner: | set to Douglas Hays |
comment:2 Changed 13 years ago by
Owner: | changed from Douglas Hays to bill |
---|
This seems to be a problem with using -moz-inline-stack for tables. Thus the problem affects many/most of the form widgets. If the parent node is an inline div or a span, then the parent background covers up part of the node - and thus things like arrows don't work since you're actually clicking the parent node.
<div style="display:inline;border:2px solid red;background-color:yellow;"> <table style="display:-moz-inline-stack;border:2px solid black;"> <tr><td>this should be completely visible</td></tr> </table> </div>
It's interesting that if the parent node is an inline fieldset, then it works perfectly.
<fieldset style="display:inline;border:2px solid red;background-color:yellow;"> <table style="display:-moz-inline-stack;border:2px solid black;"> <tr><td>this should be completely visible</td></tr> </table> </fieldset>
So, the solution seems to be either to document that if you must include a form widget inside an inline element, that you should use <fieldset>, or else we could include the fieldset as part of the template, adding an additional node for each widget whether or not they have inline parents.
comment:3 Changed 13 years ago by
Owner: | changed from bill to Douglas Hays |
---|
Adding position:relative to dijitInlineTable seems to fix the problem magically.
comment:4 Changed 13 years ago by
But inline parent styling still isn't going to work unless a fieldset is used.
comment:5 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [11465]) Fixes #5042, #5034 in 1.1. The previous opacity change was good, but the ComboBox? template needed the tabIndex=-1 removed and the tundra style fixed. Added position:relative to dijitInlineBox. Removed hardcoded style from Spinner.html and ComboBox?.html templates. Changed ComboBox? to popup on mousedown over arrow and select item on mouseup to match native select.
comment:6 Changed 13 years ago by
(In [11466]) Fixes #5042, #5034 in 1.0.1. The previous opacity change was good, but the ComboBox? template needed the tabIndex=-1 removed and the tundra style fixed. Added position:relative to dijitInlineBox. Removed hardcoded style from Spinner.html and ComboBox?.html templates. Changed ComboBox? to popup on mousedown over arrow and select item on mouseup to match native select.
comment:7 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
modified dijit/tests/form/test_FilteringSelect.html (wraps first FilteringSelect? widget in <span> tag)