Are you able to provide a site with specific details?

Can you please register an account here?
https://greenhouse.lotus.com
Once you've registered, I can add you to a community and demonstrate.  If you have access to the prior version of Chrome and the latest, you will see that there is now a problem.  We need to understand what changed with Chrome, as nothing changed with this IBM product.

Thank you for providing more feedback. Adding requester "dtapuska@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

I've now signed into an account there. How do I reproduce the issue?

1) Login to https://greenhouse.lotus.com/homepage
2) Click on Updates in Table of Contents
3) In the Share Something dialog box in the center of the screen, post a status update.
4) Once posted, hover over the status update.  You should see links for 
Like - Comment - Repost - More...
5) Click Comment
Error displays indicating "You are not authorized to make comments on this message."  See attached picture.
----------

I also added you to a community where you can see the same behavior:
Access https://greenhouse.lotus.com/communities/service/html/community/updates?communityUuid=c37c6efe-c68f-426e-996a-31fe04d592b0&filter=status

This worked fine in prior releases of Chrome, so we need to know what changed in how Chrome processes these links.

Deleted: errorMsg.png 8.5 KB

	errorMsg.png 8.5 KB View Download

Initial bisect points to:

You are probably looking for a change made after 471641 (known good), but no later than 471643 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/1e7cf3cffe06a5d7b91775ebaaa450fe299118bc..5025bccfe31b6c49a1e868d58568a89c75b3f338

Per revision bisect points to:
https://chromium.googlesource.com/chromium/src/+log/3639139a6216af6f66840f8348622d45ba06d5b9..5025bccfe31b6c49a1e868d58568a89c75b3f338

tkent@ please triage; not sure if this is just that the IBM site is using an API in a now non-standard way and that is causing the failure or it is caused by an implementation flaw.

This page appears to work correctly in FireFox (which should have the qualified name API) so I wonder if we have an implementation flaw?

Have you looked at the chrome console to see if there's any errors?  I'm seeing a 404 error with my IBM Quickr Site and wonder if you're seeing the same.

Deleted: Quickr Error.JPG 21.0 KB

	Quickr Error.JPG 21.0 KB View Download

This report is specific to IBM Connections, and I don't see the same 404 when accessing Connections.

I confirmed this is a dupe of  Issue 736430 .

The site executes getElementsByTagName('result') against an XML document like:

<feed>
 <generator>...
 ...
 <entry>
  <snx:action>...
  <snx:entryId>...
  <snx:result>true</snx:result>
 </entry>
</feed>

We stopped to return <snx:result> in such case.

I found the following UA-sniff code:

if((dojo.isWebKit||dojo.isSafari||dojo.isChrome)&&/^snx:/.test(tag)){
tag=tag.substring(4);
}
var _2d=_2c.getElementsByTagName(tag);

So Firefox works well, and Safari has the same issue.

Thanks for the analysis - I looked at  issue 736430 , and it as marked as "Won't Fix."  Can you please explain our options for remediation and why there will not be a fix?  Thank you!

#15,
This is not a bug of Google Chrome, and your option is to fix your site. Your site has the following code, and please remove the "if" block.

if((dojo.isWebKit||dojo.isSafari||dojo.isChrome)&&/^snx:/.test(tag)){
tag=tag.substring(4);
}
var _2d=_2c.getElementsByTagName(tag);

> please remove the "if" block.

If the site needs to support older Chrome and older Safari, removing "if" block won't work.  The code should be

var _2d = _2c.getElementsByTagName(tag);
if (_2d.length == 0 && /^snx:/.test(tag))
  _2d = _2c.getElementsByTagName(tag.substring(4));

or use getElementsByTagNameNS().