Open
Bug 2045897
Opened 10 days ago
Updated 10 days ago
Preferences that derive from ComposePreference do not show up in Settings search
Categories
(Firefox for Android :: Settings, defect)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox153 | --- | affected |
People
(Reporter: jonalmeida, Unassigned)
References
Details
Steps to reproduce
- Consider any preference entry that implements
ComposePreference: for example IPProtectionPreference. - Use the Settings search and enter in the search text "Built-in VPN"
Expected behaviour
- The 'Built-in VPN' entry should show up in the search results list.
Actual behaviour
- Zero entries are shown.
Device information
- Firefox version: 153.0.a1
- Android device model: All devices
- Android OS version: All versions
Any additional information?
- It looks like our search indexer doesn't have support for Compose entries, but maybe we can add some index ID or property that could help?
| Reporter | ||
Comment 1•10 days ago
|
||
Petru, do you know if there are appropriate (meta) bugs to link this one against?
Flags: needinfo?(petru)
Comment 2•10 days ago
|
||
(In reply to Jonathan Almeida [:jonalmeida] from comment #1)
Petru, do you know if there are appropriate (meta) bugs to link this one against?
This is a known limitation of the current framework which needs to scan the XML preferences files to build the in memory list of settings items that are available to search through.
After moving to Compose we won't have this data source available,
So the direction that seems to be crystallizing based on recent discussions and tests
Is to on one hand have the Composable UI for the settings screens and on another hand have the list of items that can be searched through exposed through the SettingsSearchProvider contract..
Flags: needinfo?(petru)
You need to log in
before you can comment on or make changes to this bug.
Description
•