jQuery UI Widgets › Forums › Lists › DropDownList › DropDownList issuess in mobile
Tagged: mobile
This topic contains 6 replies, has 4 voices, and was last updated by NotAFan 6 years, 2 months ago.
-
Author
-
I’m using the chrome inspector to see my app on mobile devices when I choose for example galaxy s5 and select the dropdownlist the item list is not shown below it but it shows up much below the dropdownlist,
in this link the same thing also happens DropDownListHello pbar,
I tested our demos on the website, with the inspector, and on a mobile phone.
The selected item showed right bellow(or next to) the dropdown list.Can you give us some more information in this manner?
In which demo did you see this occur?Best Regards,
StanislavjQWidgets Team
http://www.jqwidgets.com/Hello,
I have the same error on Mobile when using your DropDownList AND also DateTimeInput.In a real application, there are several input helpers on one page. The error in your DropDownList control results when the control is not yet visible when the page is called because it only has to be scrolled down to show it. Then the offset is not correct. The same error occurs with the DateTimeInput for the calendar and the time pop-ups.
Unfortunately, I encounter errors in almost every one of your controls. Layout, DockingLayout, Menu, Splitter, Scrollbars and ResposePanel behave so buggy in a real application that I had to replace them already. Likewise, your theme builder produces broken code (eg: some color information will not). Some bugs may not be important to you, but I have very demanding customers who notice the difference in pixel height between DocumentPanel and tabbedGroup – not to mention the many others Deficiencies that I have already warned.
Please correct the errors in DropDownList and DateTimeInput in a timely manner, so that I can use at least some of the controls you’ve purchased.Let me remind you of your slogan “BETTER web, LESS time”. Since I had to develop all the above-mentioned controls from the ground up, having dealt with the many detail errors of your controls, MUCH MORE TIME is more likely to apply.
In einer echte Applikation sind mehrerer Eingabefelfer auf einer Seite. Der Fehler in Ihrem DropDownList-Control entsteht, wenn das Steuelementen beim Aufruf der Seite noch nicht sichtbar ist, weil erst herunter gescrollt werden muss, um es anzu zeigen. Dann stimmt der Offset nicht. Der gleiche Fehler trittt bei dem DateTimeInput für den Kalender und die Uhrzeit-Popups auf.
Leider stosse ich bei fast jedem Ihrer Controls auf Fehler. Layout, DockingLayout, Menü, Splitter, Scrollbars und ResposePanel verhalten sich in einer echten Applikation so buggy, dass ich diese bereits ersetzen musste. Ebenso Ihr Themebuilder produziert fehlerhaften Code (z.B: einige Farbangaben werden nicht ) Einige Fehler mögen für Sie vielleicht nicht wichtig sein, aber ich habe sehr anspruchsvolle Kunden, dennen auch der Unterschied in der Pixelhöhe zwischen DocumentPanel und tabbedGroup auffällt – ganz abgesehen von den vielen anderen Mängeln, die ich bereits angemahnt habe.
Bitte korrigieren Sie die Fehler in DropDownList und DateTimeInput zeitnah, damit ich wenigstens einen Teil der von Ihnen gekauften Steuerelemente verwenden kann.Ich erinnere Sie noch mal an Ihren Slogan “BETTER web, LESS time”. Da ich jetzt alle oben erwähnten Controls von Grund auf selber entwickeln musste, nachdem ich mich mit den vielen Detailfehlern Ihrer Controls herum geschlagen hatte, gilt wohl eher MUCH MORE TIME.
Hi GrayWizzard,
We are still unable to reproduce a positioning issue of the dropdowns. We use IPhone 7, IPhone 8 and IPhone X and Samsung S8 in our tests. We also use chrome simulator. Everything works correct.
Regards,
PeterHello,
I used an REAL Samsung Galaxy S8 with Chrome and get this error – not in the simulator.
The error also occurs with your own DEMO.
Set the alignment to bottom and use this with phone in landscape mode to provoke the error: https://www.jqwidgets.com/jquery-widgets-demo/demos/jqxdropdownlist/index.htm#demos/jqxdropdownlist/dropdownlist-open-direction.htmUpdate:
Same behaviour on an iPad, an Samsung Galaxy Tab 10, Lenovo Tablet and an Acer Convertible Tablet (Windows 10).
All devices tested with newest chrome 67.0.3396.99.Hi GrayWizzard,
The devices I wrote are such we have in the office for testing. If we reproduce a specific issue somewhere, we will resolve it.
Regards,
PeterOk,
I will monitor this. -
AuthorPosts
You must be logged in to reply to this topic.