Can replicate on Windows 7 and 10, as well as Linux Mint

Correction:  Use 8194 for step 2.  So step 2 should read:
2. Type access code 8194 and click Enter.  15 tiles are displayed.

Tested on Chrome Stable #59.0.3071.115 and Canary #61.0.3149.0 on Windows 10 and unable to reproduce the issue. Please refer the screencast for reference.
 
Steps followed:
1. Launched the browser
2. Navigated to the URL https://qa.powernoodle.com/guest
3. Tried entering the access code 8194 (As mentioned in Comment #2)
 
Observation - User is redirected to the Login screen.
 
@Reporter -- Could you please try by removing the extensions and creating a new profile to verify if the issue still persists. If the issue still persists please provide test data, which would help us in triaging further. 
 
Please let us know if we have missed anything.
 
Thanks in advance.

Deleted: 739440.mp4 2.2 MB

	739440.mp4 2.2 MB View Download

Sorry about the access code not working.  It works for 16 hours per day before it has to be manually reset.  I've created an account for this bug so access will be available until the issue is resolved.

Could you use these revised steps to reproduce using the credentials provided?

1. Go to https://qa.powernoodle.com/login
2. In the Email field, type chromium@mailinator.com
3. In the Password field, type $PVx88>S
4. Click Login to Powernoodle.  15 tiles are displayed.
5. Click the first tile.  The full tile is displayed with a check mark in the top right corner.
6. Click the check-mark.  The tile closes.
7. Repeat steps 5 and 6 for the remaining tiles.  At some point, you will not be able click the check-mark; there is no response.  The tile does not "descend" from the top the full distance as tiles that could be closed.

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested on Chrome Stable #59.0.3071.115 and Canary #61.0.3150.0 on Windows 10 & 7 and unable to reproduce the issue. Please refer the screencast for reference.
 
@Reporter -- Could you please try by removing the extensions and creating a new profile to verify if the issue and let us know if the issue still persists.
 
Please let us know if we have missed anything.
 
Thanks in advance.

Deleted: 739440.mp4 3.7 MB

	739440.mp4 3.7 MB View Download

Interesting that you could not reproduce.  I removed all extensions and reset Chrome to default; the instructions on how to create a new profile don't seem to apply anymore.  I could still replicate the bug...

That said, I downloaded the beta versions of Chrome -- version 60.0.3112.50 (Official Build) beta (64-bit) for Windows 7 and Linux Mint.  I could not recreate the bug with the beta version on either platform.

So it looks like it's fixed in the beta version and I'll just wait until version 60 becomes the new stable release.  

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@Reporter -- Thank you for your observations. Could you please provide us your machine's GPU and Console logs. It may help us in triaging the issue.

Thanks in advance.

Here are the details for one machine's GPU:

Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
bus-ID: 00:02.0 chip-ID: 8086:0126
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1366x768@59.99hz
GLX Renderer: Mesa DRI Intel Sandybridge Mobile
GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes

And here is an excerpt from Chrome's log (verbose logging):

13:13:57.252 Navigated to https://app.powernoodle.com/login?email=wayneg@powernoodle.com&error_messages=user-pass

13:14:03.333 Navigated to https://app.powernoodle.com/

13:14:03.985 [Violation] Forced reflow while executing JavaScript took 59ms

13:14:04.023 pn_code.2.1.220.js:56 XHR finished loading: GET "https://app.powernoodle.com/stripekey".
send @ pn_code.2.1.220.js:56
ajax @ pn_code.2.1.220.js:56
(anonymous) @ pn_code.2.1.220.js:105

13:14:04.137 pn_code.2.1.220.js:56 XHR finished loading: GET "https://app.powernoodle.com/version".
send @ pn_code.2.1.220.js:56
ajax @ pn_code.2.1.220.js:56
(anonymous) @ pn_code.2.1.220.js:114
k @ pn_code.2.1.220.js:55
fireWith @ pn_code.2.1.220.js:55
ready @ pn_code.2.1.220.js:55
g @ pn_code.2.1.220.js:54

13:14:04.139 pn_code.2.1.220.js:56 XHR finished loading: GET "https://app.powernoodle.com/comms-address".
send @ pn_code.2.1.220.js:56
ajax @ pn_code.2.1.220.js:56
ProtocolManager.configureConnectionInformation @ pn_code.2.1.220.js:105
(anonymous) @ (index):34
k @ pn_code.2.1.220.js:55
fireWith @ pn_code.2.1.220.js:55
ready @ pn_code.2.1.220.js:55
g @ pn_code.2.1.220.js:54
13:14:04.382 pn_code.2.1.220.js:101 Established websocket connection to wss://app.powernoodle.com/?user=8214

13:14:05.329 widget_v2.208.js:9734 [Violation] Avoid using document.write().

13:14:05.571 widget_v2.208.js:9734 [Violation] Avoid using document.write().

13:14:05.610 widget_v2.208.js:6754 [Violation] 'message' handler took 465ms

13:14:05.678 inner.html:1 [Violation] 'setTimeout' handler took 52ms

13:14:06.258 inner.html:1 [Violation] 'setTimeout' handler took 51ms

13:14:07.319 inner.html:1 XHR finished loading: POST "https://m.stripe.com/4".
(anonymous) @ inner.html:1
r @ inner.html:1
M @ inner.html:1
(anonymous) @ inner.html:1
(anonymous) @ inner.html:1

13:14:09.524 pn_code.2.1.220.js:105 [Violation] 'load' handler took 1580ms

13:14:09.525 [Violation] Forced reflow while executing JavaScript took 78ms

13:14:36.091 pn_code.2.1.220.js:105 [Violation] 'load' handler took 246ms

13:14:36.175 pn_code.2.1.220.js:11 [Violation] 'setTimeout' handler took 82ms

13:14:39.639 inner.html:1 XHR finished loading: POST "https://m.stripe.com/4".
(anonymous) @ inner.html:1
r @ inner.html:1
M @ inner.html:1
(anonymous) @ inner.html:1
(anonymous) @ inner.html:1

13:14:48.915 pn_code.2.1.220.js:55 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.

13:14:48.916 pn_code.2.1.220.js:55 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.

13:14:49.645 inner.html:1 XHR finished loading: POST "https://m.stripe.com/4".
(anonymous) @ inner.html:1
r @ inner.html:1
M @ inner.html:1
(anonymous) @ inner.html:1
(anonymous) @ inner.html:1

13:14:53.594 pn_code.2.1.220.js:55 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.

13:14:53.594 pn_code.2.1.220.js:55 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.

13:14:53.659 pn_code.2.1.220.js:105 [Violation] 'load' handler took 298ms

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Could someone from Dev team look into this issue.

Thanks.

As of now removing the Needs-Bisect label.

This does not sound like a gpu issue.  This seems like a blink issue.

Per C#8 this seems to have been working fine on M-60 which will be rolled to stable in some time. Keeping this open till M-60 is rolled to stable.

@reporter: Please confirm the behavior on M-60 stable once its rolled out.

I can confirm this bug is fixed in M-60 which is now the stable default build for Chrome.

Please close this bug.

Thanks!

Thank you for providing more feedback. Adding requester "tkent@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot