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

    If q-tab "icon" prop is a string, how can I use e.g. FontAwesome fonts here?

    Help
    5
    8
    2301
    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.
    • C
      Chanlito last edited by

      I don’t know how to solve this.

      1 Reply Last reply Reply Quote 0
      • rstoenescu
        rstoenescu Admin last edited by

        Hi, not supported currently.

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

          @rstoenescu Is there a way around this? Because I don’t think material Icons are enough.

          1 Reply Last reply Reply Quote 1
          • rstoenescu
            rstoenescu Admin last edited by

            There will be in the near future.

            1 Reply Last reply Reply Quote 0
            • P
              packy last edited by packy

              Would importing Font Awesome Font and changing $icon-font-family to FontAwesome not work? I would also like to know more on this since most app branding you need to have your own set of icons, especially for tab bars.

              -Do you have to make your own icon font family and pass it in like I mentioned above?
              -Can you just pass in an SVG to the icon prop opposed to a Material string?

              Any help would be great.

              Cheers!!!

              1 Reply Last reply Reply Quote 0
              • rstoenescu
                rstoenescu Admin last edited by

                Currently not possible because Material Icons is a ligature font while the others are not. End result is the different markup these font icons need. For material you need to have a text element inside the <i> tag (<i>alarm</i>) while for Fontawesome you need to add a class name to the tag (<i class="fa fa-calendar"></i>).

                As a result, v0.14 will have a q-icon component which will deal with the correct markup.

                1 Reply Last reply Reply Quote 2
                • S
                  siba2893 last edited by

                  Is this fixed in the version 16.0, cause I still cant use font-awesome in tabs neither with the string or putting a <q-icon> inside

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

                    This is working for me in 0.16.4.
                    q-route-tab example:

                              <q-route-tab
                                v-if="isLoggedIn && checkFeature('events')"
                                label="Events"
                                to="/events"
                                name="events"
                                icon="fas fa-list-alt faa-pulse"
                                class="faa-parent animated-hover"
                                replace
                                slot="title"
                              />
                    

                    q-tab example:

                              <q-tab
                                v-else
                                label="Sign Out"
                                name="sign-in"
                                icon="fas fa-sign-out-alt fas faa-pulse"
                                slot="title"
                                class="faa-parent animated-hover"
                                @click="signOut"
                              />
                    
                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post