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

    Qtable, the QInput with "v-slot:error" reserves an empty area for message since V1.0

    Help
    3
    11
    324
    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.
    • s.molinari
      s.molinari last edited by

      @christian_f - There are the bottom-slots and hide-bottom-space props in QInput. I believe the latter is the one you are looking for.

      Scott

      1 Reply Last reply Reply Quote 0
      • metalsadman
        metalsadman last edited by

        Yep, though you will lose the animation when error appears.

        1 Reply Last reply Reply Quote 0
        • s.molinari
          s.molinari last edited by

          Yeah, better to put bottom-slots on all QInputs, so they are all “equal” and don’t move around, when errors are shown.

          Scott

          1 Reply Last reply Reply Quote 0
          • metalsadman
            metalsadman last edited by metalsadman

            Could probably omit the message too since it’s inside a qtable, if linting is enough. @christian_f prolly take a look on the upgrade guide too, seeing your on pre v1 and also https://quasar.dev/vue-components/table#Popup-editing.

            1 Reply Last reply Reply Quote 0
            • C
              christian_f last edited by

              Hi, I tried many solutions and I found I can use “true / false / undefined”.
              With “false”, the “bottom-space” is always created and displayed, even if is empty.
              With “undefined”, the “bottom-space” is removed => this is what I need!
              Thanks
              Christian

              1 Reply Last reply Reply Quote 0
              • s.molinari
                s.molinari last edited by

                Are you talking about the bottom-slots prop? @christian_f

                Scott

                1 Reply Last reply Reply Quote 0
                • metalsadman
                  metalsadman last edited by metalsadman

                  @christian_f example https://codepen.io/metalsadman/pen/MMvaqO?&editable=true&editors=101

                  1 Reply Last reply Reply Quote 0
                  • C
                    christian_f last edited by

                    Hi
                    I made for you my first “codepen” demonstration.
                    As I explained at the beginning, the error management is not the same if we compare a QInput alone in a DIV (your example above) with a QInput included in a table cell (my example below).

                    https://codepen.io/christian_f/pen/rEGYOL?editors=1010

                    Description of the buttons and events:

                    • true (default) => the errorMessage DIV is open with a message => of course, the line is not correctly aligned (not a problem)
                    • false => the errorMessage DIV remains open without a message => the line is not correctly aligned (strange)
                    • undefined => the errorMessage is removed => the line is correctly aligned

                    I don’t know if it is an issue or not, I let you decide. I just want to show you the situation so that you understand the subtlety, and possibly report it in the documentation.

                    For my part, I was able to get the right result and I have a screen that works properly

                    Regards
                    Christian

                    1 Reply Last reply Reply Quote 0
                    • metalsadman
                      metalsadman last edited by metalsadman

                      @christian_f doesn’t matter whether my example wasn’t in a table, what you’re missing is the prop hide-bottom-space, like what @s-molinari pointed out and it’s there in my example. updated your example using it https://codepen.io/metalsadman/pen/wLrYdm?editors=1010.

                      1 Reply Last reply Reply Quote 0
                      • C
                        christian_f last edited by

                        Sorry, I was too focused on the context of the table. Thank you very much for your patience.
                        Christian

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