Merge branch 'dev' of github.com:quasarframework/quasar into dev

docs/src/pages/quasar-cli-vite/upgrade-guide.md

@@ -320,6 +320,8 @@ $ bun add --dev vite-plugin-checker
 
 No need to change anything in the `/src`, `/src-capacitor` or `/src-cordova` folders.
 
+Note that the UI code (`/src`) can now use `process.env.TARGET` (which will be "ios" or "android").
+
 ### PWA mode changes
 
 The `register-service-worker` dependency is no longer supplied by the CLI. You will have to install it yourself in your project folder.
@@ -678,7 +680,7 @@ ssr: {
 ### Bex mode changes <q-badge label="updated for v2.0.0-beta.25+" />
 
 There are quite a few improvements:
-* **The BEX mode now has HMR (hot module reload)** for Chrome only!!!
+* **The BEX mode now has HMR (hot module reload)!!!** (Chrome only)
 * Completely rewrote & redesigned the Quasar Bridge to allow for:
   * Sending messages directly between any part of your bex (app, content scripts, background)
   * Ability to skip using the bridge altogether
@@ -714,10 +716,22 @@ $ bun remove events
 The `quasar dev` and `quasar build` commands now require an explicit target (chrome or firefox). Should you wish to develop for both simultaneously, then you can spawn two quasar dev commands.
 
 ```bash
-$ quasar dev -m bex <chrome|firefox>
-$ quasar build -m bex <chrome|firefox>
+$ quasar dev -m bex -T <chrome|firefox>
+$ quasar dev -m bex --target <chrome|firefox>
+
+$ quasar build -m bex -T <chrome|firefox>
+$ quasar build -m bex --target <chrome|firefox>
 ```
 
+Note that the UI code (`/src`) can now use `process.env.TARGET` (which will be "ios" or "android").
+
+### HMR for Chrome
+
+Significant improvements to the DX:
+* Full HMR for popup/page
+* When changing the background script, the extension will automatically reload.
+* When changing a content script, the extension will automatically reload & the tabs using those content scripts will auto-refresh.
+
 #### The quasar.config file
 
 ```diff /quasar.config file

docs/src/pages/vue-components/icon.md

@@ -532,7 +532,7 @@ Should you want, you can customize the mapping of icon names. This can be done b
   - At the top-level if using Composition API with `<script setup>`
   - In the `setup()` function if using Composition API
   - In the `created()` hook if using Options API
-- Set `iconMapFn` in Quasar Vue plugin options, e.g. `app.use(Quasar, { iconMapFn: () => { /* ... */ } })` (for flavours other than Quasar CLI).
+- Set `iconMapFn` in Quasar Vue plugin options > config, e.g. `app.use(Quasar, { config: { iconMapFn } })` (for flavours other than Quasar CLI).
 
 We will use the `$q.iconMapFn` approach using `<script setup>` in the use case examples below, but the same principle applies to the other methods.
 

ui/src/components/select/QSelect.js

@@ -665,11 +665,9 @@ export default createComponent({
       if (typeof value === 'string' && value.length !== 0) {
         const needle = value.toLocaleLowerCase()
         const findFn = extractFn => {
-          const option = props.options.find(opt => extractFn.value(opt).toLocaleLowerCase() === needle)
+          const option = props.options.find(opt => String(extractFn.value(opt)).toLocaleLowerCase() === needle)
 
-          if (option === void 0) {
-            return false
-          }
+          if (option === void 0) return false
 
           if (innerValue.value.indexOf(option) === -1) {
             toggleOption(option)
@@ -681,14 +679,13 @@ export default createComponent({
           return true
         }
         const fillFn = afterFilter => {
-          if (findFn(getOptionValue) === true) {
-            return
+          if (
+            findFn(getOptionValue) !== true
+            && afterFilter !== true
+            && findFn(getOptionLabel) !== true
+          ) {
+            filter(value, true, () => fillFn(true))
           }
-          if (findFn(getOptionLabel) === true || afterFilter === true) {
-            return
-          }
-
-          filter(value, true, () => fillFn(true))
         }
 
         fillFn()