EBMS Tickets

I can't reproduce this. Maybe I'll have to watch her do it.

I can reproduce it on QA (I didn't try PROD). You might have to be logged in as a user that has a default Board selected (not sure if you have one)? When I go to the Upload Document page, I can unselect the pre-selected Board, but I am unable to select any other Boards (no red check appears).

I've tried on QA and DEV, Crome and Edge, my own account and Test Board Manager, and I'm able to do anything I want with the Board checkboxes (see screen shots). Both account have at least one default Board.

Strange. Maybe I can show you on my computer then. I just checked and my Chrome is up to date.

I have filed a bug report for the Chrome bug:

https://productforums.google.com/forum/#!topic/chrome/tN7A_6Dj4jg;context-place=forum/chrome

The folks at Google are confused about where bugs should be reported. I followed the instructions within Chrome itself for reporting the bug, which ended up on the forum linked in the previous comment. However, the "community specialist" for that forum kept insisting that it wasn't the right place for bug reports. So I ended up starting over at https://bugs.chromium.org/p/chromium/issues/detail?id=647780. I have created a repro case for them at http://home.rksystems.com/issue647780/repro so we don't have to deal with getting permission from the security folks here to get the Chrome developers access to the EBMS site. In the meantime, here's a weird workaround: if you click the boards you want, and then click the middle mouse button on the "Policies" link at the bottom of the page, your selections will magically appear. That leaves you with an extra tab or two to close when you're done, but this might be less annoying than having to switch to another browser, or to work blind in the broken Chrome page.

As you can see in the bug report thread, they're saying that it's possible the bug might be fixed some time in the next 4-6 weeks. I'm not holding my breath. :-)

I'm impressed by the Chrome devs, who have already identified the cause of the bug and have produced a patch. They're targeting the next release, which (if I'm reading their web page correctly) will be October 18. Their description of the date says "These dates are subject to change without advance notice and provided here only for rough planning purposes. New bugs, security incidents, holiday schedules, partner dependencies and process changes can all affect these dates and move it in either direction. The date only estimates the week of 1st stable push of a release – it does not imply that all end points will be updated by this week." The comparable date for the previous release was September 6, and this ticket was opened on Wednesday the 14th. So (assuming a day or so between when the problem surface and when the ticket was created) we'd be looking at the last week of next month. Keeping my fingers crossed.

Crome version 54 is out, and it fixes this bug. Please confirm.

Did this ever get tested?

Yes, this resolved the problem.