[wp-hackers] widget select field problems?

[Stephanie Leary]

On Aug 3, 2009, at 9:05 PM, Andrew Ozz wrote:
> Each widget is reloaded after saving. If you look in the ajax return  
> (easily done in Firebug), does the html look ok?

Yes. Here's the return:
<p><label for="widget-randompostsfromcategory-3-content">Display:</ 
label>
<select id="widget-randompostsfromcategory-3-content" name="widget- 
randompostsfromcategory[3][content]" />
    <option value="title" >Title Only</option>
    <option value="excerpt"  selected="selected" >Title and Excerpt</ 
option>
    <option value="content" >Title and Content</option>
</select></p>
Here's what actually shows up:

<p><label for="widget-randompostsfromcategory-3-content">Display:</ 
label>
			<select name="widget-randompostsfromcategory[3][content]"  
id="widget-randompostsfromcategory-3-content"/>
                 Title Only
                 Title and Excerpt
                 Title and Content
             </p>

(I hadn't noticed until just now that the </select> tag is missing as  
well as the <option>s. How bizarre!)

> There's also a js function to remove the for=".." attribute from all  
> labels that have nested form elements like these:
> <label for="baz"><input id="baz" ... /></label> since they are not  
> needed there and seem to trigger a bug in sortable.js where nothing  
> in the widget can be selected. Don't think that interferes with the  
> selects.

Interesting! Not an issue here, though.

Want me to file this as a bug?


Stephanie Leary
sillybean.net