Cf8 ajax/layout issue - intranet application

i have a cflayoutarea that contains a cfdiv which is
populated dynamically with ajax. depending on what the user chooses
in a cfinput-autosuggest at the top of the form, a cfdiv will get
plain html -OR- a cfform containing a
cfinput type=button.
the cfform containing the cfinput type=button executes
onclick=coldfusion.window.create(), and the source file specified
is a coldfusion template containing a cfform with a cfgrid. the
query that populates the cfgrid sometimes returns sufficient data
so as to make the grid larger (vertically) than the size of the
window. when this happens, a scroll bar is generated. when i use
the scrollbar, the grid won't move. the upper border of the grid
(atop the header) is the only part that does. the data at the
bottom of the grid is rendered inaccessible.
however, everything works perfectly in FireFox 2.0.0.11.
if i take the cfform containing the cfinput type=button out
of the cflayoutarea, it works fine in IE7 and FireFox.
my organization officially supports IE7, not FireFox. the
application needs to use ajax so that it can either return plain
html in the cflayoutarea OR the cfform w/cfintput type=button that
drives the popup window. either that or i
have to completely rethink how i'm delivering this data.
i've built a working example of this that uses two files:
test_main.cfm and test_grid.cfm....thanks!

could you post a sample of your code please

Similar Messages

  • CFCONTENT from within any AJAX layout

    CFCONTENT does not work as documented when I call it from
    within my AJAX app. Workarounds that call the code from another
    directory are way too kludgey for the client, but proved my
    standard code works outside of AJAX layout areas.
    This problem was first mentioned here in January '07 but
    never answered. Has anyone found a workaround?

    > Thanks and apologies... I should have just said
    "CFCONTENT does not work when
    > called from within any AJAX container," for example
    CFDIV, CFWINDOW,
    > CFLAYOUTAREA.
    > [...]
    > The result is exactly as tSpark described... I see the
    HTML table
    > in a standard browser window, it does not launch and
    display in Excel. The same
    > code works as expected (and as I've used it repeatedly
    for at least 4 or 5
    > years) if it is in a non-AJAX page.
    Right. Well I think you might be misunderstanding how all
    this works.
    Firstly, here's a very small replicable case:
    <!--- mimeTypeTestMain.cfm --->
    <cfwindow initshow="true" source="./mimeTypeTestInner.cfm"
    />
    <!--- mimeTypeTestInner.cfm --->
    <cfcontent type="application/msexcel" reset="true">
    <cfheader name="Content-Disposition"
    value="filename=mimeTypeTestInner.xls">
    <table border="1">
    <tr><td>Foo</td></tr>
    <tr><td>Bar</td></tr>
    </table>
    As you say, this just displays an HTML table in the window.
    Now, first things first, the <cfcontent> tag is indeed
    doing its job
    exactly as intended. If you watch the underlying HTTP
    requests/responses
    taking place, you'll see the MIME type of
    mimeTypeTestInner.cfm is indeed
    being set to application/excel, and the content-disposition
    is being set to
    the correct file name.
    However that sort of thing is only ever interpretted by the
    browser as
    starts receiving a new response from a request it itself has
    made (you
    know, typing in a URL in the address bar, or clicking on a
    link or
    sumbitting a form on the referring page, etc.
    A <cfwindow> is *not* a "window" in the sense of a
    browser window (or a
    browser frame or iframe), it's just a <div> with some
    styling applied to it
    to make it look "window-y". Part of the <cfwindow> tags
    functionality is
    that behind the scenes, a Javascript XML object is making a
    request back to
    the server to get the content for the window as specified in
    the "source"
    attribute. Having received some data back, some client side
    JS (which
    <cfwindow> has previously sent down to the browser)
    grabs it and pops it
    into the innerHtml of the <div>. It doesn't pay any
    attention to your
    headers. It doesn't actually make any sense it pay any
    attention to header
    information like that, because the content of the request is
    being
    integrated into an existing doc, which already has a name and
    a MIME type.
    Make sense?
    I've singled out <cfwindow> here because I happen to be
    getting myself up
    to speed with CF8 at present, and <cfwindow> was one of
    those tags I have
    never used in production code: so it's kind of "on my radar"
    at present.
    The other AJAX-esque tags will work the same way, for the
    same reasons
    though.
    Adam

  • CF8 - Ajax Form Post and Document Type

    I'm having a problem trying to figure out how to get a form
    post to return a PDF document using CF8. I can't seem to get
    CFDOCUMENT to deliver a PDF through the form.
    I have a form inside a CFDIV...
    <cfdiv id="mydiv">
    <cfform action="myscript.cfm" method="post">
    a bunch of input fields, then...
    <input type="submit" value="Generate PDF" />
    </cfform>
    </cfdiv>
    On submit, the form makes an Ajax call sending the data to a
    script that generates a PDF using CFDOCUMENT and delivers it
    through the browser.
    However, it is not delivering the PDF. Instead, it is
    delivering the CODE for the PDF into the CFDIV and trying to
    display the code. I tried the same form delivering an Excel file
    with cfcontent and cfheader. It delivers the code instead of the
    actual document.
    If I take this form out of the CFDIV, everything works great.
    Why can't the Ajax call made by the CFDIV functionality
    deliver a PDF or other file?

    I'm having the same problems over two years later. CFCONTENT
    doesn't work as documented when you call it from within an AJAX
    app. My workarounds that call the code from another directory are
    way too kludgey for the client, but proved my standard code works
    outside of AJAX layout areas. I'm specifically trying to do what
    tSpark also mentioned, that is generate an Excel spreadsheet from
    query results displayed in an HTML table.
    Has anyone solved this problem?

  • Layout issue while trying Migrate Oracle Report to XML publisher Reports

    Hi
    I am trying to Convert Seeded Oracle Reports (rdf) to BI Publisher reports, in doing so encounter layout issues. The layout of the RTF , PDF or HTML generated by BI Publisher is different form the text, PDF or HTML outputs generated by the concurrent report. The problem with the BI Publisher template and out put
    Is, the lay out is getting distorted .
    Steps to archive the migration :
    -     download the rdf from the server to local m/c.
    -     execute Forms 9i Util rwconverter to generate a xml
    -     use the oracle.apps.xdo.rdfparser.RTFTemplateGenerator API to generate a RTF template of the report layout
    -     Then use this template to generate a XSL via oracle.apps.xdo.template.RTFProcessor API
    -     The Apply the XSL on the XML data output of the report using oracle.apps.xdo.template.FOProcessor to generate RTF , PDF & HTML files.
    Name of the Report used for migration “FSG - Report Detail Listing” , responsibility GL super User. This was just a random report we picked-up for trial.
    The layout of these files seems to distorted than the layout of the original report output as generated by the rdf report.
    Pls suggest some means to resolve this or any pointers towards what causing this could be of help.
    -     Shudipto

    The process of "converting" an old Oracle Reports rdf into a BIP report is more akin to writing a brand new report in BIP than to what most people would consider a true conversion.
    The conversion routine outlined by Oracle just gives you a starting point for converting RDF layouts into BIP, and nothing more. In regards to the data define it does somewhat better generating your queries and XML layout (but honestly, that is the easy part), but even for the data define it will lose your formula columns as well as report triggers.
    I have used the converter on several dozen rdf files and I have yet to see one that is better than 10-20% ready for use after the conversion process.
    I would strongly suggest that you only convert the reports that you have to convert (for enhancements, modifications, etc). If it ain't broke in old Oracle Reports, dont' try to fix it in BIP.
    Scott

  • Layout issue with af:tree component

    I am using af:tree component but I am finding layout issue with it. I have a requirement where in I need the tree to stretch to the available space but a horizontal and a vertical scrollbar comes up automatically. Is there a way to handle this issue?

    User, without your jdev version it's hard to help.
    Have you embedded the tree component in a stretch layout?
    Timo

  • CSS Layout issue!! Help Urgent!!

    I am having a problem with creating a css layout, in the past i used tables and am trying to convert my sites for my customers. I have layed out the website using divs and css and it looks great until i put in the cosing of the menu bar. when i put in the coding for the menu bar suddenly the bar has a padding around it but i cannot find a padding that would change this in the css coding. I need this done asap! so please help. ill show my coding below:
    this is the div coding:
    <div id=Nav>
       <ul class="dropdown" id="Bar"; width: 879px" name="Bar">
             <li class="style16" style="width: 161px; height: 22px">
       <a href="default.html" style="width: 146px">Home</a></li>
             <li class="style10" style="width: 169px; height: 23px">
       <a href="about.html" style="width: 153px">About</a></li>
         <li class="" style="height: 31px; width: 175px; left: 0px; top: 0px">
       <a href="Equipment.html" class="style18">
       <div class="style10" style="width: 156px; height: 20px;">
        Equipment</div>
       </a> <ul class="sub_menu">
                <li><a href="compressor.html">Air Compressors</a></li>
                <li><a href="compactions.html">Compaction</a></li>                            
                <li><a href="concrete.html">Concrete Equipment</a></li>
                <li><a href="forklifts.html">Fork Lifts</a></li>
                <li><a href="generators.html">Generators</a></li>                            
                <li><a href="groundthawing.html">Ground Thawing</a></li>
                <li><a href="heaters.html">Heaters</a></li>
                <li><a href="scissorlifts.html">Scissor Lifts</a></li>                            
                <li><a href="boomlifts.html">Boom Lifts</a></li>
                <li><a href="lighttowes.html">Light Towers</a></li>
                <li><a href="misc.html">Misc.</a></li>                            
                <li><a href="dirtequipment.html">Dirt Equipment</a></li>
                <li><a href="powertools.html">Power Tools</a></li>
                <li><a href="pumps.html">Pumps | Saws | Welders</a></li>                              
                     </ul>
             </li>
             <li style="width: 165px"><a href="locations.html">
       <div class="style10" style="width: 154px">
        Locations</div>
       </a>
               </li>
                 <li style="width: 180px"><a href="contact.html">
       <div class="style16" style="height: 24px">
        Contact Us</div>
       </a>         </li>
            </ul>
      </div>
    This is the css coding:
    #wrapper {
    width: 880px;
    margin-right: auto;
    margin-left: auto;
    background-color: #f4f4f4;
    #Navigation {
    background-image: url(Images/NAvigation%20BAr.jpg);
    background-repeat: no-repeat;
    width: 880px;
    visibility: visible;
    height: 3-px;
    vertical-align: top;
    Nav {
    vertical-align: top;
    margin: 0px;
    padding: 0px;
    clear: both;
    height: 20px !important;
    #wrapper1 {
    width: 876px;
    margin-right: auto;
    margin-left: auto;
    color: #F4F4F4;
    /* IE10 Consumer Preview */
    background-image: -ms-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* Mozilla Firefox */
    background-image: -moz-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* Opera */
    background-image: -o-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* Webkit (Safari/Chrome 10) */
    background-image: -webkit-gradient(linear, left top, right top, color-stop(0, #716375), color-stop(1, #E8E8E8));
    /* Webkit (Chrome 11+) */
    background-image: -webkit-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* W3C Markup, IE10 Release Preview */
    background-image: linear-gradient(to right, #716375 0%, #E8E8E8 100%);
    margin-bottom: auto;
    #Bar {
    background-repeat: no-repeat;
    width: 880px;
    height: 28pt;
    overflow: visible;
    background-image: url(Images/NAvigation%20BAr.jpg);
    position: relative;
    vertical-align: top;
    #container {
    width: 880px;
    color: #000;
    background-color: #EDEDED;
    dominant-baseline: 578px;
    /* IE10 Consumer Preview */
    background-image: -ms-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* Mozilla Firefox */
    background-image: -moz-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* Opera */
    background-image: -o-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* Webkit (Safari/Chrome 10) */
    background-image: -webkit-gradient(linear, left top, right top, color-stop(0, #716375), color-stop(1, #E8E8E8));
    /* Webkit (Chrome 11+) */
    background-image: -webkit-linear-gradient(left, #716375 0%, #E8E8E8 100%);
    /* W3C Markup, IE10 Release Preview */
    background-image: linear-gradient(to right, #716375 0%, #E8E8E8 100%);
    margin-bottom: auto;
    #content {
    float: left;
    color: #090;
    width: 580px;
    padding-right: 6px;
    background-color: #033;
    margin-top: 20px;
    .container {
    color: #000;
    background-color: #ff6;
    width: 876px;
    #expect {
    height: 164px;
    width: 294px;
    float: right;
    position: relative;
    background-color: #C90;
    margin-left: 582px;
    padding-top: 10px;
    #hours {
    float: left;
    height: 55px;
    width: 294px;
    line-height: 4px;
    word-spacing: normal;
    white-space: normal;
    display: inline;
    letter-spacing: normal;
    padding-top: 10px;
    font-size: 13pt;
    color: #000;
    margin-left: 586px;
    background-color: #F99;
    #footer {
    height: 76px;
    width: 880px;
    background-color: #CC0;
    clear: both;
    #cards {
    float: right;
    height: 31px;
    width: 294px;
    margin-left: 582px;
    padding-top: 10px;
    background-color: #F36;
    #contact {
    float: left;
    height: 328px;
    width: 293px;
    word-spacing: normal;
    white-space: normal;
    line-height: 1px;
    color: #000;
    display: inline;
    font-size: 14pt;
    background-color: #FFF;
    padding-top: 10px;
    margin-top: 20px;
    #header {
    background-image: url(Images/Proquip%20Logo/Proquip%20logo2.jpg);
    background-repeat: no-repeat;
    background-position: center center;
    width: 885px;
    height: 126px;
    background-color: #000;
    margin-right: 2.5px;
    margin-left: 0px;
    #wrapper #container #contact p strong {
    color: #800000;
    font-size: 14pt;
    #wrapper #container #contact blockquote p a {
    color: #000;
    #wrapper #container #expect div {
    color: #900;
    font-size: 14pt;
    font-weight: bold;
    #wrapper #container #hours div {
    color: #900;
    font-size: 14pt;
    font-weight: bold;
    #box2 {
    background-image: url(Images/Option%201/Services/whitebox2.jpg);
    #box3 {
    background-image:url(Images/Option%201/Services/redbox2.jpg);
    background-repeat:no-repeat;
    background-position: center center;
    #gold {
    background-image:url(Images/Option%201/Logos/gold.gif);
    background-repeat:no-repeat;
    #white {
    background-image:url(Images/Option%201/ProQuip-Pics/box1.gif);
    background-repeat:no repeat;
    #forklift {
    background-image:url(Images/Option%201/ProQuip-Pics/34-01-4380.jpg);
    background-repeat:no-repeat;
    #scissorlift {
    background-image:url(Images/Option%201/ProQuip-Pics/jlg-scissor-lifts-21.jpg);
    background-repeat:no-repeat;
    /* Navigation Menu- Level one */
    ul {
    list-style: none
    ul.dropdown {
    font-size: 13pt;
    color: #000000;
    height: 25px;
    text-decoration: none !important;
    width: 860px;
    position: relative;
    vertical-align: top;
    ul#Bar.dropdown {
    width: 878px;
    position: relative;
    vertical-align: top;
    ul.dropdown li {
    font-weight: 600;
    float: left;
    zoom: 1;
    font-family: Arial, Helvetica, sans-serif;
    font-size: 13pt;
    display: block;
    width: 175px;
    color: #000000;
    top: 25px;
    text-decoration: none !important;
    text-align: center;
    ul.dropdown a:hover {
    color:#cc0000;
    ul.dropdown a:active {
    color: #000000;
    ul.dropdown li a {
    display: block;
    border-right: 1px solid#333;
    color: #000000;
    border-right-width: 1px;
    text-decoration: none !important;
    text-align: center;
    ul.dropdown li:last-child a {
    border-right:none; /* does not wotk in IE */
    text-decoration:none !important; } 
    ul.dropdown li.hover,
    ul.dropdown li.hover {
    color: #000000;
    position: relative;
    height: 28px;
    top: 0px;
    ul.dropdown li.hover a {
    color:#800000;
    /* Level Two Navigation */
    ul.dropdown ul {
    width: 180px;
    visibility: hidden;
    position: absolute;
    top: 100%;
    left: 36%;
    display: block;
    float: left;
    color: #000000;
    text-decoration: none !important;
    height: 25px;
    ul.dropdown ul li {
    font-weight: normal;
    color: #000000;
    border-bottom: 1px solid #ccc;
    float: left;
    border-bottom-color: #c0c0c0;
    border-bottom-style: groove;
    display: block;
    background-color: #dbdbdb;
    text-decoration:none !important;
    /* IE 6&7 needs inline block */
    ul.dropdown ul li a {
    border-right: none;
    display: inline-block;
    height: 18px;
    line-height: 16px;
    color: #000000;
    width: 100%;
    text-decoration: none !important;
    /* Level Three Navigation */
    ul.dropdown ul ul {
    top: 100%;
    color: #000000;
    text-decoration: none !important;
    ul.dropdown li:hover>ul {
    visibility: visible;
    color: #000000;
    top: 30px;
    text-decoration: none !important;

    I have the site using tables up and running, this is a website for a client so I cant make a test site using that domain would it be ok if I screen shot'ed the problem?
    Date: Thu, 24 Apr 2014 12:19:44 -0700
    From: [email protected]
    To: [email protected]
    Subject: CSS Layout issue!! Help Urgent!!
        Re: CSS Layout issue!! Help Urgent!!
        created by Jon Fritz II in Dreamweaver support forum - View the full discussion
    Well, you're not using position:absolute, so you've got a big thumbs up from a bunch of us for that.
    Is there any chance you could post a link to this page on your server? It's much easier to troubleshoot from a browser than it is to rebuild the page from code fragments.
    If you haven't gone live with the page yet, create a folder called TEST in your site and save copies of the page and css there. Upload TEST and post a link to it here. Once the problem is found/fixed, delete TEST from the server.
    You can also attempt to use Firefox or Chrome to find your issue by right clicking > Inspect Element. All CSS that affects a given element will be displayed with file name and line numbers there.
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6327947#6327947
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6327947#6327947
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6327947#6327947. In the Actions box on the right, click the Stop Email Notifications link.
               Start a new discussion in Dreamweaver support forum at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Minor Layout Issue when Printing Invoices in Chrome (v20.0.1132.47)

    This is a relatively minor issue in the big scheme of things but a client of ours has reported a layout issue when bulk printing invoices in Chrome. It could be default browser behaviour which BC has no control over but I thought I’d submit it anyway.
    It occurs when you’re viewing the default Order Report (http://www.yourdomain.com/AdminConsole/#!/CRM/OrderList.aspx) in the BC v3 interface and you want to print invoices in bulk (see screenshot below).
    When you print invoices in bulk in Chrome they print on overlapping pages, as opposed to Firefox where each invoice will print on a separate page, which makes management much easier for our client. I’ve tried tinkering with the print settings inside of Chrome but I can seem to change it.
    Does anyone know a way around this or are we dealing with default browser behavior that is out of our hands?
    Cheers,
    Matt
    [email protected]

    Could someone assist please?
    I am having a similar problem.
    thanks

  • 11gR2- pdf report layout issue in chrome browser

    hi,
    We are using 11gR2(11.1.2) forms and reports,when we run reports as pdf in chrome browser it has layout issues, spacing,no data etc, but the same reports works fine on internet explorer 8.
    Is there any settings required in chrome browser, or report server?, please help with this issue.

    Did you ever solve this problem? I have the same problem... In IE it centers the report in the ReportViewer control but in Google Chrome the ReportViewer shows the report to the left... Left aligned.... What is the fix for this? Mike in Los Angeles, California,
    USA

  • Issue Tracking Application

    Can someone please help.
    I have been through Chapter 10 of the 2 Day Play Application Express Developer Guide 2.1, "How to Build and Deploy an Issue Tracking Application".
    At run time when I select the Delete button, the confirmation box appears. Selecting Yes gives this error:
    Contact your application administrator.
    Error ERR-1016 Application "108" Page "0" not found (requested language="en-us")
    OK
    Can I change this to return to the original Issues page 6?
    Thanks
    Pat.

    Pat,
    Yes, you should be able to change this. Look for the branch that is associated with the Delete button.
    Sergio

  • [svn] 2210: Fix for layout issue of AIR apps on mac when only width or height is

    Revision: 2210
    Author: [email protected]
    Date: 2008-06-24 11:56:52 -0700 (Tue, 24 Jun 2008)
    Log Message:
    Fix for layout issue of AIR apps on mac when only width or height is
    set on root WindowedApplication tag.
    Bugs: SDK-14643.
    QA: Yes, very much so.
    Reviewer: Ryan
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-14643
    Modified Paths:
    flex/sdk/branches/3.0.x/frameworks/projects/airframework/src/mx/core/WindowedApplication. as

    Updates:
    I've opened a bug with Adobe regarding this issue:
    http://bugs.adobe.com/jira/browse/FP-4362
    Also, the Cancel operation on a FileReference causes the same issue to happen as does loading.  I really think it's an operating system focus issue.
    UPDATE:
    Looks like this has already been tracked and is scheduled to be fixed:
    https://bugs.adobe.com/jira/browse/FP-2785

  • We've encountered the following issues: Adobe Application Manager failed to install.

    When I attmept to open / load Adobe Application Manager I get the following error message:
    We've encountered the following issues: Adobe Application Manager failed to install.
    OS: Windows XP Professional
    Any Help would be appreciated.

    Which operating system are you using?  Are you able to utilize other Adobe AIR applications successfully?

  • H:selectOneRadio layout issue

    All,
    I'm new to JSF and am wondering if anyone had tackled a layout issue that I am running into.
    I have a h:selectOneRadio tag inside which, I have a couple of f:selectItem items. I want to show some text fields and then show the last f:selectItem item. Is it possible in JSF?
    <br>
    In plain html terminology, I want :
    radio
    radio
    textfield
    radio
    Code in html:
    <br>
    <TABLE BORDER="0" CELLSPACING="0" CELLPADDING="3" WIDTH="550">
    <TR>
    <TD COLSPAN="2" WIDTH="100%">
    <b>Payment Method</b>
    </TD>
    </TR>
    <TR>
    <TD WIDTH="26%">
    </TD>
    <TD WIDTH="74%">
    <p class="body"><input type="radio" name="card" value="VI">Visa</p>
    </TD>
    </TR>
    <TR>
    <TD WIDTH="26%">
    </TD>
    <TD WIDTH="74%">
    <p class="body"><input type="radio" name="card" value="MC">MasterCard</p>
    </TD>
    </TR>
    <TR>
    <TD WIDTH="26%" align="right">
    <p class="body">Credit Card Number:</p>
    </TD>
    <TD WIDTH="74%">
    <input type="text" name="ccnum" maxlength="26" size="40" value="">
    </TD>
    </TR>
    <TR>
    <TR tal:replace="CVV2">
    <TD WIDTH="26%" align="right">
    <p class="body">Security Code:</p>
    </TD>
    <TD WIDTH="74%">
    <input type="text" name="cvv2" maxlength="4" size="5" value="">
    </TD>
    </TR>
    <TR>
    <TD WIDTH="26%" align="right">
    <p class="body">Expiration:</p>
    </TD>
    <TD WIDTH="74%">
    <p class="body"><input type="text" name="ccexmo" maxlength="2" size="2" value=""> <input type="text" name="ccexyear" maxlength="4" size="4" value=""> For example, 03/2007</p>
    </TD>
    </TR>
    <!-- The follow row should only be displayed if Billing is an option -->
    <TR tal:replace="BILLME">
    <td width="26%" align="right">
    <p class="body">Other Payment:</p>
    </td>
    <TD width="74%">
    <p class="body"><input type="radio" name="card" value="BILL">Please send me a bill.</p>
    </TD>
    </TR>
    </TABLE> Thanks
    Jim

    you can build this type of behaviour by creating a custom class.
    I think this is not possible by building the select items.
    PL,post the solution if you find any.
    -- raju

  • Layout of VC Applications

    Hello All,
    When we see the output of any VC Application in the Portal the layout of that application will be either in Blue Background or White Background depending on the selection of the Frame Style.
    My Qn is : Can we customize this layout with different themes and colors ?
    Regards,
    Deepu.K

    Hi,
    You can refer to this article:[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4090c675-89f9-2910-5480-993360856c2b|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4090c675-89f9-2910-5480-993360856c2b]
    Regards,
    Natty

  • Flash player Update causing layout issues in Adobe Reader

    I did an updated to adobe flash player to version 15.0.0.239 and now the Adobe Reader XI (11.0.09) Layouts don't work,  only file list mode.
    Is there any way of fixing this? This new layout issue is going to cause issues since the whole appeal of using Acrobat Portfolios is the Presentation Layout views.
    Please help
    thanks!

    I have found sometimes you need to run Adobe's Flash uninstaller, before running the installer.
    Typically the first whole number of a version is usually a major upgrade, versus an update, and hence why the built-in update function fails to see the new version on many software.
    As for "safe", clone backup in case there is a feature you don't like about the new version, so you can always run it like it was before.
    https://discussions.apple.com/docs/DOC-1992
    You don't know how Adobe might alter the overall PDF frameworks on the computer when the upgrade is completed.  If you don't clone, you may find yourself stuck with whatever changes they make.

  • Share graphic layout across web applications (WAR)

    Does somebody know how to share graphic layout across web applications?
    e.g. how to dynamically include a layout html across multiple webapps, so, if I make a change to that layout,, the change is automatically reflected in all webapplications already deployed.
    any idea will be appreciated

    Hi,
    To have a common layout across multiple web applications you can use cascading style sheets (css). By making use of the same style sheet you can have the same appearance in all the web applications. Changing the styles in the css will be reflected in all the pages that make use of this css. The changes wont be effected though in all the already deployed web applications. They will have to be re deployed for the changes to take effect.
    Hope this helps you
    Cheers
    Giri :-)
    Creator Team

Maybe you are looking for

  • Preview & Adobe Clearscan save file problem

    Preview appears to have some compatibility issues with Adobe Clearscan OCR'd PDFs. While Preview can view and read the PDF initially and can copy text from the PDF into other applications; if you attempt to save the PDF in Preview (with or without ma

  • Hi.. I neee one help in sapscript

    Moderator message: please use informative subjects and the correct forum in future.  Moved to correct forum hi. I have copied the standard SAP Script Layout/form and changing it to our standard.  i need to display the material number. and the payment

  • Infotypes and Payroll

    Hi,     Customer does not want to give display authorization for few fields in the infotypes how to resolve this issue?     To implement sap payroll what are the mandatory modules for HR ?     How do you transfer data from PA to PD ? regards, kumar

  • Safari (6.0 on mountain lion) hasn't  been loading/opening some of the sites that I....

    Ok, I may might as well never think of praising any apple product ever again!! SO the past 4 days safari (6.0 on OS X mountain lion 10.8.1) hasn't  been loading/opening some of the sites that I try to go on, for ex.: YouTube, Yahoo ect. However, site

  • Assets - Customizing of Depreciation Areas

    Good Morning! We are customizing the Depreciation Areas (In "Define Depreciation Area) and one of them is "Tax Reporting". This Area cannot be posted to General Ledger so we have defined in this transaction that this Area is not going to be posted in