Well it’s evil, fine.
But what’s evil in it?
- all browsers support it?
- which aspx asp.net controls can I not use in this tag?
Why not use the tag?
Well it’s evil, fine. But what’s evil in it? all browsers support it? which
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Well it’s evil, fine.
But what’s evil in it?
Why not use the tag?
No, although support is annoyingly broad.
Can you rephrase this. I think I can decrypt the meaning of ‘taag’, but the words don’t form a sentence.
First and foremost, on a purely practical front — it makes text scroll.
Scrolling text is an excellent way to display a large amount of information in a small place, non-interactively. This makes it rather good for things like the “What stations this train will stop at” display that I get to look at on my commute.
A web page, however, is typically viewed in a relatively large display by a single person, who has a mouse, trackpad or other way to indicate when they have finished reading whatever is displayed. This means they do not have to wait for the start of the text, the text will not move faster then they can read properly, and the text will not move more slowly then they are comfortable with. Additionally, if they are trying to read something else that is near the scrolling text, they won’t be constantly distracted by the movement in the corner of their eye.
Aside from that. It isn’t yet standardized, and the closest it appears it will ever come is to be marked as obsolete by HTML 5.