Posts made by rstoenescu

Quasar Framework v0.17.19

New

• Prevent q-btn loading state from resizing the button #2799 (#2818)
• allow overriding QSelect options QPopover behavior. (#2771)

Fixes

• Fix NaN on IE/iOS v6 (#2838)
• QAutocomplete: Unprotected access to inputEl in mounted() #2840
• q-editor code button isssue #2827
• animScrollTo - set final scroll position if no time left for the animation (#2824)
• Autocomplete prop value-field became mandatory for static lists in 0.17.8 #2819
• formatDate: use localization options passed as 3rd parameter (#2809)
• QBtnToggle: Allow disable from options as stated in the docs (#2792)
• QChip with QTooltip improvements #2816
• Slider/range not dragged in specific scenarios #2794
• opts.expires not tested for proper type in cookies plugin #2793
• QInput: size adjustments for firefox (#2801)
• QDatetimePicker: add checks for el in __scrollView (#2800)
• QInfiniteScroll: fix poll addEventListener added before debounce (#2765)

Quasar CLI v0.17.23

New

Upgraded to Quasar Framework v0.17.19

Security

Upgraded webpack-dev-server to v3.1.14 (webpack-dev-server “Missing Origin Validation” vulnerability #216)

Hi,

Can you be more specific? What columns are you referring to? Are you referring to https://quasar-framework.org/components/flex-css.html ?

@Jezzta667 Thanks for raising this issue. Patreon is not required. It can be sidestepped completely. For this I can issue invoices and we can use direct wire-transfer. Any such amounts are included into the bonus. If anyone is interested, please contact me by email (razvan.stoenescu@gmail.com)

Hi,

We have an important announcement to make. We were contacted by Think Health Data, Inc. with the following message for the awesome Quasar community:

I am excited to announce that the development team at Think Health Data has agreed to sponsor Quasar and match all contributions for monthly contributions made in the month of December dollar for dollar up-to $1500 per month. Think Health will continue to match each month as long as your contributions continue. Importantly, the contributions come with no strings attached and allows the Quasar team to continue developing on the road map it chooses. The Think Health team asks that all contributions be made with the same respect for the Quasar team’s autonomy and vision.

So your donations will count twice as much now! Many thanks to the people who understand that there are development costs involved for bringing you a free Quasar Framework and they contribute – Quasar exists because of you!
https://www.patreon.com/quasarframework

And regarding the data table… that’s why there’s pagination!

Having 30k entries takes a whole lot of time just to add to DOM through vanilla JS… Saying it’s a Quasar performance issue in this case is simply ridiculous. By using any framework it does not mean that the browser itself can run much faster with its basic operations. You as a developer has the responsibility to not render a million DOM nodes simultaneous on your page too then ask why it’s taking so long to render! There’s pagination, there’s autocomplete, … You just need a little imagination.

This will change with v1.0. The new QSelect is much smarter.

@jeffatpf Thank you! Financial support is much needed. Feel free to connect with me by email.

That’s not Quasar code… so check your deps?

Are you sure you are using quasar.conf > build > transpileDependencies to add your deps that need ES6 transpiling? https://quasar-framework.org/guide/app-quasar.conf.js.html#build-Property

If your script content is static, then you can add it directly to your src/index.template.html. Otherwise, use Quasar Meta Plugin as indicated above.

“disable” is a prop while “disabled” is the CSS class. The “disable” instead of “disabled” is due to an old Vue bug and it kind of stuck with Quasar due to legacy.

Way to do it: https://jsfiddle.net/rstoenescu/sza3qncg/4/

Few comments:

1. Quoting you: “So is quasar promoting not doing things correctly and breaking accessibility?” and “my suggestion/recommendation to address things like this in the quasar framework” --> No, Quasar was actually the first Vue framework working on accessibility. We take great pride in the components being accessible.

2. This confusion of yours comes from the fact that you are misunderstanding the concept of a slot. You’re using slot=“footer” yet you wrap it with a DOM element (<form>). Slots are strictly connected to the component upon which you are using them, and it’s equivalent to saying: “hey, component X, this slot needs this content” then the component fills its own template (not your template!) with the indicated slot content. So, wrapping a slot with an element makes no sense… because it’s a slot, it’s not content that you can wrap or place in a specific DOM tree of your choosing for the component — the component decides where to put it.

3. Finally, some thing that you should be aware of regarding your comment “Vue doesn’t promote this behavior and neither should quasar”: You are operating with Vue components, not native form elements. <form> is designed for native form elements. In any case, this is not to be taken as "Quasar components don’t work with <form>", because QInput, QButton (which actually even has a “type” prop: submit, reset, …), … do work. But just be aware these are components, not native form elements.

-Razvan

@n-taddei yes!

@jeffatpf the entry.js IS being rewritten on each quasar dev/build. Any chance I can take a look at your repo? Must be some bug outside of Quasar CLI, just don’t know what.

But nothing changed in this regard

“width” prop is a Number, so give it a number like metalsadman suggested: :width="392".

Please log a bug so I can take care of it. Thank you!

Use slash ("/") instead of dash ("-") for date separator, always, due to the many bugs in JS Date() object.

Bad: 2018-10-10
Good: 2018/10/10

This version installs Electron v3 (instead of v2) when adding Electron mode.

For those that have already added Electron mode, a simple npm/yarn upgrade of the electron and electron-debug packages to v3.0.8 and v2.0.0 respectively is enough.

Enjoy!

Enjoy! (Quasar v1.0 still has full focus – first alpha to be released this month)

Quasar v0.17.18

New

• Update to QSelect - dropdown icon not being displayed when using readonly (#2466)
• QTimelineEntry: Allow titles slots for Timeline Entries (#2736)
• Hungarian i18n pack (#2703)
• Update and improvement of Traditional Chinese i18n pack (#2674)

Fixes

• QAutocomplete - valueField should not have default value #2738
• Safari 9 notification hiding glitch (#2660)
• QInput: change the way clearValue is computed (#2690)
• Timeline: Fix overlapping property “display: inline-flex;” styles from .material-icons (#2667)
• QTabs: nested tabs position (#2722)
• Centering the time on date time (#2684)
• QDatetimePicker Mat: enforce min-width in modal and popover (#2672)
• Add default callback function to openUrl (#2661)

Quasar CLI v0.17.21

Updated deps: Quasar Framework v0.17.18, Quasar Extras v2.0.9, Webpack v4.25.1, workbox-webpack-plugin v3.6.3, and many others.

Quasar Extras v2.0.9