For example, make a Visual Basic (or RealBasic if you're rabidly anti-Microsoft) form and add a scrolling textarea to it. Take a look at the properties inspector, and notice how many properties it has.
Now do the same thing in DOM. Can Javascript tell which text is selected? No. Can it set the text color, size, or font? No. (There is such a thing as a rich-text textarea, with those options, but DOM API has virtually no access to any of it.) It's simply ridiculous how incomplete DOM is, and that's where your true problems lie.
Not true - you can use the DOM Range (or proprietary TextRange in IE) to get the selected text from a textarea (admittedly it's not as straightforward as it could be), and JavaScript can access standard CSS properties to get and set the text colour, size and font. And what is this "rich-text textarea"?
Slashdot Mirror
JavaScript itself is pretty consistent between browsers. It's the DOM that varies so much.
For example, make a Visual Basic (or RealBasic if you're rabidly anti-Microsoft) form and add a scrolling textarea to it. Take a look at the properties inspector, and notice how many properties it has.
Now do the same thing in DOM. Can Javascript tell which text is selected? No. Can it set the text color, size, or font? No. (There is such a thing as a rich-text textarea, with those options, but DOM API has virtually no access to any of it.) It's simply ridiculous how incomplete DOM is, and that's where your true problems lie.
Not true - you can use the DOM Range (or proprietary TextRange in IE) to get the selected text from a textarea (admittedly it's not as straightforward as it could be), and JavaScript can access standard CSS properties to get and set the text colour, size and font. And what is this "rich-text textarea"?