I have seen in several posts users being discouraged from using multi
page documents beyond a very limited number of pages. Could someone take
a few seconds to explain why ? Is it for performance (of the browser or
JQM) reasons, because of limits JQM ability ?
The reason I am asking now is because I have always used multi page
docs with something like 15-20 pages/popups etc and never had issues.
This was necessary as the app needed to run offline (saving data
entered in the browser "filesystem"
But I am willing to learn and do things differently, especially as
I am about to embark in a rather complex app powered by JQM. This app
will have to be able to work offline.
I also have in production a mix between multi page document and
dynamically generated pages and by and large it works although I have
seen here several times this practice as "not supported".
What is the state of this ?
I am trying to sort out with the folliowing issue.
I have a system in which the user selects a record to edit in a listview. this listview links to another In the PageBeforechange event, (on the 1st call when toPage is a string) tehre is a json call to the server to get the data entry page definition. I use this data to build teh data entry form (header, content & footer) everything works and is rendered as I intended. Then the user does what he/she needs to do, clik on the save button the data is send to the server and the display returns to the listview.
If now the user repeats the same process a second time. Every thing works (everything is in place) also bar the header which is there but not rendered as a fixed header with a navbar as before. it is just a div, themed but not enhanced.
I have checked multiple times the page div is emptied before generating header, footer & content divs, every button on the form works, with the correct script called etc .... just this rendering issue which drives me potty.
Any hint on where to start looking would be of a great help
Hello. I will try to make myself clear, but I am not a native speaker, so please bear with me.
1- On a single page app, which I have been developing for the last several week, I have a login dialog, as a div with data-role="dialog". I open using js and a call to changePage. All has been working wonderfully so far.
2- I use the swatch "a"
Since 2 days when I open the dialog with changePage, the overlay is completely white. (instead of dark)
What I have done
A: I narrowed it down to the CSS ui-dialog which specifies background: none !important. If I remove it, everything is fine.
B: I have tried specifying the theme on the dialog div ... , on the changePage call .... to no avail.
C: I have checked my markup and the HTML goes through htmlLint ... I am at loss.
If I update the original CSS (which I am trying to avoid at all costs) to remove the background rule on ui-dialog it sort of works: there must be NO transition otherwise the white background flashes.
Question: how can I get the background to be and stay dark ?
I must admit that I am running out of ideas, so any fresh input will be appreciated.