[CaptainBliParticipant]

The issue may be discussed but with only a hint of a solution given in your “Set TimeZone in to jqwidgets datetimeinput” thread. Yes the browser handles time differently, yet there should be some way to provide the date back to the widget without us having to change the value so that it shows up correctly like a property in the widget that says local time or UTC. That would make this control a better control.

[CaptainBliParticipant]

So I understand that you don’t see it because you are on the East side of UTC or a positive timezone offset. So when timezones interact to your dates, the date won’t be offset unless you are working in the late evening. The problem is a time truncation occurring causing the date to be one day earlier. I don’t see a way for us (your clients) to offset the time stamp every time we try to use the date picker by our timezone offset or rather the timezone offset for each user that will see the control on our pages.

Does anyone have a good solution to this? It is very frustrating to find a set of controls that say they work and don’t.

[CaptainBliParticipant]

Actually I meant across protocols not domains.

Actual message:
“Blocked a frame with origin “http://” from accessing a frame with origin “file://”. The frame requesting access has a protocol of “http”, the frame being accessed has a protocol of “file”. Protocols must match. applyWidget jqxcore.js

[CaptainBliParticipant]

instance.createInstance(args);

Throws the error in $.jqx.applyWidget jqxcore.js

What is happening in there to be calling CORS stuff? I am running all kinds of JavaScript and accessing images other javascript files and everything inside of an iframe that houses the Layout Widget and yet this code throws the error. Everything seems to come through and looks OK but the code throws the error.

What does createInstance do that is trying to make a request across domains?

[CaptainBliParticipant]

Note that even in the demo in jqxknockout/combobox.htm simply add in an image to the add button makes the button stop working.

<button id="addButton" data-bind="jqxButton: { imgSrc:'../../images/add.png'}" type="submit"></button>

or the remove button:

       <button id="removeButton" data-bind="click: removeItem, jqxButton: {imgSrc:'../../images/add.png'}">
                Remove</button>

The trigger starts working again as soon as you remove the imgSrc.

[CaptainBliParticipant]

To help others: in order to close the pop-out menu when minimized I used trigger(“click”) on the icon like

$(".jqx-menu-minimized-button").trigger("click");

I still have not been able to find out a way to have keyboardNavigation to work. This is definitely a bug in the code. I have to have keyboard navigation in order for this to be a viable solution.

[CaptainBliParticipant]

It appears to be related to the keyboardNavigation option. If I take this out then the minimized menu itemclick’s work, though I still can’t close the menu programmatically. And I need the keyboardNavigation.

[CaptainBliParticipant]

As I mentioned previously that if you take any example of menu and ask it to minimize and have keyboardNavigation, jqxMenu(“minimize”) it will no longer trigger itemclick or autoclose or act like it does when it is non-minimized. Example:
Fiddle Example

I would like it to close on click as well. Can we close a minimized menu? I have tried jqxMenu(“close”) with no success. Only upon clicking on the minified icon will it close. I haven’t yet tracked down how that works so that I can call it too.

[CaptainBliParticipant]

itemclick only triggers on the main menu toggle. Further, the menu doesn’t reload in the same div as before minimizing, thus causing trouble with the predefined click handlers.

[Author]

Posts