Thanks for your patience on this. We've been doing testing on Edge, Windows 10, and Chromebooks. The following is happening:

By October 5, online help documentation for currently supported versions will be updated to clarify support for these configurations.

By October 5, support bulletins will be posted on Behind the Blackboard about these changes as well as listing known issues with the Edge browser. Admins should review the known issues in determining how to best communicate the use of the Edge browser on Windows 10 at individual institutions. We're working to schedule fixes for these known issues, but if you encounter any others, please report them to Product Support.

We'll be updating the browser checker soon to reflect these changes. I don't have a target date on that one yet, but I'll update the community when I've got it nailed down.

Brent, we asked this question recently (and we are also on Oct 2014) and got the answer below. Seems that they'll be striving to support Win10 and Edge, however per their support policy aren't doing a lot of up-front testing and are instead relying on us to report issues for resolution. We'll be doing some smoke testing soon, and we have our user base on the lookout, so if we happen to notice anything crazy I'll be happy to share.

Yes, we’ve included Windows 10 and Edge browser as test scenarios for the October 2015 release.

Under this stated policy, while we wouldn’t have specifically tested those OS/browser combinations for previously-released and currently-supported versions, we would accept reported issues from the field and work to resolve those issues through standard escalation and prioritization processes.

I perfectly accept that answer of not testing it and going off of what they know from previous scenarios... But this is a brand new browser. I suppose I would have hoped a little bit of testing would have happened.

Thanks Rachel. I guess I'll need to install Windows 10 in a virtual machine and just torture test Edge with Bb myself. Same as I had to do with all the other recent MS browsers. Fun! I guess I just sort of hoped that Bb would have done at least some preliminary testing. I mean, this is only going to be the biggest OS upgrade in history - more than 75% of all computer users in the world. I'd think that would have rated a glance at the new browser that will soon dominate the market.

Yes www.brows@erstack.com if awesome. I am trying to get my school to by me a license. I did the demo copy and was very impressed with the different OS + Browser combinations that they have were available. I was able to update quite few of my JavaScript code for the Browser Check we use just based on that 1 hr access with their demo.

I also received an email yesterday from Pearson indicating that the MyLab and Mastering platforms will not work in Edge. They recommend Chrome or Firefox, which is what I typically tell faculty and students to use with Bb any way. When I googled Bb and Microsoft Edge, I found several institutional sites indicating that Bb won't work with it.

The problem with MyLab and Mastering platforms is that they have Java components and Edge does not support NPAPI plugins like Java. It is setup like IE that has a supported copy of Flash Player, which is also an NPAPI plugin, that is updated with Windows updates just like IE, but Java and MS Silverlight will not work with it.

With the role out of Chrome 45 last week, NPAPI plugins will no longer work with Chrome either. Chrome also had an embedded version of Flash Player that is updated with the update of Chrome. So it looks like you can only recomend Firefox and IE for use.

I thought this information was available from the Blackboard Help website and/or the Behind the Blackboard website? From the Blackboard Help website, there are links like the following for client-supported browsers:

So depending on what version of Blackboard Learn you are running and whether you can access that information based on being managed hosted or self hosted, you should be able to find out what browser is compatible with the Blackboard Learn release running at your institution.

Does anyone know if this process has changed? Inquiring minds would like to know.

The process hasn't changed necessarily, but Blackboard will accept trouble tickets on the most recent browsers released such as Microsoft Edge in their currently supported versions of Blackboard Learn. Those end-user technology support matrixes are usually (from my personal experience) not always updated after the product is released.

Thank you Kristine. I automatically assumed that if you opened up a ticket with Blackboard Support to report an issue and the issue was occurring in a non-supported web browser, Blackboard Support would simply inform you to use one of the supported browsers (via the list available from the Blackboard Help website and Behind the Blackboard). Each semester we update our Blackboard information on our website with what we find in the Blackboard documentation and that's one of the first things we check when an instructor or student reports an issue...oh you are using this from your jail-broken, non-supported phone device...you need to access your course from a device running one of the supported browsers specified by Blackboard.

We also use the "Check Browser" option and ask them to use this as well when diagnosing issues in Blackboard.

We've never approached Blackboard Support with cases once we have determined that the users was not using a specific web browser that Blackboard identified on the Blackboard Help or Behind the Blackboard website.

Thank you, and good to know they might actually work with you if you reported such a case or instance.

Blackboard needs to add JavaScript logic that identifies the Edge Browser using browserAgent =('Edge") and then add an if else statement that will convert browserVersion = '12' to browserVersion = '20'. The need for this version conversion due to the fact Microsoft identify Edge as token browserVersion as 12, basically being after IE11, but if you look at the settings in Edge it shows up as version 20.

Thanks for your patience on this. We've been doing testing on Edge, Windows 10, and Chromebooks. The following is happening:

By October 5, online help documentation for currently supported versions will be updated to clarify support for these configurations.

By October 5, support bulletins will be posted on Behind the Blackboard about these changes as well as listing known issues with the Edge browser. Admins should review the known issues in determining how to best communicate the use of the Edge browser on Windows 10 at individual institutions. We're working to schedule fixes for these known issues, but if you encounter any others, please report them to Product Support.

We'll be updating the browser checker soon to reflect these changes. I don't have a target date on that one yet, but I'll update the community when I've got it nailed down.

Andrew - thanks for catching that page. It looks like it's not properly linked to the source page to get the updated information. We'll work to resolve that so that yes, it'll also receive updates about Edge, Win10, Chromebooks, etc.

In particular I want to note that we've simplified the supported technology tables to move away from any particular OS requirements--essentially if you can run one of the supported browsers on a desktop OS, you're supported, and those supported browser items are minimum versions and up. This means Safari 9 is covered by the supported browsers table without any particular update to the supported browsers table.

In a separate table, we'll keep updating the operating systems and devices tested. We have had a chance to test Windows 10, but we haven't yet specifically tested Mac OS 10.11 with Learn October 2014; even so, if one is using a supported browser on that OS, they're supported (browser-specific NPAPI plug-in restrictions excluded).

For environments running the Ultra Experience, the tables are a bit more expansive because we're defining supported mobile browser versions and also listing the specific mobile devices and operating systems used during testing, although any device capable of running the minimum versions of the supported mobile browsers will be supported.

I am awaiting this before updating our own Browser Check and letting the rest of the school I work for be aware that Blackboard is now officially supporting these things, minus any tools that require NPAPI plugins for Edge and Chrome,

I do see that you all updated the Browser Check for Edge and it identifies it as Edge now instead of Chrome, but once again a version needs to also be rendered as Version 21 is currently in the Beta version now so should be coming out soon. If you team is having issues with the conversion of the BrowserVersion token please have them refer to my previous posts on this thread as currently has has the browserVersion token for Edge as "12" following IE 11, instead of 20. When Edge 21 comes out the browserVersion token will be 13.