Fixed div top right corner

• Previous
• Overview: CSS layout
• Next

Positioning allows you to take elements out of normal document flow and make them behave differently, for example, by sitting on top of one another or by always remaining in the same place inside the browser viewport. This article explains the different position values and how to use them.

We'd like you to do the following exercises on your local computer. If possible, grab a copy of 0_basic-flow.html from our GitHub repo [source code here] and use that as a starting point.

Positioning allows us to produce interesting results by overriding normal document flow. What if you want to slightly alter the position of some boxes from their default flow position to give a slightly quirky, distressed feel? Positioning is your tool. Or what if you want to create a UI element that floats over the top of other parts of the page and/or always sits in the same place inside the browser window no matter how much the page is scrolled? Positioning makes such layout work possible.

There are a number of different types of positioning that you can put into effect on HTML elements. To make a specific type of positioning active on an element, we use the position property.

Static positioning is the default that every element gets. It just means "put the element into its normal position in the document flow nothing special to see here."

To see this [and get your example set up for future sections] first add a class of positioned to the second

in the HTML:

Now add the following rule to the bottom of your CSS:

If you save and refresh, you'll see no differenceat all, except for the updated background color of the 2nd paragraph. This is fine as we said before, static positioning is the default behavior!

Relative positioning is the first position type we'll take a look at. This is very similar to static positioning, except that once the positioned element has taken its place in the normal flow, you can then modify its final position, including making it overlap other elements on the page. Go ahead and update the position declaration in your code:

If you save and refresh at this stage, you won't see a change in the result at all. So how do you modify the element's position? You need to use the top, bottom, left, and right properties, which we'll explain in the next section.

top, bottom, left, and right are used alongside position to specify exactly where to move the positioned element to. To try this out, add the following declarations to the .positioned rule in your CSS:

If you now save and refresh, you'll get a result something like this:

Cool, huh? Ok, so this probably wasn't what you were expecting. Why has it moved to the bottom and to the right if we specified top and left? This may seem counterintuitive. You need to think of it as if there's an invisible force that pushes the specified side of the positioned box, moving it in the opposite direction. So, for example, if you specify top: 30px;, it's as if a force will push the top of the box, causing it to move downwards by 30px.

Absolute positioning brings very different results.

Let's try changing the position declaration in your code as follows:

If you now save and refresh, you should see something like so:

First of all, note that the gap where the positioned element should be in the document flow is no longer there the first and third elements have closed together like it no longer exists! Well, in a way, this is true. An absolutely positioned element no longer exists in the normal document flow. Instead, it sits on its own layer separate from everything else. This is very useful: it means that we can create isolated UI features that don't interfere with the layout of other elements on the page. For example, popup information boxes, control menus, rollover panels, UI features that can be dragged and dropped anywhere on the page, and so on.

Second, notice that the position of the element has changed. This is because top, bottom, left, and right behave in a different way with absolute positioning. Rather than positioning the element based on its relative position within the normal document flow, they specify the distance the element should be from each of the containing element'ssides. So in this case, we are saying that the absolutely positioned element should sit 30px from the top of the "containing element" and 30px from the left. [In this case, the "containing element" is theinitial containing block. See the section below for more information]

Which element is the "containing element" of an absolutely positioned element? This is very much dependent on the positionproperty of the ancestors of the positioned element [SeeIdentifying the containing block].

If no ancestor elements have theirposition property explicitly defined, then by defaultall ancestor elementswill have a static position. The result of this is the absolutely positioned element will be contained in the initial containing block. The initial containing blockhas the dimensions of the viewport andis also the block that contains the element. In other words, the absolutely positioned element will be displayed outside of the element and be positioned relative to the initial viewport.

The positioned element is nested inside the in the HTML source, but in the final layout it's 30px away from the top and the left edges of the page.We can change the positioning context, that is, which element the absolutely positioned element is positioned relative to. This is done by setting positioning on one of the element'sancestors: to one of the elements it's nested inside of [you can't position it relative to an element it's not nested inside of]. To see this, add the following declaration to your body rule:

This should give the following result:

The positioned element now sits relative to the element.

All this absolute positioning is good fun, but there's another feature we haven't considered yet. When elements start to overlap, what determines which elements appear over others and which elements appear under others? In the example we've seen so far, we only have one positioned element in the positioning context, and it appears on the top since positioned elements win over non-positioned elements. What about when we have more than one?

Try adding the following to your CSS to make the first paragraph absolutely positioned too:

At this point you'll see the first paragraph colored lime, moved out of the document flow, and positioned a bit above from where it originally was. It's also stacked below the original .positioned paragraph where the two overlap. This is because the .positioned paragraph is the second paragraph in the source order, and positioned elements later in the source order win over positioned elements earlier in the source order.

Can you change the stacking order? Yes, you can, by using the z-index property. "z-index" is a reference to the z-axis. You may recall from previous points in the course where we discussed web pages using horizontal [x-axis] and vertical [y-axis] coordinates to work out positioning for things like background images and drop shadow offsets. For languages that run left to right, [0,0] is at the top left of the page [or element], and the x- and y-axes run across to the right and down the page.

Web pages also have a z-axis: an imaginary line that runs from the surface of your screen towards your face [or whatever else you like to have in front of the screen]. z-index values affect where positioned elements sit on that axis; positive values move them higher up the stack, negative values move them lower down the stack. By default, positioned elements all have a z-index of auto, which is effectively 0.

To change the stacking order, try adding the following declaration to your p:nth-of-type[1] rule:

You should now see the lime paragraph on top:

Note that z-index only accepts unitless index values; you can't specify that you want one element to be 23 pixels up the Z-axis it doesn't work like that. Higher values will go above lower values and it's up to you what values you use. Using values of 2 or 3 would give the same effect as values of 300 or 40000.

Let's now look at fixed positioning. This works in exactly the same way as absolutepositioning, with one key difference: whereas absolute positioning fixes an element in place relative to its nearest positioned ancestor [the initial containing block if there isn't one], fixed positioning usually fixes an element in place relative to the visible portion of the viewport. [An exception to this occurs if one of the element's ancestors is a fixed containing block because its transform property has a value other than none.] This means that you can create useful UI items that are fixed in place, like persistent navigation menus that are always visible no matter how much the page scrolls.

Let's put together a simple example to show what we mean. First of all, delete the existing p:nth-of-type[1] and .positioned rules from your CSS.

Now update the body rule to remove the position: relative; declaration and add a fixed height, like so:

Now we're going to give the

element position: fixed; and have it sit at the top of the viewport. Add the following rule to your CSS:

h2 { position: fixed; top: 0; width: 500px; margin-top: 0; background: white; padding: 10px; }

The top: 0; is required to make it stick to the top of the screen. We give the heading the same width as the content column and then a white background and some padding and margin so the content won't be visible underneath it.

If you save and refresh, you'll see a fun little effect of the heading staying fixed the content appears to scroll up and disappear underneath it. But notice how some of the content is initially clipped under the heading. This is because the positioned heading no longer appears in the document flow, so the rest of the content moves up to the top. We could improve this by moving the paragraphs all down a bit. We can do this by setting some top margin on the first paragraph. Add this now:

p:nth-of-type[1] { margin-top: 60px; }

You should now see the finished example:

Fixed positioning I am a basic block level element. My adjacent block level elements sit on new lines below me. I'm not positioned any more... We are separated by our margins. Because of margin collapsing, we are separated by the width of one of our margins, not both. inline elements like this one and this one sit on the same line as one another, and adjacent text nodes, if there is space on the same line. Overflowing inline elements wrap onto a new line if possible like this one containing text, or just go on to a new line if not, much like this image will do:

body { width: 500px; height: 1400px; margin: 0 auto; } p { background: aqua; border: 3px solid blue; padding: 10px; margin: 10px; } span { background: red; border: 1px solid black; } h2 { position: fixed; top: 0px; width: 500px; background: white; padding: 10px; } p:nth-of-type[1] { margin-top: 60px; }

Note: You can see an example for this live at 6_fixed-positioning.html [see source code].

There is another position value available called position: sticky, which is somewhat newer than the others. This is basically a hybrid between relative and fixed position. It allows a positioned element to act like it's relatively positioned until it's scrolled to a certain threshold [e.g., 10px from the top of the viewport], after which it becomes fixed.

Sticky positioning can be used, for example, to cause a navigation bar to scroll with the page until a certain point and then stick to the top of the page.

An interesting and common use of position: sticky is to create a scrolling index page where different headings stick to the top of the page as they reach it. The markup for such an example might look like so:

The CSS might look as follows. In normal flow the elements will scroll with the content. When we add position: sticky to the element, along with a top value of 0, supporting browsers will stick the headings to the top of the viewport as they reach that position. Each subsequent header will then replace the previous one as it scrolls up to that position.

Sticky elements are "sticky" relative to the nearest ancestor with a "scrolling mechanism", which is determined by its ancestors' position property.

You've reached the end of this article, but can you remember the most important information? You can find some further tests to verify that you've retained this information before you move on see Test your skills: Positioning.

I'm sure you had fun playing with basic positioning. While it's not an ideal method to use for entire layouts, there are many specific objectives it's suited for.

• Previous
• Overview: CSS layout
• Next

• The position property reference.
• Practical positioning examples, for some more useful ideas.

• Introduction to CSS layout
• Normal flow
• Flexbox
• Grid
• Floats
• Positioning
• Multiple-column layout
• Responsive design
• Beginner's guide to media queries
• Legacy layout methods
• Supporting older browsers
• Fundamental layout comprehension assessment

Video liên quan