Forum Discussion
- _anomDiebolt_Qrew EliteYou appear to need to call the action ?act=QuickSearch against a table dbid on mobile. I get the same result as you did.
- RoderickDizaQrew Trainee
Hi dandibolt, you know what fix should be made for this? Thank you.
- _anomDiebolt_Qrew EliteI believe that QuickBase is employing user agent sniffing to determine if the device being used is a mobile device.
When I am on a Windows desktop using Chrome I get the following user agent string:>navigator.userAgent
When I emulate Nexus 5X through the Chrome dev tools I get the following user agent string:
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.59 Safari/537.36"?navigator.userAgent
Now you can't change the user agent string in the browser but you might be able to change it in a service worker by manipulating the request header. So theoretically there might be a technical solution.
"Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.59 Mobile Safari/537.36"
However, even if it worked your user would have the weird experience of breaking out of the mobile design and temporarily entering the desktop design for this one URL. And there could be all sort of other display, navigation or browser anomolies.
The bottom line is that somewhere in the history and bowels of QuickBase a developer made the decision to have ?act=QuickSearch not work the way you want on mobile.
This technical question is something I might normally explore as I basically want to know everything about Service Workers but at this time it would be a high effort low impact task not worth my time.
- RoderickDizaQrew TraineeUp