I want to know whether it is advisable by sitepoint 's members and gurus to use marquee tag in html or not ?
Could I use it as I’m not good at either javascript or flash. So I wanna use marquee for some of line movement.
But as far as I know and have read, by using that tag, html or xhtml document will become invalid.
So I want to know what are the consequences of using it and whether to go for it or not as almost all the browser support this feature.
Definitely learn JavaScript first. JQuery is written in JavaScript any you will not be able to use it properly if you don’t understand javaScript first.
Learn JavaScript before jQuery, You should understand the fundamentals before you use some third party tool to make the process smoother 
Well thanx all for the advice.
Now I’m seriously thinking to learn some of javascript, and dun wanna give any escape value to it and won’t search for any shortcut of it.
for me learning javascript is bit wayward, so I’m thinking to straight dive into jquery, as it seems much simpler to me.
What are the advices of yours’ all ?
[FONT=Verdana][SIZE=2]Err... the MARQUEE Element was never really 'deprecated' because it was M$ Proprietary nonsense in the first place and never made a final Technical Recommendation. (Unless you mean deprecated by somebody other than the W3C) or you were referring to: http://www.w3.org/TR/css3-marquee/ .[/SIZE][/FONT]
Using MARQUEE would also make printing the scrolling content near impossible.
don’t do it
it will make your web page look <blink>cheesy</blink>
If you want a marquee then you should use JavaScript to create it properly.
You shouldn’t use marquee’s of any sort (IMO), talk about usability / readability issues. If the text scrolls too slowly the rest is unreadable, if it scrolls too fast it’s unreadable and if your ability to read is based on “hover moving” the content, it’ll be a serious accessibility violation for people with motor function deficiencies (as balanced mouse movement is required). Don’t animate things on the page unless you really have to. 
Any sensibly coded JavaScript marquee stops moving as soon as the mouse moves over it and only starts moving again when the mouse moves off of it.
That’s still insufficient for anyone who can’t use a pointing device. I have yet to see moving text or images that are keyboard accessible. They may be out there, but they’re few and far between.
cheers,
gary
And not only is that totally useless for those without a pointing device (as gary pointed out - which is a surprising number of people) and for those who use Braille assisted devices and screen readers (without mice) to allow them to surf the web effectively, you might have missed the part of my post speaking about motor function deficiencies to which I stated that for such a hover effect, a “balanced mouse movement is required” - as in people need to be able to hold a mouse over a marquee and maintain that position until their done reading… which clearly is going to be next to impossible for people with muscle spasms, muscular dystrophy, Wittmaack-Ekbom’s syndrome (RLS) - which also affects arms, severe forms of arthritis and a whole range of cognitive disorders.
The marquee tag is deprecated. As well, it was a presentational tag that didn’t define the intended content, and also caused usability/readability issues as the others have already stated. So to answer your question, you should avoid this tag at all costs.
Presumably with JavaScript where all it is doing is moving the content on the screen such a script should have no impact on those using those devices where the marquee content should be static.
It would be only those who actually view it on screen with JavaScript enabled who would have difficulties since as they tab through the links the one they are currently at may or may not be in the visible part of the marquee. They might have some difficulty in telling exactly which link they are on before hitting enter.
It shouldn’t be a major issue provided that everything available through the marquee can also be accessed some other way for those who can’t interact with the marquee properly. Then the marquee would just be an extra way for those who can use it to get to where they are going.
Not if you use the JavaScript or CSS 3 versions of marquee (which are the only ones that have ever been in the standards). JavaScript never runs on paper and CSS can be coded for specific media so in both cases you just get the static version of the content the same as people using browsers that don’t support JavaScript or CSS 3 get. You can even style it differently for paper using CSS so as to get it to print how you want.
Yes, I was just referring to the nonsense M$ Propriety MARQUEE Element only (with regards to post #13 and print, issues, etc.). It had already been clarified post #5 there were better alternatives and so forth - I did read it beforehand. It just probably read a little “strange”.
I was just clarifying the fact that by not using iproprietary tags in the HTML to get the effect that you have better control and can treat the content differently for print - something which as you pointed out can’t be done with the proprietary microsoft tag.
…
The marquee tag is a non-standard HTML element which causes text to scroll up, down, left or right automatically. The tag was first introduced in early versions of Microsoft’s Internet Explorer, and was compared to Netscape’s blink element, as a proprietary non-standard extension to the HTML standard with usability problems. It is deprecated by the W3C and not advised by them for use in any HTML documents.
It is deprecated by the W3C and not advised by them for use in any HTML documents.
Where does that quote come from?
To the best of my knowledge the only proprietary tag that the W3C officially deprecated was <iframe> as that is the only proprietary tag that got added to the HTML 4 transitional standard that wasn’t a tag in HTML 3.2 The rest of the deprecated tags were all HTML 3.2 tags that was no longer required and thus was removed from HTML 4 but temporarily allowed while people transitioned from HTML 3.2 to HTML 4.
He quoted it from Wikipedia… and it’s un-cited (the information is inaccurate). The W3C didn’t deprecate it because they never supported it in the first place. However they did classify the element as obsolete in the development specification for HTML5 (as there’s better ways to achieve it). I still am totally against it’s implementation because there’s still obvious accessibility issues for those with cognitive or motor function impairments.
Source: http://en.wikipedia.org/wiki/Marquee_element
Citation: http://dev.w3.org/html5/spec/obsolete.html#the-marquee-element
If you try to ship a browser without support for marquee then you would probably lose all market share in China and other Asian countries where it’s being used quite a lot.
Users can disable marquee in the browser. It’s harder to disable scripted scrolling text.