ParamQuery grid support forum
General Category => Help for ParamQuery Pro => Topic started by: jplevene on February 20, 2026, 12:52:37 am
-
I can't figure this one out, it is only minor.
I have a main grid on a page, but when I later create a new grids, even though focusModel is set to below, this new grids still show a focus box???
{"focusable":false,"onTab":""}
When I get the time I will dig in deeper to find the cause.
Using 11.0.0 with the same code the error doesn't occur
Also setting focusModel: { focusable: false } in gridOptions makes the first item always focused
-
Attached is the filter issue. I assume they are all the same bug. My filterModel is below
{
crules: [{condition:"range"}],
selectGridObj: function(ui) {
// Change the label render
ui.obj.colModel[0].renderLabel = function(ui){ return htmlEntities(ui["rowData"]["NAME"]); };
ui.obj.colModel[0].sortable = false;
},
//options: [], // Set below
gridOptions: {
stripeRows: false, // No stripey rows
numberCell: {show: false}, // Hide the number column
filterModel: {header: false},// Hide search box in the dropdown
focusModel: { focusable: false, onTab:""}, // Prevent the focus box
selectionModel: {type:null, column:false} // Disable row selection
},
title: function(sel, ui, column){
var s = "";
if(!empty(sel))
for(var i = 0; i < sel.length; i++) {
s += (s===""?"":", ") + depots_ids[ sel ];
}
return s;
}
}
-
Do you have a temporary fix to this until the next version is released, or is the next version with the bug fixes going to be released soon.
-
Setting focusModel: { focusable: false } specifically restricts focus via pointer devices (mouse/touch). It does not prevent focus via the Tab key or programmatic API calls.
When the filter dropdown opens, the host grid programmatically sets focus to the first option to ensure keyboard accessibility. With focusable: false enabled in the filter's gridOptions, users are prevented from focusing options via mouse clicks, but the automated programmatic focus still functions as intended.
If you are experiencing a different behavior, please provide a JSFiddle or a list of steps to reproduce the issue.