Framework

• C

  QTable with expandable rows and selection
  • ctrengove  

  2
  0
  Votes
  2
  Posts
  7
  Views

  

  If you are using the body scoped slot, then you are building the whole table “by hand”. So, yes. You’d need to implement the selection functionality within the table body yourself too. That is the whole idea behind slots. Scott
• K

  disable workbox logs
  • kenknight  

  9
  0
  Votes
  9
  Posts
  712
  Views

  

  Does anyone know if it is possible, in the current versions of quasar to setconfig debug to false (in quasar.conf.js)without using a custom service worker file? I have tried the following, none of which work: workboxOptions: { debug: false, skipWaiting: true, clientsClaim: true } workboxOptions: { skipWaiting: true, clientsClaim: true, setConfig({ debug: false }) } workboxOptions: { skipWaiting: true, clientsClaim: true, debug: false }
• 

  This topic is deleted!
  • ssuess  

  6
  0
  Votes
  6
  Posts
  33
  Views

  No one has replied

• B

  Virtual-Scroll server side paging
  • bobbyross  

  3
  0
  Votes
  3
  Posts
  25
  Views

  B

  Sorry for the delay… QInifiniteScroll does not really fit the bill as for mobile rendering of large lists it will react slowly and will require reaching the bottom of a page before more is loaded. What I would like to do is allow a user to scroll halfway down a list of say 20,000 items and have the item-fn called once to load the current page of data based on the bounds of the slice size. In the documentation there is an example for using virtual scroll and QTable where when you reach the end of a list it does load more items, but you can only scroll to the end of the current page, whereas the item-fn allows you to scroll anywhere within the length specified (say 100,000 items) and then it will make a call to render the items. This would provide a much better user experience as the concept of paging would not be evident to the user. What I find odd is when using the item-fn on a list of 100000 items as in the examples shown is not reliable. If the slice size is set to say 300 items the item-fn call is delayed and is not initially called until the index reaches about halfway through the first range of 300. After the initial item-fn call it then calls on each scroll from that point on. If it was only called once as you scrolled towards the end of the slice size it would possibly allow for a better paging scenario. Hopefully this makes sense…
• K

  Q-Input Character Restriction
  • keechan  

  3
  0
  Votes
  3
  Posts
  8
  Views

  K

  @qyloxe Hello! Yes I did… But it looks like this masking is tied to a certain length (or maybe I am missing something?). In my case, they are supposed to be “unlimited length”. So I am looking for a more straightforward, cleaner implementation.
• O

  Call a function when the Loading Bar is displayed / hidden
  button axios loading-bar • • Oxi  

  2
  0
  Votes
  2
  Posts
  5
  Views

  O

  I figured it out myself The Ajax-Bar had to be integrated and the event had to be written in it. https://quasar.dev/start/how-to-use-vue#Handling-Vue-Events https://quasar.dev/vue-components/ajax-bar#Usage
• 

  Is there crud generator template like Laravel CRUD Generator ?
  • songwutk  

  1
  0
  Votes
  1
  Posts
  11
  Views

  No one has replied

• 

  QDate Picker with button
  • Artnova  

  3
  0
  Votes
  3
  Posts
  18
  Views

  

  @metalsadman nice, thanks
• J

  Popup edit: save & cancel
  • jmg1340  

  13
  0
  Votes
  13
  Posts
  1340
  Views

  J

  Fantastic, can’t believe I missed that. Thanks.
• O

  Link in transleted text
  • Olimhon233  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  https://kazupon.github.io/vue-i18n/guide/interpolation.html#basic-usage Scott
• A

  Form input autofill background color in Chrome
  • ahmadx87  

  6
  0
  Votes
  6
  Posts
  37
  Views

  J

  HI! I also got the same problem, did you fix it?
• T

  ACCESSIBILITY - Web Content Accessibility Guidelines (WCAG)
  • ted  

  7
  0
  Votes
  7
  Posts
  35
  Views

  C

  @ted, only the one short line at https://quasar.dev/introduction-to-quasar#Best-practices-integrated-by-default is devoted to it in the entire documentation: Accessibility features I agree it’s not as informative nor comprehensive as in the link you provided in your OP. Which is odd, since the Quasar documentation is of top-notch quality on other topics.
• 

  fluid typography - SOLVED
  • qyloxe  

  39
  3
  Votes
  39
  Posts
  2209
  Views

  

  @str - I’m not certain what your problem is. You can set up the heading sizes and font weights as you please. Set them up once and use the same scss or sass or styl file for any other project with Quasar. Scott
• D

  Tooltip for tree nodes
  • DineshDinux  

  3
  0
  Votes
  3
  Posts
  13
  Views

  D

  Hi Arklv, Thanks for you code. Its working.
• A

  This topic is deleted!
  • Alinex  

  2
  0
  Votes
  2
  Posts
  7
  Views
• G

  QTimeline
  • ghada  

  3
  0
  Votes
  3
  Posts
  26
  Views

  G

  thank you it worked !!
• O

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

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• O

  This topic is deleted!
  • omgwalt  

  2
  0
  Votes
  2
  Posts
  4
  Views
• C

  QEditor: Adding custom styles
  • Cobeland  

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• B

  Pass parameters to @filter in q-select
  • bago  

  3
  0
  Votes
  3
  Posts
  14
  Views

  B

  @metalsadman Excellent ! Exactly what I was looking for. Thanks a lot ! Bago…