搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

How to leave blank instead of fill out this field?

  • 6 个回答
  • 67 人有此问题
  • 4 次查看
  • 最后回复者为 Billb114

more options

I am trying to fill out and submit a form online but firefox will not let me submit it whilst some of the fields are still blank. I must leave them blank because it is a government form. How can I turn off this guard/feature?

I am trying to fill out and submit a form online but firefox will not let me submit it whilst some of the fields are still blank. I must leave them blank because it is a government form. How can I turn off this guard/feature?

所有回复 (6)

more options

Any responses to this? I need to get my job done and will have to use IE to do it.

more options

Don't make me keep using Internet Explorer! Ahhhh!

more options

Messages about blank form fields when attempting to submit a form are usually generated by the page involved, because they want certain fields filled out and not left blank. If you don't get that same type of message when using IE, the page isn't coded correctly for both Trident and Gecko or there is a problem with the JavaScript for that form.

more options

I don't get the same message when I use IE. Page must not be coded correctly as you say. Oh well, maybe the government will start using Firefox someday. Fat chance.

more options

The input field has a "required" attribute; mine was required='no', remove it and FireFox will stop editing it. There are other ways to stop the validation process. To find out do a search on "firefox fill out this field".

more options

Not quite. Where I'm seeing a difference in FF4 is on fields that have NO required attribute set at all. We use XSL to render about 300 different web pages for some 800 internal users. The default pre-FF4 and apparently in IE8 is to make a field NOT required when no required parameter is set. Only having required="true" would make it required. In FF4 it defaults to required and that is causing a LOT of problems. Is there no way to turn that off at the browser level instead of changing code on 300 pages?