I'm having an issue with hidden (relevant='false()') textarea controls. When tabbing across the hidden control (ie hitting tab in the previous control) the focus disappears for a moment then reappears in the same control. Tabbing twice quickly will get to the next control successfully.
To recreate, create a 3 control form: input, textarea and input. Make the textarea visibility=false(). Test the form and tab away from the first control.
Using Orbeon 4.3 PE. Doesn't occur with hidden input or output controls.
Anyone seen this before?
Regards
Jez
This was due to a bug (issue 1387), which is fixed as of Orbeon Forms 4.4.
Related
I have a large project on Vaadin, it works fine on Vaadin 7. But i have start to upgrade it to 8.0 and then to 8.1 versions. Everything is fine but focusing on ComboBoxes inside Grid. It sometimes works, but sometimes not. I look at debug console online and see that there is command to set focus received. But it not always really set focus on right component. On Chrome focus can lost from all components, in Firefox focus stays on previously focused component.
I have created simple testing Servlet with Grid component, which has some ComboBoxes as columns. It must imitate problem from large project's Servlet.
On each ComboBox added valueChangeListener, which moves focus to next ComboBox. At the last ComboBox there is moving focus on next line first ComboBox. And so on, until to last line, where it move focus on first line first ComboBox.
In test Servlet i cannot find error, all works like i want. Almost two weeks i tried to solve my problem, but cannot.
Update 2017-10-18:
I think i found my problem. There is an focus lost occured if line with focused component moves to another position.
I attach simple example. It is an Vaadin Servlet with 2-columns Grid. For focus testing i added static trigger with button. Open servlet in two browsers, select some values in ComboBoxes and play with buttons. On press button in first page it must react on second page and mix two lines. Periodically check focus on second page. On some button press line with focused ComboBox will move to another place and lost focus.
Link to example source on Vaadin forum
Link to example source on Dropbox
I am currently using input text fields that spawn a chooser (listview with various entries) when they are clicked on. Testing this on the appMobi emulator works flawlessly; however, when testing it on an iPhone, the default keyboard appears when the text fields are touched and then quickly disappears to be replaced by the chooser.
Is there a way I can prevent the default keyboard from showing with JQM?
If they require user input, then you can't prevent the browsers' default implementation (at least in a x-browser friendly way). They is certainly no solution with JQM.
I suggest you style your own text box from a div or similar, using html/css. With js you can then wire up the chooser to this element.
I have multiple sets of jQuery radio buttons on a jQuery modal dialog. Clicking one in each set hides or shows divs. Anyway, they work perfectly in Chrome, but in FF and IE, they work hide/show the divs properly... but they start disappearing as they're clicked.
I've tried adding plain radio buttons that do nothing, but they still disappear individually as they're clicked. Am I missing some sort of declaration?
I would post the code, but it can literally be a copy from the jQuery website for radio buttons and they'll still disappear.
Thanks for any help.
Have you tried the same example page from another system? If all examples you can find have this behavior, I'd start to suspect your display driver or even hardware. Give a link for a page that you see the problem with, and we can see if it happens for us.
I'm still not quite sure what the problem is, but I implemented a work around.
In Chrome, I remember I had to add an unused jQuery radio button at the top... that hides when the dialog is opened... and "unhides" when the dialog is closed (the dialog is hidden when closed, so the user doesn't ever see this radio button).
For some reason I had to add another one of these jQuery radio buttons that hides and unhides itself to prevent the disappearing jQuery radio buttons in IE9 and FF. So in my case, Chrome required one of these fake buttons... while IE and FF needed two.
Anyway, I think the root of the problem stems from my overall layout template. I think multiple divs all over the place are screwing something up somewhere.
I'm just an amateur programmer so I know this isn't the solution that I'm sure many people would be looking for, but it works for now so at least I'm able to move on.
I encountered yet another problem with ribbon. When I have two forms (one of them is main) and I put ribbon on both of them, they behave strangely. When I open the second form by Form2.Show;, every time I click a ribbon menu button on the second form, it loses focus and the main form gets it.
This happens at pure blank project, so what could I possibly be doing wrong?
Here is a video, just in case: Watch YT
And to be clear, the Action1 button has only Caption:='a'; code.
The ribbon control assumes that there is only one per application, and misbehaves if it is not the only control. You could try to modify the Ribbon.pas code, but it is doing some hacks that probably rely on Ribbon.Parent being Application.MainForm only.
SO I have a select box that I fill dynamically. I discovered that once the SELECT gets longer than the page, it automatically becomes a dialog listview.... which is TERRIBLE!
When this happens, the page refreshes when the dialog is closed and my whole page starts over....
Has anyone experienced that and do you know how to shut it off?
Thanks!
Todd
You could use the native look and feel?
http://jquerymobile.com/demos/1.0.1/docs/forms/forms-all-native.html
Native form elements & buttons Although the framework automatically enhances form elements and buttons into touch input
optimized controls to streamline development, it's easy to tell jQuery
Mobile to leave these elements alone so the standard, native control
can be used instead.
Adding the data-role="none" attribute to any form or button element
tells the framework to not apply any enhanced styles or scripting. The
examples below all have this attribute in place to demonstrate the
effect. You may need to write custom styles to lay out your form
controls because we try to leave all the default styling intact.