是登录表单“表格数据”吗？ [英] Is a Login Form "Tabular Data"
问题描述
我正在将我的基于表格的布局转换为css定位的div - 但
只是因为我这样做是因为它被认为是最佳实践。
当我使用表格时，我真的没有看到任何奇怪的东西 - 但是
我正在这样做，因为HTML和CSS规范为表格数据保留
表格。
因此，当我将登录widgit转换为css时，我对自己说 -
嘿，这种形式肯定是表格数据。 - 即使它是
互动。它有一个逻辑标题，柱状数据类型，一个页脚 -
整个包。
所以它似乎是这样，并且应该是正确的，一个HTML表格。所以
我的问题是 - 现实世界中有什么东西说不然吗？
等等，它变得更好。
看起来，在一个结构良好的页面中，你有相同的情况。
一个页面自然地构成一个表格，并且只需遵循几个
逻辑设计规则（标题，柱状数据类型，页脚），页面
可以被视为表格数据。
多远在左侧字段中是这个吗？
规格说不使用表格进行页面布局，但他们也说
使用表格作为表格数据。当一个页面
*发生*被格式化为表格数据时哪个优先？
Sanders Kaufman < bu *** @ kaufman.netwrote in message
news：s1 ************* @ newssvr14.news.prodigy.net ...
我正在将基于表格的布局转换为css定位的divs - 但
只是因为我这样做是因为它'*被视为*最佳做法。
仅限？新格式是否会增加观众的体验？啊，我知道，你
是重构你的页面:-)
左边的字段有多远？
规格说不使用表格进行页面布局，但是他们还说使用
表格表格数据。当页面*发生时，哪个优先于
被格式化为表格数据？
数据库绝对是表格数据。它有数据字段列，
和这些字段的集合行。
表单_could_被视为表格。它有行，每个输入一个
字段。它有colums，1）输入字段本身和2）
该字段的描述，或许3）该字段中数据的验证错误。
但是，你能否适合页面？进入数据库？行在哪里？哪些是
列？
-
Richard。
< blockquote> Jukka K. Korpela写道：
Scripsit Sanders Kaufman：
>我没有真正看到使用表格时出现任何问题的地方 -
但我仍然这样做，因为HTML和CSS规范说保留
表格表格数据。
他们吗？我几次只读过几次，而且我不能回忆他们说的话。不过，这是一个很好的原则。但是很难重写工作代码的理由。
不幸的是，如果它有效，就不能修复它。原则并不适用
。标准合规性是一种销售功能。
>看起来，在一个结构良好的页面中，你有同样的情况。
一个页面自然地构成一个表格，只需遵循一些逻辑设计规则（标题，列式数据类型，页脚），就可以考虑一个页面 ;表格数据
标题？页脚？在没有URL的情况下，我判断您的页面整数不是表格数据，但您希望认为这是为了证明您使用表格来证明你的表格是合理的。布局。
这是对你没见过的代码的有趣分析。你怎么做
那个？
Sanders Kaufman schreef：
Jukka K. Korpela写道：
> Scripsit Sanders Kaufman：
>>我不知道在使用表格时会发生什么事情 -
但是我还是这么做，因为HTML和CSS规范要求保留
表格数据表。
他们呢？我几次只读过几次，我不能回忆起他们说的话。不过，这是一个很好的原则。但是，几乎没有理由重写工作代码。
不幸的是，如果它有效，就不能解决它。原则并不适用
。标准合规性是一种销售功能。
这是胡说八道。在你的第一篇文章中你说：
" ...但我唯一的理由是因为它被认为是*最好的
练习。
当我使用桌子的时候，我真的没有看到任何变态......
现在你说它是卖点功能。你是说你的客户
了解网络标准以及为什么它们是好东西，
而且你（专家）不知道这个？ />
>
>>看起来，在一个结构良好的页面中，你有相同的情况。
一页自然地结构化为表格，并且通过遵循一些逻辑设计规则（标题，柱状数据类型，页脚），页面可以被认为是表格数据。
标题？页脚？在没有URL的情况下，我判断您的页面不是表格数据，但您希望认为这是为了证明您使用表格进行布局。
这是对你没见过的代码的有趣分析。你怎么做
那个？
我和Jukka在一起。为了保持页面整体是表格数据，
也是胡说八道。你不必看任何页面的代码，知道这个。
你之前给出的例子是错误的。您可以将内容保存在数据库中
，然后将其显示在页面中，
但页面本身*不会以< table开头并以< / table>结尾;。
-
Rob
I''m converting my table-based layouts to css-positioned divs - but the
ONLY reason I''m doing it is because it''s *considered* a best practice.
I don''t really see where anything goes hinky when tables are used - but
I''m doing it anyway because the HTML and CSS specs says to reserve
tables for tabular data.
So as I convert my login widgit to a css thing, I''m saying to myself -
hey, this form is most certainly "tabular data" - even if it is
interactive. It has a logical caption, columnar data types, a footer -
the whole package.
So it seems like this is, and of right ought to be, an HTML table. So
my question is - is there anything in the real world that says otherwise?
But wait, it gets better.
It seems like, in a well structured page, you have the same situation.
A page is naturally structured as a table, and by just following a few
logical design rules (caption, columnar data types, a footer), a page
could be considered "tabular data".
How far out in left field is this?
The specs say to not use tables for page layout, but they also say to
use tables for tabular data. Which takes precedence when a page
*happens* to be formatted as tabular data?
"Sanders Kaufman" <bu***@kaufman.netwrote in message
news:s1*************@newssvr14.news.prodigy.net...
I''m converting my table-based layouts to css-positioned divs - but the
ONLY reason I''m doing it is because it''s *considered* a best practice.Only? Does the new format add to your viewers experience? Ah, I know, you
are "refactoring" your page :-)
How far out in left field is this?
The specs say to not use tables for page layout, but they also say to use
tables for tabular data. Which takes precedence when a page *happens* to
be formatted as tabular data?A database is most certainly tabular data. It has columns of data fields,
and rows of collections of those fields.
A form _could_ be considered to be tabular. It has rows, one for each input
field. It has colums, 1) the input field itself and 2)the description of
that field and perhaps 3) a validation error for the data in that field.
However, can you fit a "page" into a database? Where are the rows? Where are
the columns?
--
Richard.
Jukka K. Korpela wrote:Scripsit Sanders Kaufman:
>I don''t really see where anything goes hinky when tables are used -
but I''m doing it anyway because the HTML and CSS specs says to reserve
tables for tabular data.
Do they? I''ve only read a couple of them a few times, and I can''t
recollect where they say that. It''s a good principle, though. But hardly
a reason to rewrite working code.Unfortunately, the "if it works don''t fix it" principle doesn''t apply
here. Standards compliance is a selling feature.
>It seems like, in a well structured page, you have the same situation.
A page is naturally structured as a table, and by just following a few
logical design rules (caption, columnar data types, a footer), a page
could be considered "tabular data".
Caption? Footer? In the absence of a URL, I judge that your page as a
whole is not tabular data but you wish to think it is to justify your
use of a table for layout.That''s an interesting analysis of code you have not seen. How do you do
that?
Sanders Kaufman schreef:Jukka K. Korpela wrote:>Scripsit Sanders Kaufman:
>>I don''t really see where anything goes hinky when tables are used -
but I''m doing it anyway because the HTML and CSS specs says to reserve
tables for tabular data.
Do they? I''ve only read a couple of them a few times, and I can''t
recollect where they say that. It''s a good principle, though. But
hardly a reason to rewrite working code.
Unfortunately, the "if it works don''t fix it" principle doesn''t apply
here. Standards compliance is a selling feature.
That''s nonsense. In your first post you said:
"...but the ONLY reason I''m doing it is because it''s *considered* a best
practice.
I don''t really see where anything goes hinky when tables are used..."
Now you say it''s a selling feature. Are you saying that your clients
know about web standards and why they are a good thing,
and that you (the specialist) don''t know that?
>>>It seems like, in a well structured page, you have the same situation.
A page is naturally structured as a table, and by just following a few
logical design rules (caption, columnar data types, a footer), a page
could be considered "tabular data".
Caption? Footer? In the absence of a URL, I judge that your page as a
whole is not tabular data but you wish to think it is to justify your
use of a table for layout.
That''s an interesting analysis of code you have not seen. How do you do
that?I''m with Jukka. To maintain that a page as a whole is tabular data is
also nonsense. You don''t have to see the code of any page, to know this.
The example you gave before is wrong. You can keep content in a database
and later display it in a page,
but the page itself *does not* start with <tableand end with </table>.
--
Rob
这篇关于是登录表单“表格数据”吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
