"It behaves identifically for documents whose parsed token sequencesĪre identical". HTML 2.0 specification where requirements on aĬonforming browser or other user agent include the following: This was clearly stated as early as in the
#SUBMIT BUTTON TEXT HTML CODE#
Whether the source code contains a linebreak or a space. But it must not present it differently depending on Present text in a submit button the way it likes, perhaps in two "Incorrect behavior" refers to processing Incorrect behavior (Netscape 4.0 seems to I don't recommend relying on this incorrectīehavior, though, especially since other popular browsers have In practice, some browsers seem to treatĪ newline within such a value so that the presentation contains a lineīreak at that point. Since in attribute values, no markup (like Is in principle no way to include a line break into Moreover, there isĭisproportionately large white space on the left and But beyond some length, you get a crudeīutton, with oddly distorted border. When the text is short, you get the nicely rounded and shaded 3D button from One takes an unnecessary risk of browsers presenting it badly.Īs an illustration, the screen shot on the right shows submitīuttons with texts of varying length on IE 6 on Windows XP. INPUT TYPE="SUBMIT" element, should be relatively
The text for a normal submit button, i.e. Style sheets often ignore them for submit buttons (and otherįorm fields), since they use more or less fixed routines Notice, however, that even browsers which otherwise support Suggests presentational details with respect to submit buttons, too. You could include an author style sheet which There can be great variation between users (and browsers) īut adding variation between Web pages to that will The point is that you, as a user, can easily recognize submitīuttons when a uniform style is used for all submit buttons. Then configure things differently-for your viewing. Naturally, you may prefer some quite different style. Is a submit button as rendered by default by IE 4 while the second one The following simple screenshot illustrates this the first button Those which you code as INPUT TYPE="SUBMIT" as an author. To affect the appearance of normal submit buttons, i.e. Just as an example, the user can write a simple user's Technical problems, to be discussed later. The use of images for submit buttons causes some additional Settings, if the appearance of buttons is configurable). In its way, which is what its users are accustomed to if theyĭon't like them esthetically, they need to consider whether the dislike
To let a user agent present those buttons Users recognize submit buttons as submit buttons. The crucial thing in the useability of forms in visual The desire to present buttons in some particular way in graphicĬontexts is itself understandable. Instead, they know what will happenīased on earlier experience. Principles: when things always behave the same, users don't have to Moreover, there are user interfaces where the "line"Ĭoncept is vague at least what does a line break mean in speechĪnd on the WWW, that means compliance with Makes no sense, although the logical concept of form submission
On the Web in many environments where "button" as a visual concept Use image buttons, namely the desire to make buttons "look better"įirst we should understand the inherent limitations caused by The same applies to the more common desire which makes authors Why that would create problems instead of solving them. This document explains, among other things, Which is displayed in a button-like manner and which causes submission Where the questioner assumably was using an element in a This text was originally written as a response to a news article Why? | Why not? | Styles | Line break in normal submit button text? | How? | What about "tooltips"? | Technical problems and notes | Side effect: what really gets submitted | Notes on the JavaScript surrogate | Rollover effects Why? (and multi-line texts in normal submit buttons)Īnd multi-line texts in normal submit buttons