Template talk:DefaultFunctions
I don't see why < s > cannot be used for striking through, it provides a specific visual that may be ambiguous, but it also saves characters. Non-editors normally do not analyze the wiki's generated html source, so all your extra code does is lengthen the response packet sent by the server. I don't know about you, but I was told of the limited resources of the wiki server, and I also feel the wait time between responses. We shouldn't be getting so picky with html tags.
Popinman322 -- 20:02, 12 February 2012 (EST)
- Well, you see, the s element is used for something else. Using it for this would not necessarily have the same visual effect on every browser (just because all the major browsers make it look like this doesn't mean every single browser will). The meaning of the s tag is not to strike-through text, it is to represents contents that are no longer accurate or no longer relevant and that therefore has been “struck” from the document. (see this) I know that the wiki doesn't have that much capacity, but, sincerely, using HTML correctly is far more important than that. It's not like 50 bytes or something like that is going to change anything. Not all browsers will show it the way you expect it to if you use the s tag, and it doesn't have the correct meaning. 13 February 2012
- If you really care about this, I can make a template that strikes text the correct way and that is shorter to type than the s tag, though. 13 February 2012
- Julien, that's the reason that it's used to show deprecation in the object browser!
Popinman322 -- 21:48, 12 February 2012 (EST)- Which object browser? The one in the studio? 13 February 2012
- Anyways, you know what I think we should do? I think we should just remove them from the list instead of striking them through. 13 February 2012
- Fair enough, they shouldn't be used anyway, and you need to set a specific property to see them in the object browser anyway.
Popinman322 -- 22:02, 12 February 2012 (EST)
- Fair enough, they shouldn't be used anyway, and you need to set a specific property to see them in the object browser anyway.
- Anyways, you know what I think we should do? I think we should just remove them from the list instead of striking them through.
- Which object browser? The one in the studio?
- Julien, that's the reason that it's used to show deprecation in the object browser!
Guys, you realize this template itself is obsolete, and any pages that use it need to use the new documentation format?
Aside from that, Julien, you're wrong. The <s> tag has never had any semantic meaning - you're thinking of the <del> tag. See the Mozilla Developer Center's page on the tag.
- I'm not wrong, follow the link I put in my message. 13 February 2012
