The App Extension adds the stylesheet for you.

If you install the UI package directly, import the stylesheet in your boot file or app entry:

import '@quasar/quasar-ui-qscroller/dist/index.css'

Quasar CLI projects can also centralize the stylesheet in quasar.config.ts:

// Note: using ~ tells Quasar the file resides in node_modules
css: [
  "app.scss",
  "~@quasar/quasar-ui-qscroller/dist/index.css",
],

Yes. After the App Extension is installed, run:

quasar describe QScroller
quasar describe QStringScroller
quasar describe QTimeScroller
quasar describe QTimeRangeScroller
quasar describe QDateScroller
quasar describe QDateRangeScroller
quasar describe QDateTimeScroller

The same generated API is shown on each Developing page.

Use QScroller when the user benefits from seeing nearby choices while they adjust a value. It is best for compact pickers, dashboards, embedded form controls, and kiosk-style UIs. Use Quasar’s native inputs when you need the broadest platform conventions, validation ecosystem, or mobile OS input behavior.

Yes. The scrollers can be placed in popups, dialogs, menus, or appended sections around QInput. The docs keep the first examples focused on the component itself. Add integration examples when your app needs to show a specific popup, dialog, or form-control pattern.

Yes. Style props accept Quasar palette names and CSS colors, so you can tune the scroller shell and inner value area for light or dark layouts.

Use QScroller when you want one wrapper controlled by the view prop. Use the dedicated components when you know the value type up front and want clearer templates or stronger IDE hints.