SilicaWebView comboboxes on a webpage don't work
asked 2014-02-11 21:34:08 +0300
Given the code below, the page loads fine, but the comboboxes on the webpage just don't work at least with this page while the very same page works fine on the the default web browser. I didn't find any documentation regarding this issue in neither the SilcaWebView nor the QtWebKit WebView documentation. Google also came up short. Please note that I have only tried it with this webpage so this issue might very well not exist on others. Any help would be much appreciated.
import...
Page {
SilicaWebView {
anchors.fill: parent;
url: "http://m.tfl.gov.uk/mt/journeyplanner.tfl.gov.uk"
}
}
They don't work in Firefox 27 either - or I have no idea what they're supposed to do. And btw HTML has no such thing as combo boxes, so you may wanna elaborate on your question.
Tanghus ( 2014-02-12 05:14:29 +0300 )editWell, I was almost sure they weren't called comboboxes, but since I don't know what they are called I used the term that IMO best described what they were supposed to do. That link works fine with Jolla's browser btw. In order to make any use of the site one needs to be able to set certain options such as the time of departure. The problem might be with the site itself as the tendency in Britain is to be non-compliant with standards so long it works on our 2 favorite proprietary OSs on 3, max 4 browsers. /rant over My interests in html/js are very limited so don't condemn me for not knowing the right terms.
fasza2mobile ( 2014-02-12 05:59:51 +0300 )editSorry, but I'm a bit confused now, so someone please fill me in: The OP wants to know about using a web view but doesn't wanna know about JS and HTML?
Tanghus ( 2014-02-12 07:06:31 +0300 )edit@Tanghus Just to be clear I do have a basic understanding of html and js, I am just not interested in writing web pages nor am I about to write a web browser. The only reason why I am to use a wrap for a mobile webpage in the first place is due to the fact that the API in question is IP locked. To access the API would require a static IP and a high availability proxy server which I would not be able to afford to neither maintain or rent. So to answer your question I do want to know about html and js whatever I need to in order to accopmlish my task, but my interest ends about there for now. Having this out of the way, could you now please help me to establish if the issue at hand is due to a bug in SilicaWebView or is it just the page being non-compiant. Would perhaps changing the user agent solve the problem, would that be possible from QML(if so it isn't documented) or would I have to do it in C++ etc.
fasza2mobile ( 2014-02-12 14:54:30 +0300 )edit@fasza2mobile: My apologies if my previous comment came out as condescending, but if you would start with describing what should happen on that page that doesn't happen in a SilicaWebView it would help a lot. Not that I would positively be able to give any solution, but at least I would understand the problem.
Tanghus ( 2014-02-12 17:15:16 +0300 )edit