MD Extensions: Long extension errors are truncated
Reported by
anowlcal...@gmail.com,
Mar 28 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Have an extension error 2. Go to chrome://extensions 3. See that the error is truncated What is the expected behavior? The whole error should be shown. What went wrong? When the error is long, it is truncated. Did this work before? Yes Pre-MD extensions Chrome version: 65.0.3325.181 Channel: stable OS Version: Ubuntu 16.04 Flash Version: This is caused by the overflow-x and overflow-y settings on #content -- setting overflow-y to auto makes it a bit better (as seen in the second attached screenshot), although long URLs are still truncated (maybe add word-break: break-all?).
,
Mar 29 2018
anowlcalledjosh@ Thanks for the issue. Tested this issue on Windows 10 and Ubuntu 14.04 on the reported version 65.0.3325.181 and the latest Canary 67.0.3382.0 by following the below steps. 1. launched Chrome and added the extensions 'Ublock Origin' and 'Https Everywhere'. 2. Enabled 'Https Everywhere' extension and could not observe any errors on the chrome://extensions page for Ublock origin. 3. Tried visiting https pages and also couldn't observe any errors. Attached is the screen cast for reference. Request you to please check and confirm if anything is missed from our end in triaging the issue. Also request you to mention the steps followed to get an error on the extensions details or provide a sample extension where this issue can be reproduced. Thanks..
,
Mar 29 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 30 2018
Unable to reproduce the issue on reported chrome version 65.0.3325.181 using Ubuntu 14.04 with the below mentioned steps. 1. Launched Chrome 2. Added two extensions Ublock Origin and HTTPS Everywhere 3. Opened extensions.html in a new tab 4. Navigated to Chrome://extensions Though we have error in Ublock origin extension, we didn't observe any truncated text i.e., it's full length was visible(Similar to that of the attachment "extension_error.png" in comment#0 ). Attaching the screen shot of the same. @Reporter: Could you please have a look at the screen shot and let us know if we have missed anything from our end. Any further inputs from your end may help us. Thanks!
,
Mar 30 2018
The full error message should be something like: This extension failed to redirect a network request to chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/web_accessible_resources/c2c7eb5240aa19439b7ebbf38d6789e5.javascript?secret=84mx0e8zpql2 because another extension (HTTPS Everywhere) redirected it to https://www.google-analytics.com/ga.js. but only the first part of it is displayed in that screenshot. (If you enable the "developer mode" toggle in the top-right, it makes the cards bigger, and more of the error gets displayed – but still not the whole error.)
,
Mar 30 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 2 2018
Tried checking the issue on Chrome version 60.0.3072.0 using ubuntu 14.04 in the process of investigating it further. Though we have added both the extensions Ublock Origin and HTTPS Everywhere later opened the file "extensions.html" in a new tab, we didn't find any errors in chrome://extensions. Attaching the screenshot of the same. @anowlcalledjosh: Could you please have a look at the screen shot and let us know if anything missed from our end. Any further inputs from your end may be helpful. Thanks!
,
Apr 3 2018
I experimented a bit more (using an old Chromium build), and you might need to disable and re-enable the uBlock Origin extension before the error will show up again. Also it sometimes seems to help to hard-refresh the extensions.html page with the shortcut ctrl-shift-R in order to make the error show up. On that M60 build, the old chrome://extensions design does display extension errors, but it seems like the Material Design version doesn't display them (screenshots attached).
,
Apr 3 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 4 2018
anowlcalledjosh@ Thanks for the issue. Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac OS 10.12.6 on the reported version 65.0.3325.181 and the latest Canary 67.0.3387.0 as per comment #9. With enabling MD-extensions flags and adding the 'Ublock origin' and 'HTTPS everywhere' extensions to chrome and navigating to the given html page in comment #3, can observe the error on chrome://extensions page is truncated. This behaviour is observed from M-65 chrome builds. From the introduction of MD-extensions flag in M-63 build, can observe that the Extension error is shown on the wrench menu and not in chrome://extensions page. By disabling MD-extensions flag, can see the full error, but it is extending out of the warning block. Attached are the screen shots for reference. This is a Non-Regression issue. Hence marking this as Untriaged for further updates from Dev. Thanks.
,
Apr 5 2018
,
Apr 6 2018
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by susan.boorgula@chromium.org
, Mar 28 2018