netscape砍掉我的b [英] netscape chops off my b's
问题描述
嗨。
为什么netscape在这个例子中切断了b'的底部（参见
以下）？
似乎工作正常吗？注意：我的主要目标是能够在输入字段中使用
8点文本。
谢谢。 er*******@rcn.com
这里这是一个例子：
< html>< head>< style>
输入{height：12pt; font-size：8pt}
body {font-size：8pt}
< / style>< / head>
< body>
为什么这些b'会在netscape 7.01的底部被砍掉？ ：
<输入类型=文字大小= 30值=" bbb">
< / body>< / html>
Eric Osman写道：
为什么netscape会切断b'的底部例子（见下面的
）？
似乎工作正常吗？注意：我的主要目标是能够在输入字段中使用
8点文本。
在WWW上使用pt单位的字体大小是一个糟糕的选择，特别是在这样的小尺寸的b $ b。之前有很多关于此的内容，
使用Google了解详情。简而言之，您的访问者比您更了解
他们更喜欢阅读的文字大小，并且可能会覆盖他们的决定
使网站难以理解。坚持像em或％的相对单位，
并且不要低于正常水平。
此外，如果你在输入元素上设置一个高度当你的访问者使用
浏览器让他们忽略你的字体大小时，事情会变得更糟（这就是那些
功能在浏览器中是因为作者正在做你正在做的事情！$ / b
< html>
我知道我开始听起来像是一张卡住的唱片，但*请*在你的帮助之前*验证
你的代码。它可以节省您的时间和我们的时间。
在这种特殊情况下，验证器会告诉您没有
有doctype。没有doctype将浏览器踢入Quirks
mode。 Quirks模式意味着浏览器假定您没有编码
标准，并且故意搞砸了代码的渲染。
这个bug似乎是故意误导之一。代码为
标准，以及bug消失。或者，如果你是一个受虐狂并希望
继续使用怪癖模式，你可以通过在该元素上明确设置边界
来解决它。
（另一个添加到标准==未来兼容性列表）。
-
Jim Dabell
我在一些旧电子邮件中找到的一个验证器是通过将
放在以下代码片段后激活的你的网页，然后点击
html或css链接。
然而，不幸的是，即使我正在运行一个apache web服务器
我的家用机器，当我点击链接时，验证站点说它
无法访问我的页面。这是一个拖累，因为如果我必须使用ftp将
页面复制到远程Web服务器上，那么每当我修复验证器抱怨的某些内容时，我就会知道， ''必须将新文件ftp到
远程Web服务器，这比仅在我的本地apache服务器上运行
页面要繁琐得多。
你们中的任何人都知道apache web服务器以及为什么它可能不允许在我的本地apache web服务器上访问我的页面更多的网站？
嗯，我想知道我的isp（即rcn.com）是否禁止访问我的
本地网络服务器????
无论如何，这里是我找到的验证器片段：
< a
href =" http：//validator.w3.org/ check / referer">< img
style =" border：0;宽度：88px;身高：31px"
src =" http://validator.w3.org/images/vh40"
alt ="有效HTML
4.0！ height = 31 width = 88>< / a>< br>
< a
href =" http://jigsaw.w3.org/css -validator / check / referer">< img
style =" border：0;宽度：88px;身高：31px"
src =" http://jigsaw.w3.org/css-validator/images/vcss.gif"
alt = 有效
CSS！"< / a>
Eric Osman写道：
Jim，感谢您的回复。
以下任何一项都会使您的回复更有用：
o有关验证的一些细节。代码。这是用特定的网站完成的吗？如果是的话，你能说出哪一个？或者用工具完成了吗？多少钱 ？或者你在谈论手动
验证？
o解决问题的一个工作示例也会有所帮助，或者至少有一些关于我的代码中需要修改的内容的一些提示它。
o你提到不使用磅值。如果需要，我愿意使用不同的
单位。在我的情况下，想要选择一些小尺寸的原因是表格是从最初适合纸张两面的纸张形式转换而来的。我正在努力
使纸张的网页版本仅在纸张的两面打印
当打印时在浏览器中被选中。
/ Eric
Jim Dabell写道：
Eric Osman写道：
为什么netscape在这个例子中切掉了b'的底部（见下面的
）？
似乎工作得很好ie ？注意：我的主要目标是能够在输入字段中使用
8点文本。
在WWW上使用pt单位的字体大小是一个糟糕的选择，尤其是
这样的小尺寸。在此之前已经有很多关于此的内容了，
使用Google了解详情。简而言之，您的访问者比您更了解
他们喜欢阅读的文字大小，并且压倒他们的决定可能会使网站难以理解。坚持像em或％相对单位，
并且远远低于正常水平。
此外，如果你用pt单位设置输入元素的高度，
当访问者使用允许他们忽略你的字体大小的浏览器时，情况会变得更糟（浏览器中这些功能的原因是因为作者做的正是你所做的那样/>正在做！）。
< html>
我知道我开始听起来像一张卡住的记录，但是*在请求帮助之前，请*验证您的代码。它节省了您的时间和我们的时间。
在这种特殊情况下，验证器会告诉您没有
有doctype。没有doctype将浏览器踢入Quirks
mode。 Quirks模式意味着浏览器假定您没有编写
标准，并故意搞砸了代码的呈现。
这个bug似乎是故意误导之一。代码为
标准，以及bug。消失。或者，如果你是一个受虐狂并想要保持怪癖模式，你可以通过在该元素上明确设置边界来解决它。
（另一个添加到标准==未来兼容性列表。）
Eric Osman写道：
但是，不幸的是，即使我在家用机器上运行了一个apache web服务器，当我点击链接时，验证站点说它无法访问我的页。
验证者无法访问您的localhost（127.0.0.1）。你必须
计算你从ISP收到的IP（在Windows上它是ipconfig
或winipcfg）。如果您的服务器允许来自
远程主机的连接，那么它应该可以使用该IP。
这是一个阻力，因为如果我必须将
页面复制到一个带有ftp的远程Web服务器，然后每当我修复验证器抱怨的东西时，我都要将新文件ftp到
远程Web服务器，这比单纯的繁琐得多在我当地的apache服务器上运行
页面。
使用Opera浏览器。使用ctrl-alt-v，您可以将整个页面发送到
W3C-validator而无需将其上传到您的远程服务器（还有
仍然是最近的问题Opera在使用内容协商时，但是
不过它应该是一个很好的起点）。
Micha
Hi.
Why does netscape chop off the bottom of the b''s in this example (see
below) ?
It seems to work fine in ie ? NOTE: My main goal is to be able to use
8 point text in my input fields.
Thanks. er*******@rcn.com
Here''s the example:
<html><head><style>
input {height:12pt; font-size: 8pt}
body {font-size:8pt}
</style></head>
<body>
Why do these b''s get chopped off on the bottom in netscape 7.01 ? :
<input type=text size=30 value="bbb">
</body></html>
Eric Osman wrote:
Why does netscape chop off the bottom of the b''s in this example (see
below) ?
It seems to work fine in ie ? NOTE: My main goal is to be able to use
8 point text in my input fields.
Using pt units for font size is a poor choice on the WWW, especially at such
small sizes. There''s plenty that has been said about that in here before,
use Google for details. In short, your visitor knows better than you do
what size text they prefer to read, and overriding their decision may well
make the site unreadable for them. Stick to relative units like em or %,
and don''t go far below normal.
Furthermore, if you are setting a height on input elements with pt units,
then things are going to get even worse when your visitors are using
browsers that allow them to ignore your font sizes (the very reason those
features are in the browsers is because of authors doing exactly what you
are doing!).
<html>
I know I''m beginning to sound like a stuck record, but *please* validate
your code before asking for help. It saves your time and ours.
In this particular case, the validator would have told you off for not
having a doctype. Not having a doctype kicks the browser into "Quirks
mode". "Quirks mode" means the browser assumes you aren''t coding for
standards, and intentionally screws up the rendering of your code.
This "bug" appears to be one of those intentional misrenderings. Code to
standards, and the "bug" disappears. Or, if you are a masochist and want
to stay with quirks mode, you can work around it by setting a border
explicitly on that element.
(Another to add to the "standards == future compatibility" list).
--
Jim Dabell
One validator I found in some old email is activated by putting the
following code snippet on your web page and then clicking on either the
html or the css link.
However, unfortunately even though I''m running an apache web server on
my home machine, when I click on the link, the validator site says it
can''t access my page. This is a drag, because if I have to copy the
page onto a remote web server with ftp, then every time I fix something
that the validator complains about, i''ll have to ftp the new file to the
remote web server, which is much more tedious than merely running the
page on my local apache server.
Any of you know about apache web server and why it might not be allowing
more sites to access my pages here on my local apache web server ?
Hmmm, I wonder if my isp (which is rcn.com) is disallowing access to my
local web server ????
Anyway, here''s the validator snippet that I found:
<a
href="http://validator.w3.org/check/referer"><img
style="border:0; width:88px; height:31px"
src="http://validator.w3.org/images/vh40"
alt="Valid HTML
4.0!" height=31 width=88></a><br>
<a
href="http://jigsaw.w3.org/css-validator/check/referer"><img
style="border:0; width:88px; height:31px"
src="http://jigsaw.w3.org/css-validator/images/vcss.gif"
alt="Valid
CSS!"></a>
Eric Osman wrote:
Jim, thanks for your response.
Any of the following, however, would have made your response more useful:
o Some specifics about "validating" the code. Is this done with a
particular web site ? If so, can you please say which one ? Or is it
done with a tool ? How much money ? Or are you talking about manual
validation ?
o A working example that solves the problem would help too, or at
least some hints about what to change in my code to fix it.
o You mention not using point sizes. I''m willing to use different
units if need be. In my case, the reason for wanting to choose some
small size is that the form was converted from a paper form that
originally fit on two sides of a piece of paper. I''m trying very hard
to make the web version of the form print on only two sides of a paper
when "print" is chosen in the browser.
/Eric
Jim Dabell wrote:Eric Osman wrote:Why does netscape chop off the bottom of the b''s in this example (see
below) ?
It seems to work fine in ie ? NOTE: My main goal is to be able to use
8 point text in my input fields.
Using pt units for font size is a poor choice on the WWW, especially
at such
small sizes. There''s plenty that has been said about that in here
before,
use Google for details. In short, your visitor knows better than you do
what size text they prefer to read, and overriding their decision may
well
make the site unreadable for them. Stick to relative units like em or %,
and don''t go far below normal.
Furthermore, if you are setting a height on input elements with pt units,
then things are going to get even worse when your visitors are using
browsers that allow them to ignore your font sizes (the very reason those
features are in the browsers is because of authors doing exactly what you
are doing!).
<html>
I know I''m beginning to sound like a stuck record, but *please* validate
your code before asking for help. It saves your time and ours.
In this particular case, the validator would have told you off for not
having a doctype. Not having a doctype kicks the browser into "Quirks
mode". "Quirks mode" means the browser assumes you aren''t coding for
standards, and intentionally screws up the rendering of your code.
This "bug" appears to be one of those intentional misrenderings. Code to
standards, and the "bug" disappears. Or, if you are a masochist and want
to stay with quirks mode, you can work around it by setting a border
explicitly on that element.
(Another to add to the "standards == future compatibility" list).
Eric Osman wrote:
However, unfortunately even though I''m running an apache web server on
my home machine, when I click on the link, the validator site says it
can''t access my page.
The validator can''t access your localhost (127.0.0.1). You have to
figure out the IP you received from your ISP (on Windows it''s ipconfig
or winipcfg for example). If your server allows connections from
remote hosts then it should work with that IP.
This is a drag, because if I have to copy the
page onto a remote web server with ftp, then every time I fix something
that the validator complains about, i''ll have to ftp the new file to the
remote web server, which is much more tedious than merely running the
page on my local apache server.
Use the Opera browser. With ctrl-alt-v you can send the whole page to
the W3C-validator without uploading it to your remote server (there''s
still a problem with recent Opera when using content negotiation, but
nevertheless it should be a good starting point).
Micha
这篇关于netscape砍掉我的b的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
