OK, misunderstood due to my fast reading. I just tried this in
mooshell and it seems to work.
$('myselect').addEvent('change', function(){
if($("myselect").getElement(":selected")) {
$("option-resut").set("text", $("myselect").getElement
(":selected").text)
}
else {
$("option-resut").set("text", "not found")
}
});
On Oct 23, 12:35 pm, Sanford Whiteman <[email protected]>
wrote:
> CroNiX, Savageman, you're missing the point.
>
> MT Selectors allow you to use late-model W3C CSS syntax to get Element
> collections, even if the hosting browser does not support all the
> selectors in its native CSS parser. By virtue of being open-source,
> they also allow you to create and use custom pseudo-classes that may
> appear to use CSS syntax, but actually are invalid CSS. Thus
> ':selected' may be formatted similarly, but that pseudo is not in the
> W3C CSS spec, thus it is invalid CSS.
>
> That would be more explicable to me if there were no valid CSS that
> would get the same Elements. Only there is valid CSS here. I think if
> you are using a CSS parser, you should use valid CSS unless [a] it is
> absolutely impossible and_ [b] you feel compelled to keep using
> Selectors (perhaps for standardization in your app) instead of simply
> using DOM methods/conveniences that don't pretend to be CSS. I don't
> know why you would use fake CSS otherwise. That is a slippery slope
> toward, say, creating a custom pseudo-class ":myfavoriteanchor" that
> is exactly equivalent to "ul li a.favorite.enabled" but "easier" to
> type or whatever. Next thing you know, your so-called selectors are
> riddled w/fake CSS. And you can't style them using a real stylesheet.
> So you have to create styling functions to apply Element styles using
> JS. I mean, ugh....
>
> -- Sandy
