extjs 6.5.* (1, 2) combobox bug on iPad and Google Chrome - ios

While testing my webapp on an iPad (ios 10.3.3) i came up to something that looks like a framework bug.
All the comboboxes with queryMode set to local were not opening the dropdown popup on combobox's button click.
(Tested on Chrome v. 63.0.3238.73)
I would add a fiddle but you can test it at:
extjs 6.5.2 modern combobox, example usage
and
extjs 6.5.1 kitchensink modern, checkout form (Shipping Address -> State)
Anyone else faced that bug or is it a device problem?
Any known workarounds?

I came up with a workaround and I am posting it in order to help someone with the same issue.
Adding a minHeight to the floatedPicker config solves the bug.
floatedPicker: {
minHeight: 100
}

Related

Jquery-mobile popup zlevel issue on Android 4.0

With Jquery mobile 1.4.2 (latest currently) I've encountered a problem with the popup feature on Android 4.0 (Ice Cream Sandwich).
When displayed the popup appears behind the rest of the page content (can be simulated with a z-index:1 on ui-popup-container)
My solution to this problem was a bit tweaky : add a -webkit-transform:translateZ(0) :
.ui-popup-container {
-webkit-transform:translateZ(0)
}
(I had to shared this, I lost to much time on it !)

Issue with Zurb Foundation anchors in heading tags on Android Froyo

On Android Froyo (Galaxy S phone) default browser, the issue I'm seeing is when I tap on a link that is in a h1 or h2 or any heading tag, the active link box appears above the link. In some cases the box doesn't appear at all and the link doesn't work. It appears to only be links in heading tags. I've also tested it on iPhone 4s and Android Jellybean, and they work fine. I've narrowed it down to something inside foundation.css, but I can't find the CSS that's doing it or if it's a "feature" of Froyo browser.
Has anyone else seen this? Is there a fix?
TIA,
Chris
I think I found the problem. In foundation.css (Foundation 4) text-rendering: optimizeLegibility. It may be related to WebKit bug 41363.
I nullified that node and things are back to normal.

jquery ui autocomplete - suggestions show only once on BB5

I am using jqueryui autocomplete and it works great on desktop and most of the mobile devices - ipad, iphone ,etc. However on blackberry 5, when I type in pis for the first time it shows the suggestions list immediately. when I break see the list and type in additional letter, I dont see the suggestions anymore. I change the text, do whatever and no suggestions until I reload the page and it repeats the same issue again. Should I do anything different with BB5? Thanks
What version of jQuery UI are you using? Blackberry 5 only has limited support for JavaScript 1.6 and this may be why your implementation is functioning oddly. It may be that there is nothing you can do to fix it for BB5 users.

Change page in PhoneGap 1.1.0 with JQm Rc 2

I'm using phoneGap to create smartphone apps, but after I updated my app from jqmobile beta 2, to jqmobile rc 2 my app can't change page.
The code looks like this
Afbudsrejser
If somebody could help it would very much appreciated, Thanks
Brian
Instead of calling $.mobile.changePage(), simply use the url:
Afbudsrejser
jsFiddle example

Smart GWT: Combobox Item pick list issue

I am using Start GWT 2.5. I am using combobox item. While opening a pick list and if pick list is having only one option, it shows horizontal and vertical scrollbars. Image is attached representing the issue.
Code:
DynamicForm form = new DynamicForm();
form.setIsGroup(true);
form.setCellPadding(5);
form.setNumCols(2);
ComboBoxItem comboBoxItem = new ComboBoxItem("TestCombo");
comboBoxItem.setValueMap("test1");
form.setFields(comboBoxItem);
form.draw();
Can any one help me?
I know this is a very old post. But it might help someone.
This issue has been resolved in the newer versions of SmartGWT. All the releases above SmartGWT 2.5 reflects that the problem has been solved.
I've noticed the same issue, and in my experience it only occurs in Google Chrome in development mode. Try debugging in Firefox, by using the Firefox plugin which can be found here. That ought to provide a workaround to the problem.
Note: if the problem still occurs in Google Chrome after you've deployed your application, I strongly recommend that you open a ticket at the SmartGWT Google Code project.

Resources