Orbeon dropdown values on reload in firefox not visible - firefox

I have created a form which has several dropdown fields in it.
In my specific case, the same form can be opened in two browsers.
If I edit the form in e.g. Chrome, and reload it in Firefox, all of the values are visible except for the ones which were set for dropdowns.
I've read that the autocomplete="off" attribute should be set to disable caching in Firefox, but unfortunately, that hasn't worked in my case. I've also tried adding the xxf:autocomplete="off" in the form definition, but without any luck.
Is there a known bug for this issue or maybe a solution?
Thanks in advance.

Related

Two quick create forms are opened from Subgrid on "New" button click

I have kind of unusual issue with one of my subgrids in CRM.
On the Main form for an entity i have several subgrids, each of them for records from different entity.
When creating new record from subgrid, all of the forms are opened as expected, except one. It opens two quick create forms.
Forms are not opened normally, one following another. First one looks fine, except there is display name displayed twice. Another form doesn't display any field, just the close button. You can see the issue in the attached images.
I have checked Command for "New" Subgrid button in Ribbon Workbench, and there is nothing more than standard command. I have also tried to do this in several browsers, but the issue continued to appear. I have checked JavaScript functions and none of them is connected with this form.
Now I have lack of ideas what could cause this issue.
I need help for this if anyone had similar issue.

Drop-down menu not enabled in IE11 non-compatibility mode

We are migrating the app to IE11 from IE8. Everything in the app works perfectly well, but for the fact that the drop-down menus in the app don't show up. If you hover over it, it does show a "hand" and on clicking then, it does drop down.
So basically the only thing that's missing is the fact that the little arrow for drop-down menus dont' show up, although it functions perfectly well.
Any idea how to correct this and get the drop-down menus to show up like in regular IE8?
PS: I cannot be using the compatibility mode. I would need to use the regular, non-compatibility mode for IE11. Also, it works perfectly well in compatibility mode.
Here is the code bit for the input type:
<input id="retrieveReports_filterReports" dojoType="dijit.form.FilteringSelect" value="" autoComplete="false"
style="width: 350px;" highlightMatch="all" queryExpr="*${0}*" invalidMessage="Please enter a report name, keyword or key."
name="auto_complete" store="reportStore" onchange = "getMatchingReports(this.value.index)"/>
It seems to be using dojo's dijit library.
I am not able to upload pictures to be able to demonstrate this. But hope this helps!
I found the solution. I had to correct a CSS file to change the visibility to inline or visible [both work] for the drop down arrow.
Another way would probably have been if the Dojo version was upgraded, but that was not in scope.

Two calendars being opened when click on datepicker

I am having an issue for which I can find no Solution. Once I click on a datepicker on this page two date picker panels are opened for them. It only happens on this page. So I know there must be some kind of conflict. Please advise if I should add the source code of the form on the following page
Chronoforms Has an issue with having multiple forms on a single page. I had an booking engine on the very same page and they conflicted. Once I removed the booking engine the form worked perfectly and I did not have the multiple datepicker issue anymore

CakePHP Form Validation rendering error

I was doing the standard CakePHP blog tutorial (using 2.4 beta since it'll be out of beta by the time I make a real site)
On the add form I'm seeing rendering issues, is this a bug or something I've done:-
The validation popup on the second field is messed up, resizable gap above it a bit like the multi line text input its attached to the validator on the first text box is fine
See the drag handle (top right of the popup)
http://snag.gy/U7tKQ.jpg
And you can drag it
http://snag.gy/087fr.jpg
it seems to be connected to the fact the popup is on a field that is resizable
That's chrome's default behavior
The framework used to generate the form won't affect the appearance of that kind of message. Chrome's default behavior (or simply, behavior - don't think it can be modified) for any input with required="required" is to prevent submitting the form if the input is empty with a hint of Please fill in this field (or similar). This is one of the many features introduced in html5 capable browsers.
js interference?
The mentioned drag handles on the hint popup are not normal - that is likely caused by some javascript or a browser extension.
Go there http://diveintohtml5.info/forms.html and scroll down to form validation.
This is HTML5 built in form validation for the browser you're using, inspect the input element. Honestly I'm not sure if you can style them different but to me it looks like the browser is doing this by adding some markup and CSS to the DOM tree that might conflict with whatever else you have there. I personally haven't had the case before.
Knowing your markup and CSS might help by the way.

Manipulate Html from Firefox Extension

I am creating a Firefox extension that is somewhat similar to Firebug. There is a panel (or vbox) at the bottom of the browser that allows users to specify colors to certain Html elements. When they click the OK button, I would like these colors to get updated on the current web page.
I have my JavaScript working when I click the button (i am just throwing an alert), however when I change that JavaScript to change the css or styles of an element (by either using document.getElementById or jquery), nothing changes.
Is there something with Firefox extensions that I am missing? Any help is appreciated.
Let me know if you have any questions. Thanks
https://developer.mozilla.org/en/Extension_Frequently_Asked_Questions#Accessing_the_document_of_a_webpage_doesn%27t_work
You want content.document.getElementById() and similarly for every other construct you use.

Resources