Adding a Layer (absolute position div) to a locked page

Maybe I am just not understanding templates but I have a
really simple one that has one editable region called "content". I
want to add a absolute positioned div to the content area but DW
tells me this would require changing code that is locked by the
template. I thought that the editable area automatically put in by
DW would accommodate the added code (css) that DW puts in when
adding a template to the page.
So what is the Editable area called "Head" used for anyways
if not for situations like this?
Thanks

Here's the problem with layers in template child pages, and a
simple
solution.
When you DRAG a layer onto the page in DW (this means you
click on the layer
icon in the Insert Toolbar and drag the layer on the page),
DW wants to put
the code for that layer immediately under the body tag, e.g.,
BEFORE DRAG -
<body...>
<table>
AFTER DRAG -
<body ...>
<div id="foo" style="position:absolute; ...>LAYER
STUFF</div>
<table>
In a template child page, this region is usually not part of
your editable
region, and so the layer's code is rejected by the template
engine. This is
a bad thing.
If instead of dragging the layer onto the page, you use
INSERT | Layer, that
should work provided your cursor is in an editable region,
but since
editable regions are usually within tables or other layers,
you have just
broken one of the rules listed above. This is also a bad
thing.
THE SOLUTION -
Open your template page in DW, and create a special place
where it is SAFE
to put your layers. In code view, find this -
</body>
and click so that your cursor insertion point is just to the
left of
</body>.
Now, use INSERT | Template Objects > Editable Region, and
name this region
"Layer Pad" or something like that.
When you save your template page, all your child pages will
now have the
LayerPad editable region on them.
THE BIG FINISH -
On any child page where you need a layer, just click in this
editable
region, and use INSERT | Layer. Bada bing, bada boom.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"htown" <[email protected]> wrote in message
news:[email protected]...
> Maybe I am just not understanding templates but I have a
really simple one
> that
> has one editable region called "content". I want to add
a absolute
> positioned
> div to the content area but DW tells me this would
require changing code
> that
> is locked by the template. I thought that the editable
area automatically
> put
> in by DW would accommodate the added code (css) that DW
puts in when
> adding a
> template to the page.
>
> So what is the Editable area called "Head" used for
anyways if not for
> situations like this?
>
> Thanks
>
>

Similar Messages

  • Firefox for windows won't display absolute positioned divs over flash video

    I have a website that has a brightcove video player. About a month or so ago, I was able to float divs over the video player so that they would display on top of the video player, using absolute positioning.
    You can see the player here:
    lifeminute.tv/evv/8+9+10+11+12+34/widget300s
    In Firefox (mac), Chrome (windows), Internet explorer (windows) and Safari (mac) it all still displays properly. In Firefox (windows) the video player ignores the Z-index I assign it, and always places the divs underneath it, UNLESS I give the floating div a solid background color.
    When I assign the following styles to the div containing the overlay, I can see the text properly, but of course the video is obscured.
    background-color: #FFFFFF;
    height: 158px;
    position: absolute;
    top: 4px;
    width: 275px;
    If I remove the background-color element the whole overlay pops to the back of the stack behind the video again.
    Is this a FF windows bug or am I just missing something obvious?

    At times you have to add wmode="transparent" attribute to the flash video embed code.

  • Question on positioning div elements

    I have a wrapper div and a footer div below that. I want to
    center the wrapper div in the middle of the page and then position
    sub elements within this wrapper div. For example, I would like to
    create a "nav" div and an "actual content" div within the wrapper
    div. I learned that I can relatively position the wrapper div to be
    in the middle of a page regardless of screen width and then
    absolutely position the "nav" div and "actual content" within the
    wrapper div. The problem with this is that as soon as I absolutely
    position the "actual content" div within the wrapper div then the
    footer div jumps up the page to be right in the middle of the
    wrapper div when it should be located completely below the wrapper
    div. The other way of doing it would be to relatively position (or
    don't specify) both the nav and actual content divs and just float
    the nav to the left. This seems to work but I am wondering why the
    footer jumped up when I tried to absolutely postion divs in the
    wrapper div. Is there a way to not make the footer jump up and also
    what is the standard way of doing this?

    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 of positioning (with
    regard to
    placement of elements on the page only)....
    Position:absolute (or A/P elements)
    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
    page element
    (except for those contained within it, of course).
    2. The absolutely positioned element takes its position from
    the position of
    its closest PARENT *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
    layer's code
    appears (between <body> and </body>), its
    location on the screen will not
    change (this assumes that you have not positioned the A/P
    element within
    a table or another A/P element, of course).
    Furthermore, the space in
    which
    this element would have appeared were it not positioned
    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 (or R/P elements)
    In contrast to absolute positioning, a relatively positioned
    page element is
    *not* removed from the 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
    relatively positioned
    element appears (, as it will be positioned in that location
    (factoring in
    the offsets) on the screen (this is true for any placement in
    the code).
    Furthermore, the space where this element 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
    offsets (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
    content scrolls.
    Support for this in elements other than page backgrounds is
    quirky
    There are several 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%).
    3. The placement of A/P elements *can* affect the BEHAVIOR of
    other
    elements
    on the page. For example, a 'layer' placed over a hyperlink
    will mask that
    hyperlink.
    You can see a good example of the essential difference
    between absolute and
    relative positioning here -
    http://www.great-web-sights.com/g_layersdemo.asp
    You can see a good demonstration of why using layers for a
    page layout tool
    is dangerous here -
    http://www.great-web-sights.com/g_layer-overlap.asp
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "Johnny the boy" <[email protected]> wrote
    in message
    news:[email protected]...
    >I have a wrapper div and a footer div below that. I want
    to center the
    >wrapper
    > div in the middle of the page and then position sub
    elements within this
    > wrapper div. For example, I would like to create a "nav"
    div and an
    > "actual
    > content" div within the wrapper div. I learned that I
    can relatively
    > position
    > the wrapper div to be in the middle of a page regardless
    of screen width
    > and
    > then absolutely position the "nav" div and "actual
    content" within the
    > wrapper
    > div. The problem with this is that as soon as I
    absolutely position the
    > "actual content" div within the wrapper div then the
    footer div jumps up
    > the
    > page to be right in the middle of the wrapper div when
    it should be
    > located
    > completely below the wrapper div. The other way of doing
    it would be to
    > relatively position (or don't specify) both the nav and
    actual content
    > divs and
    > just float the nav to the left. This seems to work but I
    am wondering why
    > the
    > footer jumped up when I tried to absolutely postion divs
    in the wrapper
    > div.
    > Is there a way to not make the footer jump up and also
    what is the
    > standard way
    > of doing this?
    >

  • Can Layers be given RELATIVE, rather than ABSOLUTE position

    I'm having no luck finding an answer to this in HELP. I place
    the layer's anchor in a table, then position the layer. If I
    subsequently add (or remove) any lines above the anchor, everything
    on the page moves down (or up), but the layer stays where it was,
    relative to the page, not the anchor.
    If there are several layers on the page this means a wholeot
    of repositioning every time I do an edit up-page.
    Any advice?

    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 of positioning (with
    regard to
    placement of elements on the page only)....
    Position:absolute (or A/P elements)
    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
    page element
    (except for those contained within it, of course).
    2. The absolutely positioned element takes its position from
    the position of
    its closest PARENT *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
    layer's code
    appears (between <body> and </body>), its
    location on the screen will not
    change (this assumes that you have not positioned the A/P
    element within
    a table or another A/P element, of course).
    Furthermore, the space in
    which
    this element would have appeared were it not positioned
    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 (or R/P elements)
    In contrast to absolute positioning, a relatively positioned
    page element is
    *not* removed from the 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
    relatively positioned
    element appears (, as it will be positioned in that location
    (factoring in
    the offsets) on the screen (this is true for any placement in
    the code).
    Furthermore, the space where this element 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
    offsets (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
    content scrolls.
    Support for this in elements other than page backgrounds is
    quirky
    There are several 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%).
    3. The placement of A/P elements *can* affect the BEHAVIOR of
    other
    elements
    on the page. For example, a 'layer' placed over a hyperlink
    will mask that
    hyperlink.
    You can see a good example of the essential difference
    between absolute and
    relative positioning here -
    http://www.great-web-sights.com/g_layersdemo.asp
    You can see a good demonstration of why using layers for a
    page layout tool
    is dangerous here -
    http://www.great-web-sights.com/g_layer-overlap.asp
    Based on this, a static div (no longer a 'layer') would be
    what you want.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "bwilsonduncan" <[email protected]> wrote in
    message
    news:[email protected]...
    > I'm having no luck finding an answer to this in HELP. I
    place the layer's
    > anchor in a table, then position the layer. If I
    subsequently add (or
    > remove)
    > any lines above the anchor, everything on the page moves
    down (or up), but
    > the
    > layer stays where it was, relative to the page, not the
    anchor.
    >
    > If there are several layers on the page this means a
    wholeot of
    > repositioning
    > every time I do an edit up-page.
    >
    > Any advice?
    >

  • Bayside Beat Tutorial - Part 4 - Absolute positioning

    I am stuck on the Absolute positioning section. My image is supposed to be spread out across the screen and the text is supposed to be at 36% as a layer on top of the image. Here are the instructions:
    To keep related styles together, select #wrapper in the Selectors pane, and click the plus button to create a new selector called #hero after it.
    In the Layout category, set the position property to relative.
    With #hero still selected in the Selectors pane, create a new selector called #hero article to style the <article>element nested inside the hero <div>.
    In the Layout category, set the width property to 36%, and left and right padding to 10px.
    Set the position property to absolute.
    The moment I set steps 4 & 5, I get the following layout:
    It should look like this:

    Looking at your screenshot, it looks as though you have wrapped the <article> around the hero <div> in the underlying HTML. The problem isn't with your CSS, but the HTML structure.
    Compare your HTML file with the version in the completed folder.

  • How do i add a Scroll Bar to a  JList Component using absolute positioning?

    I've got a applet whose content pane is set to null. I've create a jlist component on this applet and using absolute positioning set the bounds at
    ListBox1.setBounds(380,10, 500, 500);.
    My problem is creating add a scroll bar to the list box.
    JScrollPane scrollPane = new JScrollPane(ListBox1);
    C.add(scrollPane);
    The above code is what i use and when i run this applet i don't see the list box at all. How do i add a scrollbar to this list box or JList component. Please help.

    You need to setBounds() on the JScrollPane, not the JList.
    The JScrollPane is the component that is being added to the panel.

  • Static v absolute position

    Many comments have been made elsewhere about the wisdom of
    using 'absolute', particularly when a crossbrowsers are considered
    and user's adjustment of text size..to quote one problem...
    So, in order to eliminate these glitches from my pages, I
    should apparently convert to 'static'..
    What would be the steps to take to accomplish this without
    too much hassle. I do have a lot of CSS code, which, I guess, when
    adjusted would take care of some of the problems.
    Is there a tutorial/publication which deals with this
    procedure?

    Any element without an explicit positioning style is static,
    by default,
    e.g.,
    <html>
    <head>
    </head>
    <body>
    <div>This is a static div</div>
    <p>This is a static paragraph</p>
    </body>
    > So, in order to eliminate these glitches from my pages,
    I should
    > apparently
    > convert to 'static'..
    That's a gross oversimplification. You should re-design your
    layout so that
    the page elements are placed on the page as dictated by THE
    NORMAL FLOW,
    mediated through the CSS rules. Simply taking a page that has
    been designed
    using absolutely positioned elements, and converting the
    absolute position
    to static position (by removing the positioning altogether)
    will most likely
    not work very well. I think you understand this, but I'm not
    sure.
    > I do have a lot of CSS code
    This, too, is a bit troubling. Having a lot of CSS often
    means inefficient
    use of rules and selectors.
    In general, you don't need many custom classes. And, in fact,
    they
    make your life more difficult when you come back to maintain
    the page a year
    later. Use ID selectors and create descendent selector rules.
    An example -
    #maintable { .... }
    #maintable td { .... }
    #maintable td table { ... }
    each of those rules would apply explicitly to a) this table -
    <table id="maintable">,
    and b) this cell -
    <table id="maintable">
    <tr>
    <td>...</td>
    </tr>
    </table> (and all others in that table),
    and to this table -
    <table id="maintable">
    <tr>
    <td>
    <table>
    <tr>
    <td></td>
    </tr>
    </table>
    </td>
    </tr>
    </table>
    Then you could use this rule -
    #maintable table td.special { .... }
    to apply to this cell explicitly -
    <table id="maintable">
    <tr>
    <td>
    <table>
    <tr>
    <td class="special">this one</td>
    <td>but not this one</td>
    <td class="special">this one</td>
    <td>but not this one</td>
    </tr>
    </table>
    </td>
    </tr>
    </table>
    Also, it is not necessary to define default styles, e.g.,
    font-weight:normal, unless you are trying to counteract some
    cascading rule.
    Further, it is not necessary to define styles that are
    normally inherited,
    e.g.,
    body { font-family: Calibri, verdana, arial, helvetica,
    sans-serif; }
    will style all characters used on the page, no matter where
    they are located
    or in which container.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "Karlhevera" <[email protected]> wrote in
    message
    news:[email protected]...
    > Many comments have been made elsewhere about the wisdom
    of using
    > 'absolute',
    > particularly when a crossbrowsers are considered and
    user's adjustment of
    > text
    > size..to quote one problem...
    >
    > So, in order to eliminate these glitches from my pages,
    I should
    > apparently
    > convert to 'static'..
    > What would be the steps to take to accomplish this
    without too much
    > hassle.
    > I do have a lot of CSS code, which, I guess, when
    adjusted would take care
    > of
    > some of the problems.
    > Is there a tutorial/publication which deals with this
    procedure?
    >
    >

  • Rendering bug with absolutely positioned button tags

    I'm using Firefox 10.0.1 and I've found a bug regarding button elements that are absolutely positioned. The problem is setting both the right and left CSS attributes does not affect the width of the button as it should.
    Here is some example code to show what I mean (the forum is mangling the html, hopefully you can get the gist of it):<br />
    <br />
    <pre><nowiki><html>
    <body>
    <div style="width: 500px; position: relative;">
    <button style="position: absolute; left: 0; right: 0;">Test</button>
    </div>
    </body>
    </html></nowiki></pre>
    In all other browsers the button will be 500px wide. In Firefox, it will fit to the text.

    Why don't you give that button a width:100% if you want it to take the full width of that DIV container?

  • Problem with Absolute Positioning

         I have a LARGE number of web pages (>1500) that have fields that are absolutely positioned.  I have to process these pages (JSPs) and create a temporary HTML file that will be edited in Dreamweaver.  The editing will only modify the CSS file: the temporary HTML is throw-away.
    The goal is to use Dreamweaver to organize fields on the screen and have it modify only the position in the CSS.
    My problem is that when I create the temporary HTML, it looks fine in the browser, but Dreamweaver displays the elements using a normal flow, and not using the absolute position.  I have checked the "AP Elements" tab in DW, and it shows all my fields and the "Prevent overlaps" checkbox is UNCHECKED.
    Any guidance will be appreciated...
    Here is a small HTML example (CSS below that):
    <html>
         <head>
              <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
              <title>CL0350</title>
              <link rel="stylesheet" href="example.css">
              <style type="text/css">
    body {
         background-color: #efe;
    #formContainer {
         width: 802px;
         height: 564px;
         font-family: Arial, Helvetica, sans-serif;
         font-size: 11px;
         font-weight: bold;
         border: 3px #444 solid;
         background-color: white;
         position: relative;
    </style>
         </head>
         <body>
              <div id="formContainer">
                   <div id="lblEPP_MEMBER_NBR">Member#</div>
                   <div id="lblEPP_YMDRCVD">Recv Dt</div>
    <input id="txtEPP_MEMBER_NBR"><input id="txtEPP_YMDRCVD"></div>
         </body>
    </html>
    And finally, the CSS:
    #lblEPP_MEMBER_NBR
    white-space:nowrap;
    POSITION:absolute;
    left:17px;
    top:43px;
    #txtEPP_MEMBER_NBR
    POSITION:absolute;
    LEFT:17px;
    TOP:62px;
    WIDTH:110px;
    #lblEPP_YMDRCVD
    white-space:nowrap;
    POSITION:absolute;
    LEFT:542px;
    TOP:43px;
    #txtEPP_YMDRCVD
    POSITION:absolute;
    LEFT:542px;
    TOP:62px;
    WIDTH:92px;

    Ahh - nevermind.  I see you fixed your code....  Now I'll take a look.
    On this page in DW, the fields seem to be placed using the absolute positioning, not the normal flow.  Is the additional CSS contained in the externally linked CSS file?
    <html>
         <head>
              <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
              <title>CL0350</title>
              <link rel="stylesheet" href="example.css">
              <style type="text/css">
    body {
         background-color: #efe;
    #formContainer {
         width: 802px;
         height: 564px;
         font-family: Arial, Helvetica, sans-serif;
         font-size: 11px;
         font-weight: bold;
         border: 3px #444 solid;
         background-color: white;
         position: relative;
    #lblEPP_MEMBER_NBR
    white-space:nowrap;
    POSITION:absolute;
    left:17px;
    top:43px;
    #txtEPP_MEMBER_NBR
    POSITION:absolute;
    LEFT:17px;
    TOP:62px;
    WIDTH:110px;
    #lblEPP_YMDRCVD
    white-space:nowrap;
    POSITION:absolute;
    LEFT:542px;
    TOP:43px;
    #txtEPP_YMDRCVD
    POSITION:absolute;
    LEFT:542px;
    TOP:62px;
    WIDTH:92px;
    }</style>
         </head>
         <body>
              <div id="formContainer">
                   <div id="lblEPP_MEMBER_NBR">Member#</div>
                   <div id="lblEPP_YMDRCVD">Recv Dt</div>
    <input id="txtEPP_MEMBER_NBR"><input id="txtEPP_YMDRCVD"></div>
         </body>
    </html>

  • Looking for confirmation regarding absolute positioning...

    Absolutely-positioned elements *never* interrupt the flow,
    regardless of
    what that element is.
    As such, scrollbars completely ignore said elements at *all*
    times, as if
    they weren't there at all.
    Are both those statements considered pretty much factual?

    > Would there be any way *at all* to place a div outside
    the viewport
    > WITHOUT generating a scrollbar?
    Yes - place it to the left of the left margin, or above the
    top margin. 8)
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "Mike" <[email protected]> wrote in message
    news:g8rohn$8go$[email protected]..
    > "Murray *ACE*" <[email protected]>
    wrote in message
    > news:g8rgne$rdc$[email protected]..
    >>> Absolutely-positioned elements *never* interrupt
    the flow, regardless of
    >>> what that element is.
    >>
    >> Absolutely positioned elements are REMOVED from the
    flow, so yes, they
    >> can never affect anything that is located by the
    normal flow.
    >>
    >>> As such, scrollbars completely ignore said
    elements at *all* times, as
    >>> if they weren't there at all.
    >>
    >> Curiously not. Place an absolutely positioned
    element 2000px to the
    >> right of the page's right margin and you'll get a
    horizontal scrollbar.
    >
    > How strange.
    >
    > Would there be any way *at all* to place a div outside
    the viewport
    > WITHOUT generating a scrollbar?
    >

  • Newbie Q - Absolute position of items / regions

    Hello,
    Is it possible to set an absolute position for items / regions?
    I'd like to be able to display an item at coordinates (x,y) on screen, but all I could find was how to position my items relatively to other items / regions.
    Please help.
    Thanks.
    Anat :o)

    Hi Anat,
    Yes you can absolutely position regions.
    In the Region Header enter in something like:
    &lt;div style="position:absolute; top:100px; left:100px;"&gt;
    and put the following in the Region Footer:
    &lt;/div&gt;
    You will need to experiment with this to see what affect this has on the rest of the page. There is a discussion on this forum about using DIV tags instead of TABLE tags as a means of laying out pages - not sure how far this has got yet, but it would involve rewriting the page templates.
    Regards
    Andy

  • Epub : absolute position style in Digital Editions

    Hello,
    I am developer, working for epub content and using Digital Editions to review generated epub file.
    In one of our epub contains <div> tag like below:
    <div id="top">
      <img src="../image/001.jpg"/>
      <div style="position:absolute; z-index: 1; top: 0px; left: 0px; font-size:x-large">Put words at 0px-0px</div>
      <div style="position:absolute; z-index: 1; top: 200px; left: 100px; font-size:x-large">Put words at 200px-100px</div>
      <div style="position:absolute; z-index: 1; top: 70%; left: 35%; font-size:small">Put words at 70%-35%</div>
    </div>
    I am trying to put the words onto the image file and it looks ok when checking it in other epub viewer but looks like DE ignoring these style attrbs: position, top, left.. and put these inner <div>s on next page.
    Is there any solution for this?
    just fyi, I set 'pre-paginated' on the content opf file and viewport metadata in the html file.
    Thanks,
    KT

    Can't help directly I am afraid.
    Just a comment that you should test on both v2.0/2.0.1 and on the older more reliable v1.7.2 (link below). 
    They use quite different rendering technologies, and probably very different rendering engines.
    Many people use v1.7.2: either because they haven't upgraded, or because (like me) they have hit one of the huge number of bugs in v2.0 and can't use it.  (In my case the V2 bug working with Sony ereader and Overdrive library books.)
    ~~~
    ~~~~~~~~~
    There are lots of bugs in ADE2.0 (and 2.0.1).  Try replacing ADE2.0 with the older but more reliable v1.7.2.
    (You can have them both installed at once if you like.)
    Version 1.7.2, it is a little difficult to find, available on Adobe site for Windows and for Mac.
    http://helpx.adobe.com/digital-editions/kb/cant-install-digital-editions.html
    The forum software is sometimes corrupting the link above.  There shouldn't be a blank in 'editio ns.html'.  The following redirects to the same page: http://tinyurl.com/diged172
    Some people have found ADE trying to upgrade automatically. 
    It appears (not 100% sure) that if you install ADE2.0 as a new install (not as an upgrade) that your 1.7.2 will continue to run.
    Probably best to say no if 2.0.x installation asks if you want to migrate your library.

  • [Photoshop CC 2014] Click&hold-move-release doesn't work when adding adjustment layer from the layer panel

    When selecting a menu item I used to click the left mouse button and hold it down, move the pointer to the desired menu item and release the mouse button. Everything works fine in the mine menu, but there's a problem when adding new adjustment layer from the layer panel: when I release the button nothing happens, I have to press the button again. In previous PS version it worked fine. How can I fix this?

    I don't think that is user fixable, meaning you'll have to wait till adobe fixes it with an update.
    Photoshop cc 2014
    windows does not work
    mac does work
    Did you already post over here:
    [Photoshop CC 2014] Click&hold-move-release doesn't work when adding adjustment layer from the layer panel

  • Page footer absolute position issue - Crstal Reports

    Hi,
    I have a page footer section in the crystal report.
    There are 2 sections Page footer A and Page footer B.
    Here I am displaying Page Footer A in the first page and Page Footer B on all the pages.
    Here the issue is, as I applied a suppress condition on page footer A in order to display only on frist page. This is working fine. But in the second page the page footer B is displayed a bit above the end of page as the page footer A is suppressed.
    Can we set absolute position for page footer B? So that, the page footer B will be displayed at the same way in all the pages as like the first page.
    Thankyou,
    Regards
    Gowtham Sen.

    Hi All,
    The issue got resolved. I used the option underlay. It worked well.
    Thanks.

  • Box model/none absolute positioning with flash

    In recent years none-absolute positioning (or box model positioning) has become the norm with HTML/CSS
    this is uselfull for dynamic functions which appear on an event (such as an object which appears when a button is clicked on or a error message that appears when a form box is given invalid input because it automatically inserts itself it the right place.)
    One very important example of this is when you have a form which automatically produces an error message and the error message appears bellow the input area which caused it and the rest of the page is pushed down.
    With none absolute positioning the developer does not need to worry about this.
    But if the objects are given absolute position then it becomes a massive problem, the developer has to go about giving the objects differetn positions dependant on if dynamic objects appear or not
    potentially the developer has to consider all possible variables, and code if statements which determine the position of all static objects for all possible variables which dynamic objects could take.
    so does flash have a "none absolute positioning" solution to this problem.

    Before you get all happy and pleased with yourself, APDivs or Layers seldom work well as a primary layout method. Here are some reasons why:
    http://apptools.com/examples/pagelayout101.php
    You're much better off using default CSS positioning (which is no positioning at all) along with CSS margins, padding and floats.  If you don't believe me, check your page in non-IE browsers with increased/decreased text-sizes (zoom, text only).
    From  Tables to CSS Web Design Part 1 -
    http://www.adobe.com/devnet/dreamweaver/articles/table_to_css_pt1.html
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    http://alt-web.com/
    http://twitter.com/altweb
    http://alt-web.blogspot.com

Maybe you are looking for

  • I was trying to update my iTunes to 11.1.3 and I keep getting an error message

    I was trying to update my iTunes to 11.1.3 and I keep getting the error message "iTunes has an invalid signature. The download has been removed or stopped".  Thanks

  • Problem updating 8520 4.6 to 5.0

    currently i'm using 4.6 system software...  i 've previously updated my blackberry to 5.0 but for some technical issues , i downgraded it to 4.6... now i want to update it to 5.0 but as i double click loader.exe( vendor.xml deleted) , it starts but w

  • Handling runtime Exceptions in tomcat / struts

    Hi, I'm trying to find a way to cleanly handle exceptions in struts/tomcat. I've read a number of suggestions in my struts book, but none seem to work. What I've done is created an instance within my action class that deliberatley creates a NullPoint

  • How to avoid TEST PRINT page

    Dear All, How to aviod the test print page in printing. I am getting SAP cover page(test print page) for every time I am printing. I ma using the following code.   CASE sy-ucomm.     WHEN 'PRNT'.       DATA: l_params TYPE pri_params,             l_va

  • Alguém já encontrou o aplicativo QEEP para o firefox Os

    Eu ja procurei no Marketplace o aplicativo é não achei. Quem tiver achado me manda o link..