In case HTML changes the spec one day...
-
public const string HtmlTableTag = "table"; public const string HtmlRowTag = "tr"; public const string HtmlCellTag = "td";
Hey, you never know. Maybe HTML6 will go with "grid" for that.
-
Soon
public const string HtmlTableTagIdAttribute = "id"; public const string HtmlTableTagClassAttribute = "class"; public const string HtmlTableTagStyleAttribute = "style"; ... public const string HtmlRowTagIdAttribute = "id"; public const string HtmlRowTagClassAttribute = "class"; public const string HtmlRowTagStyleAttribute = "stlye"; ... public const string HtmlCellTagIdAttribute = "id"; public const string HtmlCellTagClassAttribute = "class"; public const string HtmlCellTagStyleAttribute = "style"; ...
spelling mistake intentional.
-
Hey, you never know. Maybe HTML6 will go with "grid" for that.
Or obsolete the concept entirely.
-
And
public const string HtmlTableTagDelimiterStart = "<"; public const string HtmlTableTagDelimiterEnd = ">"; public const string HtmlTableTagInternalSeparator = " ";
-
public const string HtmlTableTagIdAttributeLeftDelimiter = """;
public const string HtmlTableTagIdAttributeRightDelimiter = """;
-
public const string HtmlClosingTagSlashWindows = "\\"; public const string HtmlClosingTagSlashUNIX = "/";
... how do you mean "No!"?
-
public const string HtmlClosingTagSlashWindows = "\";
public const string HtmlClosingTagSlashWindowsDoNotUse = "\\";//See ISSUE-2106/6 for why
-
Hey! Discourse escaped my escape! See? SEE? We DO need it!
-
Hey, you never know. Maybe HTML6 will go with "grid" for that
What's he doing about "tbody" and "tfoot" and "thead"; and what if they add more section delimiters than those. He needs some extra tags reserved to handle that case.
Clearly a noob.
-
Hey, don't mock. I bet the poor soul has a manager that says "STATIC CODE ANALYSIS!", and we all know those tools hate 'magic' values.
-
Seriously guys? 73 of you didn't know about that? And cared enough to click that link?!‽
-
I think I knew about some of those. Honestly, I don't keep up with web standards, because I don't have a reason to.
-
73 of you didn't know about that?
10 people tried to highlight to quote reply and got codingwhorror-fucked by javascript auto-open triggering link follows.
90 times now.
-
Seriously guys? 73 of you didn't know about that? And cared enough to click that link?!‽
Maybe it was just one person who clicked the link 73 times.
-
Maybe it was just one person who clicked the link 73 times.
I'm certain that casual abuse like that is taken care of. And if someone is that bored they want to find 73 different proxies and go spamming clicks, more power to them.
-
Seriously guys? 73 of you didn't know about that? And cared enough to click that link?!‽
Yeah... 'fessing up to being stupid, the hell am I looking for? Only thing I see about tables is removing some attributes that should be replaced by CSS.
-
Only thing I see about tables
I was more referring to - in 5's case - the removal of frames, while leaving iframes alone. (I'm aware of the reasons, for those keen to point them out, thanks.)
-
Ah.
Wait, that's new? I thought even W3C figured out frames are a spawn of
Satansecure mediation framework and should be taken behind the barn and shot years ago.
-
Previously deprecated. 5 made it obsolete by taking it behind the barn...
-
As seen in C#:
private string stringQuotifier = "'"; // does not protect against SQL injection!
-
For science!
Before Clicking
After clicking + <--Back
After Clicking Again
However
After page reload
So yes, it does have some user recognition.
-