No. The HTML 5 spec mentions:
The method and formmethod content attributes are enumerated attributes
with the following keywords and states:
The keyword get, mapping to the state GET, indicating the HTTP GET
method. The GET method should only request and retrieve data and
should have no other effect.
The keyword post, mapping to the state
POST, indicating the HTTP POST method. The POST method requests that
the server accept the submitted form's data to be processed, which may
result in an item being added to a database, the creation of a new web
page resource, the updating of the existing page, or all of the
mentioned outcomes.
The keyword dialog, mapping to the state dialog, indicating that
submitting the form is intended to close the dialog box in which the
form finds itself, if any, and otherwise not submit.
The invalid value default for these attributes is the GET state
I.e. HTML forms only support GET and POST as HTTP request methods. A workaround for this is to tunnel other methods through POST by using a hidden form field which is read by the server and the request dispatched accordingly.
However, GET, POST, PUT and DELETE are supported by the implementations of XMLHttpRequest (i.e. AJAX calls) in all the major web browsers (IE, Firefox, Safari, Chrome, Opera).
Set the parent div to position: relative
, then the inner div to...
position: absolute;
bottom: 0;
...and there you go :)
Best Answer
Most of the answers here are wrong; some work, but not for the reason they state. Here is some explanation.
This is how z-index should work according to the spec:
z-index
value to any element; if you don't, it defaults toauto
position
attribute different from the defaultstatic
) with az-index
different fromauto
create a new stacking context. Stacking contexts are the "units" of overlapping; one stacking context is either completely above the another (that is, every element of the first is above any element of the second) or completely below it.z-index
value have that value as a stack level, other elements inherit from their parents. The element with the higher stack level is displayed on top. When two elements have the same stack level, generally the one which is later in the DOM tree is painted on top. (More complicated rules apply if they have a differentposition
attribute.)In other words, when two elements have
z-index
set, in order to decide which will show on top, you need to check if they have any positioned parents which also havez-index
set. If they don't, or the parents are common, the one with the higher z-index wins. If they do, you need to compare the parents, and thez-index
of the children is irrelevant.So the
z-index
decides how the element is placed compared to other children of its "stacking parent" (the closest ancestor with az-index
set and aposition
ofrelative
,absolute
orfixed
), but it doesn't matter when comparing to other elements; it is the stacking parent'sz-index
(or possibly thez-index
of the stacking parent's stacking parent, et cetera) which counts. In a typical document where you usez-index
only on a few elements like dropdown menus and popups, none of which contains the other, the stacking parent of all the elements which have az-index
is the whole document, and you can usually get away with thinking of thez-index
as a global, document-level ordering.The fundamental difference with IE6/7 is that positioned elements start new stacking contexts, whether they have
z-index
set or not. Since the elements which you would instinctively assignz-index
values to are typically absolutely positioned and have a relatively positioned parent or close ancestor, this will mean that yourz-index
-ed elements won't be compared at all, instead their positioned ancestors will - and since those have no z-index set, document order will prevail.As a workaround, you need to find out which ancestors are actually compared, and assign some z-index to them to restore the order you want (which will usually be reverse document order). Usually this is done by javascript - for a dropdown menu, you can walk through the menu containers or parent menu items, and assign them a
z-index
of 1000, 999, 998 and so on. Another method: when a popup or dropdown menu becomes visible, find all its relatively positioned ancestors, and give them anon-top
class which has a very high z-index; when it becomes invisible again, remove the classes.