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

    IE11 supportIE: true not working

    Help
    5
    18
    908
    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.
    • A
      apavel last edited by apavel

      I removed the gauth boot file (the issue was with vue-google-oauth2) and it works!! thanks!

      it required some fiddling to get it to look right on IE, for example col doesn’t work well.

      This is the contents of my gauth.js boot file:

      import GAuth from ‘vue-google-oauth2’
      import Vue from ‘vue’
      import config from ‘@/config/config.js’

      const { gauthOption } = config.auth
      // gauthOption.access_type = ‘offline’
      gauthOption.scope = ‘profile email’
      gauthOption.prompt = ‘select_account’
      Vue.use(GAuth, gauthOption)

      do you know how I can add it to the babel-polyfills that quasar uses? Or do I manually have to import polyfills and get it done?

      Thanks!

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

        @metalsadman - Do you know by chance about adding additional polyfills?

        Scott

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

          @s-molinari nope sorry :x.

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

            So setting the supportIE: true flag just ensures that core quasar components work in ie11. And using 3 party code can break the ie11 compatibility. That would be a good thing to add to the ie11 support page.

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

              It’s easy to do a PR! Use the pencil top right of the page. 😉

              Scott

              dobbel 1 Reply Last reply Reply Quote 0
              • A
                apavel last edited by

                Doesn’t quasar compile all javascript into chunks, minify it, etc… I would imagine it runs polyfills on it. I am having trouble understanding how that particular import gets excluded. Am I missing something? If so, there must be a way of including it in the polyfills.

                Thanks!

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

                  @s-molinari
                  I think it would be better if someone that actually understands this issue will explain and confirm what is actually going on here. I just observe that setting the supportIE: true will not always result in an ie11 compatible appiclations.

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

                    I just observe that setting the supportIE: true will not always result in an ie11 compatible appiclations.

                    But, it does, at least for pure Quasar applications. @apavel figured out it was one of his boot files/ supporting packages that was breaking the app in IE11. Nonetheless, if you can better explain your situation, where you aren’t getting an app working on IE11, we can also make suggestions on how to possibly fix.

                    Also, this issue has moved from what it was with IE11 and the quasar.conf.js setting to how to install another polyfill. So. I’ve asked Razvan to pop in when he has time to offer how to possibly plug in other polyfills.

                    Scott

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

                      @s-molinari Thanks for your help. I think I may have to rewrite the module that doesn’t work on IE11. It may be they are using a non-standard polyfill.

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

                        Yeah, and you might in general want to look hard at the need to use IE11. Because, this year, with Vue 3 moving to Proxy objects, support for IE11 will end and thus, inadvertently with Quasar v2 too. Of course, the plan will be to support v1 of Quasar for a while. How long still needs to be decided. But for sure, the future isn’t looking good for IE11 users in the next couple of years. 😔

                        Scott

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

                          Just some feedback. You can add polyfills in a boot file. Make sure they are loaded first (first boot file in quasar.conf.js).

                          Scott

                          1 Reply Last reply Reply Quote 0
                          • S
                            StudioLite last edited by

                            I’m having a similar issue. Did you just remove the boot files altogether?

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