No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Scrolling in Q-Page-Container instead

    Framework
    2
    4
    309
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      raynorise last edited by

      Hi everyone,

      I am currently working on a website using quasar framework and have been trying to figure out how can I make the scrollable area within the Q-Page-Container instead of scrolling the entire page

      https://jsfiddle.net/tr52yg39/21/

      From this jsfiddle, you could see if I were to scroll down, the top left border radius will be gone and that is not what I wanted.

      I was hoping to scroll within the container instead so that the top left border radius would remain in that position

      beets 1 Reply Last reply Reply Quote 0
      • beets
        beets @raynorise last edited by

        @raynorls Try this:

            <q-page-container class="bg-blue absolute-full">
              <div class="fit scroll">
                <router-view />
              </div>
            </q-page-container>
        
        R 1 Reply Last reply Reply Quote 1
        • beets
          beets last edited by

          You could also replace that div with a q-scroll-area. Keep the fit class but the scroll class wouldn’t be needed anymore. Just depends if you want the fancy scrollbar and other features q-scroll-area provides.

          1 Reply Last reply Reply Quote 1
          • R
            raynorise @beets last edited by raynorise

            @beets Thank you! This works perfectly. I did tried adding a <div class=“fit scroll”> previously, but now I know the problem lies on “absolute-full” in the q-page-container. Much thanks!

            1 Reply Last reply Reply Quote 0
            • First post
              Last post