I'm using jQuery Mobile (JQM) for an involved single page app. I'm using jQM's page feature, based on some old skool jQuery Mobile tutorials. We're having trouble with menu lockup.
The file jqm-demos.js and jqm-demos.css come from https://github.com/jquery/demos.jquerymobile.com/tree/master/1.3.2
My demo program here:
I've built a generic example, and I'm able to reproduce the fault. The sequence to obtain menu lockup is to select the following menu choices in this order: (1->2->3->4->5->4-> lockup occurs here)
Login
Sales
Summary
Our Team
Reports
Our Team ---> From this point on, menu goes into lockup.
I'm not seeing root causes for this lockup issue. The lockup is very repeatable and is totally visible in Chrome dev tools on desktop browser.
Anybody understand what is causing the issue?
Anybody understand how to isolate the fault using Chrome Dev Tools?
Is there a fix?
Related
What could cause Chrome on mobile to display a web page appears to smudge elements when scrolling the page, such as the below image.
The page uses many icons from Fontawesome and uses Google fonts (font source NPM package), reactjs, jQuery and is packaged using webpack. It includes multiple webpack bundles on the same page.
What could be the approach to troubleshoot this issue?
The example below is at URL https://uquiz.com/DlVmXD:
The issue appears to have surfaced with the inclusion of the additional react component further down the page that shows suggestions of other content. Apparently it doesn't happen when the suggestions aren't displayed such as on this embed URL of the same content: https://uquiz.com/quiz/embed/DlVmXD/what-romance-trope-are-you?embed=true
I have tried it on many devices and it is fine and thousands of people are successfully able to use the page without issue every single day, but many people are reporting this issue. Every person that I have investigated is using Chrome on a mobile device.
I can't find anything to do with this behviour on the githubs for the main libraries that I use so I'm left thinking it could be a hardware issue. Could it be?
We have a phonegap/ionic application targeting iOS. We have been testing with the ipad air simulator (xcode) and ipad air (10.3.3), ipad Pro (11.0.3).
The app is an ionic (v1) app that downloads and loads stand alone html files (the files contain css, html, js in one doc). The documents are typically long forms. In all test environments we are getting odd behavior with selects/drop downs.
When you click/tap on a select the options will appear correctly.
Then when you click/tap somewhere else, blank space or another input field you will usually get the select options bubble again but it will be empty.
In the above image I made my selection from the options and then clicked into the next field.
This was intermittent at first and now it seems to happen all the time. It seems like it has something to do with losing focus but I am unable to see why this is popping back up. I haven't found anything very useful from searching online in regards to this problem.
UPDATE 11/7/17
After more thorough searching this seems to be due to building the app with xcode 9 and/or the use of UIWebView vs WKWebview. I also looked through the code more to see we were already using WKWebView not UIWebView and the problem is still present. As someone mentioned in this thread.
Good thing is Cordova has support for WKWebView too. You have to install the plugin: cordova-plugin-wkwebview-engine
Long time user/lurker, but this is my first time asking a question. Here goes...
The sidr menu on http://jonathanfanndesign.com/lowsleep/ works on my home laptop on IE, works on my iPhone, works on my work computer in Chrome, and works on my wife's Mac, but simply gives me http://jonathanfanndesign.com/lowsleep/#sidr as the result with no menu being pulled out on my home laptop (HP running Windows 8).
The Developer area returns the following errors:
GET http://jonathanfanndesign.com/lowsleep/dist/js/slider.js 404 (Not Found) (index):128
Uncaught ReferenceError: MM_preloadImages is not defined (index):29
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
The slider javascript error is there because it is not being used anymore and I need to remove that from my code when I get to work tomorrow, so I didn't upload it to my site, but this shouldn't affect the sidr menu. Could it be the deprecated event.returnValue? Why would this not work only on ONE computer? I'm sort of freaking out about this because I don't want my sites not working on random people's computers with me not knowing about it.
Thank you for any input you can offer.
I was having this exact same issue that you were having. My Sidr menu was working in just about every browser except Google Chrome on PC (but Chrome on Mac was fine). I also noticed I was having issues opening the menu on mobile also. I would have to very delicately press the menu button for it to work.
I found a solution to both issues here:
https://github.com/artberri/sidr/issues/97
Essentially the solution is basically putting the menu icon within a jQuery click function below your original Sidr function call:
jQuery("#id_of_my_btn").click(function() {
jQuery.sidr('toggle', 'name_of_the_sidr_panel');
});
You'll notice that I used "jQuery" instead of "$". That could also be a possible issue, especially if you have a CMS like WordPress installed with plugins that conflict with the "$". I have had to use "jQuery" instead of "$" on most of my WordPress sites.
Another thing to note is that I also had to put all of my Sidr code into the footer of my website, due to loading issues, which could also be another possible issue.
My problem is not about fixing an issue with a certain IDE, in this case Delphi, but is about finding out the problem that leads to the issue. You probably know that in Delphi 2010 (maybe also in some earlier versions) there's a welcome page that lists recently opened projects. It's actually an html page that also involves some js files to load menus and stuff. But recently my welcome page does not work. It does not list any menus and projects and appears like an erroneus page. I've uninstalled and reinstalled Delphi many times but the problem persists. It seems there's a problem with running some JavaScript command,which I think because of the Windows, not Delphi. Here's how the Welcome Page now looks like
Try to right click and select "browse mode" or something alike. It's a known bug, sometimes it enters "edit mode" and doesn't display correctly. IIRC there's an Hausladen IDE fix pack that corrects it.
I found a couple of rather glaring bugs in SWFAddress, involving IE-based browsers. Both of the following occurred in SlimBrowser (15,000,000 downloads on Cnet) and one in Avant (also several million downloads on Cnet).
Both bugs occur when returning to the original startup screen of a flex app via the back button. Both of them are repeatable using the already compiled sample Flex app that comes with the most recent SWFAddress 2.4 full download (but I have also repeated them after recompiling, and with other flex apps as well.)
Bug 1:
Open SlimBrowser and then open the SWFAddress Flex sample app in a single tab (make sure all other tabs are closed). In the flex sample app click one of the menu bar selections just to take it to another screen. Now hit the browser back button to return to the original screen. Then right-click the browser window tab for the Flex app and select 'close', to attempt to close the Flex app browser window. It causes the browser to crash.
Bug 2:
Modify the code for the starting page of the Flex sample app mentioned above to include a hyperlink to some other website. Now repeat the steps from Bug 1 to go to a different page of the sample app, and then return to the starting page via the back button. (Makes no difference this time if other browser tabs are opened.) Now click the hyperlink you created to navigate to some other site. On the other site the back button is disabled and you can't return to the Flex sample app.
I can of course attempt to debug this myself. Just didn't know if anyone wanted to save me the trouble. Also is anyone still maintaining SWFAddress, and do they even care about this sort of thing. I know people tend to loathe IE so don't know if they just decided not to support it. Also it would include scores of 3rd party browsers that have nothing to do with Microsoft, other than using the IE engine behind the scenes.
why don't you add a new issue on the swfadress bugtracker?