New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 641367 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
LBS



Sign in to add a comment

[LBS] Chrome Legacy Browser extension cuts URLs to 10 chars

Project Member Reported by djeche@google.com, Aug 26 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8530.62.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.70 Safari/537.36

Steps to reproduce the problem:
It appears as thought the legacy browser extension is cutting URLs by 10 chars. This does not seem to be the same as the other bug were URLs were being cut in half. This issue shortens all URL to 10 chars irregardless of size.

affected users: All 

LBS version: 4.6 

IE version: 11.0.9600.18426 

Chrome version: 52.0.2743.116 m 

What is the expected behavior?
The whole URL should be processed with out trimming.

What went wrong?
Issue description: Customer is reported that after updating to latest LBS version the URLs transferred to IE are being cut to maximum 10 characters. 

WebStore page: 

Did this work before? Yes previous version LBS

Chrome version: 52.0.2743.116 m  Channel: stable
OS Version: 52.0.2743.116 m
Flash Version: 

Logs can be located here: https://drive.google.com/open?id=0B9BQIK7d0CYNMGpjNjIwUWFoMm8

We are currently trying to get more information in relation to the particular URL effected.
 

Comment 1 by djeche@chromium.org, Aug 26 2016

Cc: djeche@chromium.org
Labels: Hotlist-Enterprise
Owner: pastarmovj@chromium.org

Comment 2 by djeche@chromium.org, Aug 26 2016

Cc: vnikolov@chromium.org
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 28 2016

Labels: Hotlist-Google
Labels: LBS
Status: Untriaged (was: Unconfirmed)
I checked the data and it seems this is a duplicate of the https://bugs.chromium.org/p/chromium/issues/detail?id=639400. 

Can you verify that not only the Chrome extension is at version 4.6 (which I presume you checked in chrome://extensions) but also the native component which you can check in the install Programs list in windows. Those two update independently though different channels as explained in the linked bug.

It seems like in your case the binary component has not yet updated from version 4.5 and therefore causing the issue.



Any news here?
Status: Assigned (was: Untriaged)
has owner -> assigned
Did you manage to get this one resolved? Barring any new comments I will close this entry next week.
Status: WontFix (was: Assigned)
Seems like there is no more info on this one. Closing it now.

Sign in to add a comment