Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter alevel

    (@alevel)

    Hi,

    I’m sorry to say, but this does not work. This always returns the value 1 (so attr(‘page’) = 0), regardless of what is the actual current page.

    Rgds, Alex

    Thread Starter alevel

    (@alevel)

    Hi,

    Finally got it working with the below settings in the template style.css:

    html, body, form {
    height: 100vh;
    }
    #fbuilder {
    height: 100%;
    overflow-y: hidden;
    }
    #fbuilder fieldset>.fields.cff-container-field {
    height: calc(100vh – 205px); /* header + footer + margin = 205px */
    overflow-y: auto;
    }
    #fbuilder .pbPrevious {
    position: fixed;
    bottom: 10px;
    left: 50px;
    }
    #fbuilder .pbNext, .pbSubmit {
    position: fixed;
    bottom: 10px;
    right: 50px;
    }

    Best regards,

    Thread Starter alevel

    (@alevel)

    Hello,

    The form/template I’m working on are still on my dev-environment (localhost), so difficult to share a link at this point. Sorry.

    What would help me though, is to understand which selectors to use to control the height of the inner div’s of the form, I mean inside the .pbreak class (+ the fieldset that is automatically added by cff for each page). Most of my form-pages use a fieldset container as wrapper and sometimes a second fieldset inside that first container. The outer container should fill-up the entire screen that remains after the form header and the ‘footer’ which holds the previous and next buttons, are subtracted. If the form content exceeds the height of the outer container, it should scroll inside of that container but not cause the entire screen to scroll. Thanks!

    Best regards, Alex

    Thread Starter alevel

    (@alevel)

    Hi,

    Thanks!

    With some tweaking I got your code to work, but only on the first pagebreak somehow. I will look into that some more. However, with some further digging on Google, I found following css-only workaround which also works quite nicely. I thought I’d share it. Just enter these css-rules in the Form Settings-Customize From Design:

    @keyframes grow {
    0% {
    display: none;
    opacity: 0;
    }
    1% {
    display: block;
    opacity: 0;
    margin-left: 100%;
    }
    100% {
    opacity: 1;
    margin-left: 0%;
    }
    }
    #fbuilder .pbreak {
    display: none;
    animation-name: grow;
    animation-timing-function: ease-out;
    animation-duration: 0.5s;
    }

    /* btw, other ‘transform’ options like scale or scaleX also work */

    Best regards, Al

    Thread Starter alevel

    (@alevel)

    Hi,

    I’ve sent the link via your support page. I’d rather not share the link in the public domain. But thanks for your swift reply!

    Regards, Alex

    Thread Starter alevel

    (@alevel)

    Hi Peter,

    Not quite sure what you are asking. You mean the “f12″ console in the browser?

    No console messages there. Below is what I can find in the page source:

    <input type=”button” onclick=”javascript:location.href=’?page=diehard&schema_name=uXXXXXXXXXX&table_name=sp_ea_appointments&paged=1′” class=”button button-secondary” value=”Back To Parent List”>

    If this does not give the right clue, should I look elsewhere? Or I can send you the url via e-mail. Let me know.

    Regards, Alex

    Thread Starter alevel

    (@alevel)

    Hi Peter,

    Thanks for your quick reply! Hopefully this weird date bug isn’t too hard to fix.

    Regarding the ‘Back to Parent List’ button; this happens in a Data Projects parent/child detail view in the front-end. Not critical, as the obvious work-around is hitting the browser’s back-button, only slightly annoying 🙂

    Btw, I’m looking forward to working with your Pro-version. Any news on the ETA?

    Regards, Alex

Viewing 7 replies - 1 through 7 (of 7 total)