Hi,

I tried the new version of Kendo DataViz. However, I noticed a degression of how markers are handled for the area chart. In Q3 2013, when hovering a value, the marker would show itself. In 2014, it does not anymore. It's quite bad from a UX point of view because of the loosed context. You can see the problem in your demos too: http://demos.telerik.com/kendo-ui/dataviz/area-charts/index.html

I have a grid setup and I set an interval so that it reads the dataSource every few seconds. This works fine on desktop and iPad (mostly).

The issue I'm seeing is that if you're scrolling the grid on iPad during a 'tick' (when I do grid.dataSource.read()), the grid freezes completely and I can't scroll. Oddly, the data still updates.

To reproduce:
I set up a JS Fiddle: http://jsfiddle.net/dmathisen/ERgkA/
(the numbers don't update but that's not the point, the issue is still reproducible)

1) Open in an iPad
2) Scroll vertically left and right for a couple seconds.
3) After 2 seconds, grid.dataSource.read() will trigger and the grid will freeze up and scrolling the grid breaks

Just started using Kendo.UI and I can't seem to find any documentation on how to do what I need in JavaScript. I have a ORM Entity Model I'm accessing in the web project via a web service (oData/JSON). I can get the top-level data of any table just fine. But let's say I have a table called Devices (because I do) and it has a association called DeviceHasLocation (because it does) and I want to display the Name of the associated Location in a grid of Devices. What would the code for that look like? 

I need to do something similar for a LOT of these associations, so a reusable methodology would be much appreciated.

Hello,
we are using Kendo components to build the a multibrowser UI for a complex financial web application.
We use the library kendo.all.min.js library, version 2013.2.918, to run the client frontend both on desktop and tablet, specifically Ipad.
On Ipad we are experiencing the following problem:
when se load the data foer a grid, the loading operation terminates but the data is not visible and the grid remains empty. If I " play with the screen", say I enlarge it or shrink it, the application seems to reactivate and the data appears, but I believe the data was already there.
This problem does not happen on Windows PC with Explorer/Chrome/Firefox browsers.
Unfortunately I don't have a Mac for further debug
The Ipad info are:
Version iPad 7.0.6 (11B651)
browser 7.0
Webkit 537.51.1
Safari 9537.53

Though the question is vague, please give me a hint,

thank you for your help

best regards

Marco

My endless scrolling listviews were working (excepting a couple of bugs that I've already brought up on this forum) until I updated to v2013.2.1024 and now I get the following error: 

"Uncaught Error: the DataSource does not have page size configured. Page Size setting is mandatory for the mobile listview virtual scrolling to work as expected."

I found that this only happens when I use declarative binding. This problem also occurs in the latest available beta v2013.3.1030.

Cheers
Dean

Hi there, it's me again with another ScrollView-issue:

I have an array of knockout-viewmodels.
For each viewmodel, I'd like to get a page in my ScrollView-instance.

Now I get the problem described in your documentation: If there's a whitespace, you'll get an extra page.
Unfortunately the template-workaround doesn't work here and I cannot work with datasource as my knockout-bindings are initialized before I initialize kendoUI Mobile (there is much more going on in the app, so changing that order would be a lot of refactoring which I'm trying to avoid).

Because I can't find a way to define a specific number of pages (as a simple workaround), I'm hopping for your help :)

Thanks for your help!

Cheers,
Richard

Hello, I'm trying to bind an array of primitive objects to an un-ordered list using the example from the getting started documentation here:

http://docs.telerik.com/kendo-ui/getting-started/framework/mvvm/bindings/source#source-binding-to-array-of-primitive-objects

I'd like to add a button along side each list item that, when clicked, removes the item from the list.

When I run the example above without the addition of a click event handler, everything works fine as the below link shows:

http://jsbin.com/muzameko/3/edit

However, when I add a click event handler to the same span, or even a neighboring span element as below...

http://jsbin.com/muzameko/4/edit

I get the following error in Chrome's console:

Uncaught TypeError: Object Coffee has no method 'get'

and the rest of the list fails to render correctly. Is this a bug or am I binding in an unusual way?

Thanks in advance, Sam.

I am using your Mobile ThemeBuilder and I can not get the selected button's text in the ButtonGroup to change color.  I've tried many different ways to change the color through declarative css styles. (No Inline, I can not use inline styling).

This is the style that is generated by your theme builder:

.km-ios7 .km-view .km-navbar .km-view-title > * .km-button.km-state-active .km-text {
    color: rgb(0, 63, 135);
}

It does not work.  The selected button's text is always white.

Thank you for your time.

The Kendo UI Team has identified a problem with the Popup in Firefox, which affects all Kendo UI Widgets that use it. The issue only manifests itself when the page is scrolled as inability to open the Popup there.

We have identified the root cause of the problem and all following releases, including internal builds, will be free of this defect.

The corrected minified Popup script is also available for download as attachment to this post. You can load it right after the combined scripts in order to avoid the issue.

There is an easy alternative fix with CSS only. Force your desired overflow on the document element, like this:
.k-ff {
    overflow: inherit !important;
}

The selector above will affect only Firefox. Adjust the overflow to your needs (visible, auto, hidden, scroll, inherit).

I am working on creating a new application using the Kendo SPA framework.  One must-have feature is the ability to cancel navigation to a route, for example - don't allow the user to navigate away if the current has unsaved changes.

According to the documentation, this should be as simple as calling e.preventDefault() in the router's change event.  And this does work in the simplest scenario - if you wire up the change event and call preventDefault, the route will be cancelled, you stay on the current view, and the url is reverted back to it's original value.

However, I feel that is overly simplistic.  In reality, you would never simply just cancel the route.  You need to make a call to see if there are unsaved changes so that you can determine whether or not the navigation is allowed.  And this is where my problem lies.

In my scenario, I have a callback that is executed in the router change event that checks to see if the navigation is allowed.  If I hit a route that I cannot leave, then I call e.preventDefault and the view does not change (which is good), but the route does not revert back to the original value (which is bad).  So now the wrong url is showing in the browser.  What's worse is that if I now attempt to navigate to a different route, this will cause an infinite loop where the change event keeps firing and being cancelled, which locks up the browser.

I have created an example in JS Bin that demonstrates this behavior - http://jsbin.com/EXARiTiJ/10.  Here are the steps to recreate the issue:

1.  When the page loads, it will first navigate to the Home view
2.  Click on "Orders" to navigate to the Orders view.  This will navigate correctly and update the url appropriately.
3.  Click "Products" to navigate to the Products view.  Again, this will navigate correctly and update the url.
4.  Click "Orders" to navigate back to the Orders view.  The code in the change event will call preventDefault and this will trigger the error condition. The Products view will remain visible, but the url now shows "/orders" - however, it should still show "/products".
5.  Now click "Home" to try to navigate to the Home view.  Be warned though, this will now create an infinite loop and lock up the browser.

It seems like this is a bug with the router, but maybe I am missing something.  Is there a different way that I should be handling canceling the route navigation?  If this is a bug, I would like to know if there is a workaround/fix that can be implemented, since this feature is a must-have for my application.