You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I configure my router like this (no specific handlers, but I would like defaultHandler to fire)
var router=new $.mobile.Router({
},{
},{
defaultHandler: function(type, ui, page) {
console.log("Default handler called due to unknown route ("
+ type + ", " + ui + ", " + page + ")"
);
},
defaultHandlerEvents: "bc,c,i,bs,s,bh,h",
defaultArgsRe: true
});
defaultHandler is not invoked.
But it is invoked when I specify at least one route:
var router=new $.mobile.Router({
"#index": { handler: function(type){
console.log("Index has been "+(type=="pagehide"?"hidden":"shown"));
}, events: "h,s" }
},{
},{
defaultHandler: function(type, ui, page) {
console.log("Default handler called due to unknown route ("
+ type + ", " + ui + ", " + page + ")"
);
},
defaultHandlerEvents: "bc,c,i,bs,s,bh,h",
defaultArgsRe: true
});
Expected: defaultHandler to be invoked even without specific routes specified. I read through the introduction page, don't think this is intended behavior.
The text was updated successfully, but these errors were encountered:
If I configure my router like this (no specific handlers, but I would like defaultHandler to fire)
defaultHandler is not invoked.
But it is invoked when I specify at least one route:
Expected: defaultHandler to be invoked even without specific routes specified. I read through the introduction page, don't think this is intended behavior.
The text was updated successfully, but these errors were encountered: