Closed cor2879 closed 5 years ago
@cor2879 this particular version of Edge seems to be included in the Windows 1809 update. This update is no longer available due to data loss issues.
I'd appreciate it if you could point us to a VM image that we can use for testing. Otherwise we'll have to wait for a fixed version to be released.
Thanks for the response. I'll see if we can set up a VM for that. I suspect though that it won't be approved.
On Wed, Nov 7, 2018 at 2:54 AM Tsvetomir Tsonev notifications@github.com wrote:
@cor2879 https://github.com/cor2879 this particular version of Edge seems to be included in the Windows 1809 https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) update. This update is no longer available due to data loss issues https://blogs.windows.com/windowsexperience/2018/10/09/updated-version-of-windows-10-october-2018-update-released-to-windows-insiders/ .
I'd appreciate it if you could point us to a VM image that we can use for testing. Otherwise we'll have to wait for a fixed version to be released.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/telerik/kendo-angular/issues/1895#issuecomment-436535377, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDc0N6pMkoMh11K_RZF0xkPx-8cAPLFks5uspHAgaJpZM4YQ2k5 .
Hello Tsvetomir,
We won't be able to provide a VM with this build of Windows. The build should be obtainable through the Windows Insiders program. Also apologies, I forgot I was signed in with my personal account when I created this bug. I am with Microsoft and can also be reached at my work email dacole@microsoft.com
Thanks,
David C
On Wed, Nov 7, 2018 at 8:50 AM David Cole cor2879@gmail.com wrote:
Thanks for the response. I'll see if we can set up a VM for that. I suspect though that it won't be approved.
On Wed, Nov 7, 2018 at 2:54 AM Tsvetomir Tsonev notifications@github.com wrote:
@cor2879 https://github.com/cor2879 this particular version of Edge seems to be included in the Windows 1809 https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1809_(October_2018_Update) update. This update is no longer available due to data loss issues https://blogs.windows.com/windowsexperience/2018/10/09/updated-version-of-windows-10-october-2018-update-released-to-windows-insiders/ .
I'd appreciate it if you could point us to a VM image that we can use for testing. Otherwise we'll have to wait for a fixed version to be released.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/telerik/kendo-angular/issues/1895#issuecomment-436535377, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDc0N6pMkoMh11K_RZF0xkPx-8cAPLFks5uspHAgaJpZM4YQ2k5 .
I'll check if we can get the fixed update through Insiders, thanks!
@cor2879 Hi David, my name is Lance McCarthy and I'm a Senior Support Engineer at Progress (Telerik/Kendo). I'm also a Microsoft MVP (verify here) and have access to 1809 to test this.
I'm using:
I loaded the Kendo Grid Keyboard Navigation demo but wasn't able to notice any problems moving around the Grid using keyboard arrow keys there.
Just to make sure it wasn't a demo site environmental condition, I ran the code in a standalone StackBlitz, but the issue did not present there either. Here is a very short video (8s) of me tabbing in from the address bar and moving through the Grid using keyboard arrow keys: https://www.screencast.com/t/wyknxR7Ns1q
Did I miss any other steps? I will be creating a VM (with our enterprise keys) for @tsvetomir to keep testing this.
Thanks Lance. Any chance you or Tsvetomir could get on a Skype chat with me to look at this? Then I could walk you through our dev site and see if anything stands out. Maybe there is something we are doing that is interfering with the kendogrid's expected behavior.
On Thu, Nov 8, 2018 at 12:58 PM Lance McCarthy notifications@github.com wrote:
@cor2879 https://github.com/cor2879 Hi David, my name is Lance McCarthy and I'm a Senior Support Engineer at Progress (Telerik/Kendo). I'm also a Microsoft MVP (verify here http://mvp.microsoft.com/en-us/mvp/Lance%20McCarthy-5000553) and have access to 1809 to test this.
I'm using:
- Microsoft Edge 44.17763.1.0
- Microsoft EdgeHTML 18.17763
I loaded the Kendo Grid Keyboard Navigation demo https://www.telerik.com/kendo-angular-ui/components/grid/keyboard-navigation/#preview-0 but wasn't able to notice any problems moving around the Grid using keyboard arrow keys there.
Just to make sure it wasn't a demo site environmental condition, I ran the code in a standalone StackBlitz, but the issue did not present there either. Here is a very short video (8s) of me tabbing in from the address bar and moving through the Grid using keyboard arrow keys: https://www.screencast.com/t/wyknxR7Ns1q
Did I miss any other steps? I will be creating a VM (with our enterprise keys) for @tsvetomir https://github.com/tsvetomir to keep testing this.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/telerik/kendo-angular/issues/1895#issuecomment-437096577, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDc0CT7ALZ3DIA8Wj4wdMwFnbcb9peOks5utHDKgaJpZM4YQ2k5 .
Angular is outside my area of expertise, I had access to the 1809 environment so I helped out with testing the initial report :) I will need to defer to Tsvetomir for further investigation. Since he's located in the UTC+2 timezone (Sofia, BG), he might not be able to respond until the morning.
In any case, I have completed building a VM for him to test on. If there is anything else you can share here, please do so that he has all the info to get started.
If you're not able to share the code publicly, open a Support Ticket here and attach/paste the code, private Support Tickets carry our support agreement's NDA. Then come back here and share the ticket number with us.
Sounds good. Thank you, Lance!
On Thu, Nov 8, 2018 at 1:41 PM Lance McCarthy notifications@github.com wrote:
Angular is outside my area of expertise, I had access to the 1809 environment so I helped out with testing the initial report :) I will need to defer to Tsvetomir for further investigation. Since he's located in the UTC+2 timezone (Sofia, BG), he might not be able to respond until the morning.
In any case, I have completed building a VM for him to test on. If there is anything else you can share here, please do so that he has all the info to get started.
If you're not able to share the code publicly, open a Support Ticket here https://www.telerik.com/account/support-tickets/contact-support-team and attach/paste the code, private Support Tickets carry our support agreement's NDA. Then come back here and share the ticket number with us.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/telerik/kendo-angular/issues/1895#issuecomment-437109991, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDc0I6opB5y4keR2LbDyx0SbCrzLNbRks5utHq9gaJpZM4YQ2k5 .
My tests with the KB Navigation demo did not reveal any issues either. Edge version used:
I would also recommend opening a support ticket, especially if you can share a project that can be used to replicate the issue.
Thank you Tsvetomir, I will look into opening a support ticket.
On Fri, Nov 9, 2018 at 7:36 AM Tsvetomir Tsonev notifications@github.com wrote:
My tests with the KB Navigation demo https://www.telerik.com/kendo-angular-ui/components/grid/keyboard-navigation/#preview-0 did not reveal any issues either. Edge version used:
[image: image] https://user-images.githubusercontent.com/247917/48262865-b6b7e880-e42c-11e8-8982-1fccb689f393.png
I would also recommend opening a support ticket, especially if you can share a project that can be used to replicate the issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/telerik/kendo-angular/issues/1895#issuecomment-437347272, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDc0Pi_atHxiGaD357Jn9qIzlATGX3sks5utXbAgaJpZM4YQ2k5 .
I'm submitting a...
Support request
Bug Report
Current behavior
Kendo Grid is not navigable via keyboard (as described here https://telerik.com/kendo-angular-ui/components/grid/keyboard-navigation/#toc-keyboard-navigation) in Microsoft Edge when the [navigable]="true" attribute is set.
Expected behavior
The grid should be navigable via keyboard as described. This works in Chrome but not in Edge.
Minimal reproduction of the problem with instructions
It's actually quite easy to reproduce. Just load up a UI that uses KendoGrid. Make sure the [navigable] attribute is set to 'true' and populate the grid with any data. Then attempt to navigate it via keyboard. It works in Chrome but does not work in Edge.
Environment
Package versions:
Browser:
Chrome desktop version 70.03538.77 Edge version 44.17763.1.0
System:
Node version v8.12.0 Windows 10