Just a note for your documentation team, and a bug report.
kendo.ns
Is documented extremely briefly in the declarative syntax section of your online docs, the gist of the docs go like this:
set kendo.ns e.g.
kendo.ns = "kendo"
This would change your data declarations to : data-kendo-role= (etc.)
This is not correct (as per the latest code drop) setting...
kendo.ns = "kendo"
Recognizes data attributes in the following form...
data-kendorole=
You can set kendo.ns="kendo-" and then be able to use data attributes in the form
data-kendo-role
However, even with enough data attributes recognised to get the app to start, large chunks of declarative markup simply don't work anymore. (As a very basic example, layouts don't recognise data-kendo-header / data-kendo-footer ... there's many more problems with it.)
Switching off kendo.ns and renaming data- attributes back to their non ns'ed form fixes everything.
Where is your issue tracking system, or do you guys pull bug reports in from here?
Jason.
Fishvision.
kendo.ns
Is documented extremely briefly in the declarative syntax section of your online docs, the gist of the docs go like this:
set kendo.ns e.g.
kendo.ns = "kendo"
This would change your data declarations to : data-kendo-role= (etc.)
This is not correct (as per the latest code drop) setting...
kendo.ns = "kendo"
Recognizes data attributes in the following form...
data-kendorole=
You can set kendo.ns="kendo-" and then be able to use data attributes in the form
data-kendo-role
However, even with enough data attributes recognised to get the app to start, large chunks of declarative markup simply don't work anymore. (As a very basic example, layouts don't recognise data-kendo-header / data-kendo-footer ... there's many more problems with it.)
Switching off kendo.ns and renaming data- attributes back to their non ns'ed form fixes everything.
Where is your issue tracking system, or do you guys pull bug reports in from here?
Jason.
Fishvision.