|
Re: Unclosed tags in posts (done)
by tye (Sage) on May 30, 2008 at 16:53 UTC
|
| [reply] |
|
|
| [reply]
[d/l] |
|
|
Deselecting balanced tags doesn't have much advantage (apart from enabling the fake xp nodelet on g0n's homenode), I think it's a historical feature. On the other hand, deselecting "HTML error reporting during preview", which shows the unbalanced tags and other HTML errors as grey tags can have an advantage if you write HTML using all the optional opening and closing tags the standard allows, because then perlmonks keeps complaining about unclosed tr, th, td, li, dt, dd tags (you don't ever need to close those though you can: a tr is closed by the next tr or closing the table, a th or td is closed by the next tr, td, td, or the end of the table, etc). It sometimes even complains about a missing closing p tag, like when a p tag is inside a blockquote or readmore. All those grey tags in the preview can be annoying if you mostly write correct HTML anyway.
| [reply] |
|
|
|
|
Re: Unclosed tags in posts
by ambrus (Abbot) on May 30, 2008 at 16:56 UTC
|
Do you have both "Enforce proper nesting of HTML" and "HTML error reporting during Preview" set in Display Settings?
| [reply] |
Re: Unclosed tags in posts
by kyle (Abbot) on May 30, 2008 at 17:01 UTC
|
In your Display Settings, there are options for telling you about HTML problems during preview. Have you tried those?
| [reply] |
Re: Unclosed tags in posts
by ww (Archbishop) on May 30, 2008 at 18:48 UTC
|
/me thinks blazar may have cited his typos as an example of how a problem can occur; to that, the prior answers are on point. And I think the prior answers suggest a way we could program his "auto-close," even if the poster fails to make use of the available help.
Could we not use the output of "Enforce proper nesting of HTML" and "HTML error reporting during Preview" to drive new code which would auto-close tags still improperly open at the end of a node, if the writer fails to correct them before submitting?
| [reply] |
|
|
Could we not use the output of "Enforce proper nesting of HTML" and "HTML error reporting during Preview" to drive new code which would auto-close tags still improperly open at the end of a node, if the writer fails to correct them before submitting?
Why?
if you, personally, always want to see balanced html tags, then check the box, and you will always see balanced html tags, regardless of who wrote the node, or how diligent they were about balancing their html tags.
problem solved.
if the nodes where "auto-closed" when they were created, it would be impossible to ever see the "original" node as written, which can be helpful to understand "what the hell was this person trying to say?"
Update: Absolute URL since i forgot that link shortcuts don't support relative anchors...
http://www.perlmonks.org/index.pl?node=17642#display
| [reply] |
|
|
if you, personally, always want to see balanced html tags, then check the box, and you will always see balanced html tags, regardless of who wrote the node, or how diligent they were about balancing their html tags.
I personally believe I should apologize: my fault for virtually never checking the settings. The point is, it seems there are so many of them, perhaps even too many, often with poorly chosen defaults. This is in contrast with Perl's philosophy itself, which is much about intellegently chosen defaults. Who could possibly not want to see balanced html tags? And even if one such person exists, then why is (s)he given the right to screw up the view for anyone else?
| [reply]
[d/l] |
|
|
|
|
I agree; there are many people viewing the site who aren't logged in, or who have created accounts but not got as far as the configuration yet, and putting them off would seem to be a bad idea.
| [reply] |