Is this the problem you are trying to fix, or the disabled options?
If the latter, I think there is a problem with your model.
Cheers,
Nick.
蝈蝈龙 wrote:
For , As I use complicated CSS, I found the page can't display
correctly in IE but it's fine in Firefox.
I prefer the generated html code is
For , As I use complicated CSS, I found the page can't display
correctly in IE but it's fine in Firefox.
I prefer the generated html code is more simple.
2007/7/5, Howard Lewis Ship <[EMAIL PROTECTED]>:
It looks like the bug, if any, is that
disabled="false"
should set the Select component'
It looks like the bug, if any, is that
disabled="false"
should set the Select component's disabled parameter to false (which
is the default), but it appears it may be set to true. Generally,
when the TypeCoercer coverts a string to a boolean, any non-blank
string is converted to true, even the
I meet the same problem.There is not any error tip.
2007/7/4, Allen Guo <[EMAIL PROTECTED]>:
Hi All,
I use select component in html template like this
The generated result is like this
bug
pet
I used the latest TP5.0.5(not snapshot). It's really very strange. Can any
Then please show the source & usage of your model.
Cheers,
Nick.
蝈蝈龙 wrote:
The same error
2007/7/4, Nick Westgate <[EMAIL PROTECTED]>:
What happens if you omit the disabled attribute?
Cheers,
Nick.
Allen Guo wrote:
> Hi All,
>
> I use select component in html template like this
>
>
The same error
2007/7/4, Nick Westgate <[EMAIL PROTECTED]>:
What happens if you omit the disabled attribute?
Cheers,
Nick.
Allen Guo wrote:
> Hi All,
>
> I use select component in html template like this
>
> The generated result is like this
>
> bug
> pet
>
>
What happens if you omit the disabled attribute?
Cheers,
Nick.
Allen Guo wrote:
> Hi All,
>
> I use select component in html template like this
> value="shop.currTemplate.backgroundImage" size="1" disabled="false"/>
> The generated result is like this
>
> bug
> pet
>
