Framework

• E

  QTable n rows
  • eloy.silva  

  7
  0
  Votes
  7
  Posts
  41
  Views

  G

  @metalsadman this is also not working unless I reload the page I can see the number of rows changing
• 

  Q-Select Home/End key support
  • labs20  

  3
  0
  Votes
  3
  Posts
  23
  Views

  

  Hi. Thank you! I’ll read your suggestions. Thanks!
• 

  Chrome (but not FF nor Safari) randomly fails PWA update
  • ssuess  

  29
  0
  Votes
  29
  Posts
  64
  Views

  

  well, I reported this as a bug to both the workbox team and the register service worker team, hoping to hear something back.
• M

  Integration with Testing Library
  test testing • • Matheus Ryuki  

  6
  0
  Votes
  6
  Posts
  67
  Views

  A

  Hi all, I’m still struggling with the test setup. Issue: “[Vue warn]: Unknown custom element: <q-breadcrumbs> - did you register the component correctly? For recursive components, make sure to provide the “name” option.” I’m not able to set " localVue.use(Quasar);" which is the clue when using vue test-utils. But the render function of the vue testing-library creates the “localVue” instance internally. Any hints ? Andreas
• W

  q-img preloading
  • walfin  

  2
  0
  Votes
  2
  Posts
  12
  Views

  

  @walfin how do you preload an image when it is displayed?
• A

  Dark mode
  • amoss  

  4
  0
  Votes
  4
  Posts
  17
  Views

  

  https://quasar.dev/quasar-plugins/dark Scott
• A

  When to use quasar prefetch?
  • Abdullah Sohail  

  1
  0
  Votes
  1
  Posts
  6
  Views

  No one has replied

• M

  Quasar and vuefire
  • meesterKurt  

  5
  1
  Votes
  5
  Posts
  143
  Views

  

  @pd76 Here’s an article about Quasar Firebase and Vuexfire: https://dev.to/quasar/to-the-stars-with-quasar-firebase-user-profile-319l Here’s the repo of a demo app( from the article): https://github.com/quasarframework/firebase-sample-apps/tree/master/data/profile
• 

  How to style q-btn with :to
  • sandroden  

  4
  2
  Votes
  4
  Posts
  84
  Views

  P

  Well, I faced the same necessity. In my case, with buttons inside a <q-toolbar>, I was able to workaround the issue as follows. From this <q-btn stretch flat :to="{ name: 'items' }" label="Items" /> To: <q-btn stretch flat label="Items"> <router-link exact :to="{ name: 'items' }" class="absolute full-width full-height" ></router-link> </q-btn> Style: .router-link-active { border-bottom: 2px solid white; }
• L

  QCalendar suggestion
  • LM  

  32
  0
  Votes
  32
  Posts
  627
  Views

  

  @julczka You didn’t give your QCalenda a view (in code above). The actual QCalenda is a component wrapper. Itself does have @click:date and @click:date2, but the other ones come from the specific component being wrapped. Also, to avoid overhead, the events are not fired unless there is a listener for it. Here is a Codepen where you can try out the new events: https://codepen.io/Hawkeye64/pen/eYzJPEW
• H

  Build cache issue
  • hexillion  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  @hexillion you could try quasar clean before a build. https://quasar.dev/quasar-cli/commands-list#Clean
• M

  Unit testing and simulating input
  q-input testing vue-test-utils • • maxant  

  11
  0
  Votes
  11
  Posts
  860
  Views

  S

  @dariosalvi Have you found a solution to this? I’m getting started with quasar + jest and I am running into the same issue. I have a component which wraps a q-input. I would like to test that v-model on my custom component works correctly but when I change the value props there is no input event emitted. The component works as expected through manual testing so the problem must be with jest
• S

  [SOLVED] QPopupEdit in QTable with Vuex data source - Do not emitted save event.
  • sontis  

  31
  0
  Votes
  31
  Posts
  1419
  Views

  D

  I got the same issue now like @sontis (of course while I have the same apporach). Is there meanwhile a solution now? There is no save event emitted by PopupEdit, if there is no :value and no :input handler in q-input avauilable. But that’s the problem, because q-input cannot mutate only the store (and even not directly)
• O

  Method's first letter gets dropped, produces "Property _________ does not exist on type 'CombinedVueInstance'"
  • omgwalt  

  7
  0
  Votes
  7
  Posts
  51
  Views

  O

  @ajmas You’re right. The issue returned for me, but I tried what you suggested with a variation. I just changed that value to false instead of deleting it, and I got the same result as you did. Thanks!
• S

  q-uploader not working on android
  • speterson  

  4
  0
  Votes
  4
  Posts
  27
  Views

  S

  I have solved it. Read it here https://forum.quasar-framework.org/topic/6951/solved-quploader-qfile-on-android
• S

  [SOLVED] QUploader & QFile on Android
  • samodraland  

  2
  0
  Votes
  2
  Posts
  16
  Views

  S

  SOLVED Just FYI to whoever read this. After try & error I found that different platform has different behaviour when handling “accept” attribute. What I did for QUploader & QFile to set accept props value from computed: <q-uploader :accept="accept"> or <q-file :accept="accept"> export default{ computed: { accept () { return this.$q.platform.is.cordova ? 'image/*' : '.jpg, .jpeg, .png' } }, } based on this https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#Unique_file_type_specifiers I have tried use one of them (just extension or MIME) or combine file extension and MIME type but none of them were working. Have to use one option based on platform
• 

  Dark Mode on firefox, always dark
  • Shoooryuken  

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• N

  How to inline css in html for ssr+pwa
  • nfl31  

  2
  1
  Votes
  2
  Posts
  18
  Views

  T

  I am also interested in this topic. Would be glad to get a solution.
• B

  QTime Feature Request
  • btmi  

  7
  0
  Votes
  7
  Posts
  40
  Views

  S

  Oops, this was popup-proxy, by bad Thanks !
• T

  How to control text size in a responsive way
  font-size responsive • • tobiasBora  

  6
  0
  Votes
  6
  Posts
  21
  Views

  

  @tobiasBora said in How to control text size in a responsive way: @qyloxe Sure, I just wanted to avoid to add a compilation step for simplicity I’m afraid it is almost impossible to avoid novadays (compile/webpack/bundle/preprocess/and many more possible steps). If it is unavoidable, than we just need to accept it, and use some kind of intermediate step before deployment and after development and just live with that. The git shared repositories (submodules) are ok for that. I can just use some compilation step for shared modules in UMD projects and put them in separate repository, and use that specific shared repository with compiled code in simple UMD projects.