Ask a Question related to Macromedia Dynamic HTML, Design and Development.
-
johnegbert #1
RELATIVE LAYERS..... take up space even when invisible?
hey guys,
I am trying to make this stupid like, drop down menu type thing, pretty much I
have a layer that i am showing and hiding when I click a button, but I cannot
for the life of me figure out how to get this thing positioned correctly. I am
currently positioning it relatively (instead of absolutely) to the button that
is making it appear and dissapear, which works perfectly for positioning
purposes. ..... BUT... whenever I have it set on invisible (or I have the
button "unclicked" I leaves a huge gaping hole in the middle of my page. I
want this sucker to layer over the top of the content and not make its own
space....
how do i do this people? it would work with the "absolute" attribute but all
of us developers know that absolute is realitive to screen size and what not.
The project I am currently working on just so happens to require a centered
table in the middle of the screen for the content. so no such luck with the
absolute thing.
HELP?!?!??!?!?!
johnegbert Guest
-
Prob. with Absolute/Relative Positioning of Layers
I'm using the List-u-Like generator to create a menu (http://www.listulike.com/generator/) for this page that I created in Dreamweaver:... -
relative vs abolute position with layers in liquidinterface
:confused; Newbie here. I've got a 2 column table in an editable area of a page created from a template. In column 1 there is a roll over... -
blend texture layers relative to camera distance
I have some terrain models with high-res satellite images in texture layer 1. They look great from a distance, but when the camera is close to the... -
Relative positon to layers
Layers are a wonderful way of building up ones web page. I would like to apply a relative position to these layers. Could somebody advise me how... -
document relative/site root relative linking
It used to be that DW had a much, much better memory of what your last selection was, re: root v. document. MX now seems to get confused much more... -
Murray *TMM* #2 Re: RELATIVE LAYERS..... take up space even when invisible?
This may help you understand positioning a bit -
There are 4 different types of positioning:
Absolute
Relative
Fixed
Static
Here is a brief explanation of each kind....
Position:absolute
-----------------------
This does several things -
1. It 'removes' the element from the flow of the code on the* page so that
it can no longer influence the size or position of any other pa*ge element
(except for those contained within it, of course).
2. The absolutely positioned element takes its position from the position of
its closest PA*RENT *positioned*
element - in the absence of any explicitly positioned parent, this will
default to the <body> tag, which is always positioned *at 0,0 in the browser
viewport.
This means that it doesn't matter where in the HTML code the laye*r's code
appears (between <body> and </body>), its location on the screen will not
change. Furthe*rmore, the
space in which this element would have appeared were it not positi*oned is
not
preserved on the screen. In other words, absolutely positioned elements
don't take up any space on the page. In fact, they FLOAT over the page.
Position:relative
----------------------
In contrast to absolute positioning, a relatively positioned page element is
*not* removed from t*he flow of the
code on the page, so it will use the spot where it would have* appeared
based
on its position in the code as its zero point reference. If* you then
supply top, right, bottom, or left positions to the style for this *element,
those
values will be used as offsets from its zero point.
This means that it DOES matter where in the code the relativ*ely positioned
element appears, as it will be positioned in that location (*factoring in
the offsets) on the screen. Furthermore, the space where this e*lement
would
have appeared is preserved in the display, and can therefore* affect the
placement of succeeding elements. This means that the taller a relatively
positioned element is, the more space it forces on the page.
Position:static
-------------------
As with relative position, static positions also "go with *the flow". An
element with a static position cannot have values for offset*s (top, right,
left, bottom) or if it has them, they will be ignored. Unless explicitly
positioned, all div elements default to static positioning.
Position:fixed
------------------
A page element with this style will not scroll as the page c*ontent scrolls.
Support for this in elements other than page backgrounds is *quirky
There are two other things you need to know:
1. ANY page element can be positioned - paragraphs, tables, images, lists,
etc.
2. The <div> tag is a BLOCK level tag. This means that if it is not
positioned or explicitly styled otherwise, a) it will always begin on a new
line on the screen, and b) it will always force content to a new line below
it, and c) it will always take up the entire width of its container (i.e.,
width:100%).
You can see a good example of the essential difference between absolute and
relative positioning here -
[url]http://www.great-web-sights.com/g_layersdemo.asp[/url]
--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================
"johnegbert" <webforumsuser@macromedia.com> wrote in message
news:deo5jr$ht5$1@forums.macromedia.com...> hey guys,
> I am trying to make this stupid like, drop down menu type thing, pretty
> much I
> have a layer that i am showing and hiding when I click a button, but I
> cannot
> for the life of me figure out how to get this thing positioned correctly.
> I am
> currently positioning it relatively (instead of absolutely) to the button
> that
> is making it appear and dissapear, which works perfectly for positioning
> purposes. ..... BUT... whenever I have it set on invisible (or I have the
> button "unclicked" I leaves a huge gaping hole in the middle of my page.
> I
> want this sucker to layer over the top of the content and not make its own
> space....
>
> how do i do this people? it would work with the "absolute" attribute but
> all
> of us developers know that absolute is realitive to screen size and what
> not.
> The project I am currently working on just so happens to require a
> centered
> table in the middle of the screen for the content. so no such luck with
> the
> absolute thing.
>
> HELP?!?!??!?!?!
>
Murray *TMM* Guest
-
rob::db #3 Re: RELATIVE LAYERS..... take up space even when invisible?
It may be better to use display:none and display:block instead of
visibility:hidden and visibility:visible.
johnegbert wrote:> hey guys,
> I am trying to make this stupid like, drop down menu type thing,
> pretty much I have a layer that i am showing and hiding when I click
> a button, but I cannot for the life of me figure out how to get this
> thing positioned correctly. I am currently positioning it relatively
> (instead of absolutely) to the button that is making it appear and
> dissapear, which works perfectly for positioning purposes. .....
> BUT... whenever I have it set on invisible (or I have the button
> "unclicked" I leaves a huge gaping hole in the middle of my page. I
> want this sucker to layer over the top of the content and not make
> its own space....
>
> how do i do this people? it would work with the "absolute" attribute
> but all of us developers know that absolute is realitive to screen
> size and what not. The project I am currently working on just so
> happens to require a centered table in the middle of the screen for
> the content. so no such luck with the absolute thing.
>
> HELP?!?!??!?!?!
rob::db Guest
Reply With QuoteSimilar Questions and Discussions
Posting Permissions
- You may not post new threads
- You may post replies
- You may not post attachments
- You may not edit your posts
