New issue
Advanced search Search tips

Issue 791195 link

Starred by 1 user
Status: Fixed
Owner:
dpa...@chromium.org
Closed: Dec 2017
Cc:
reillyg@chromium.org
steve...@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Settings: Runtime error about not finding certificate_shared_css.html.

Project Member Reported by dpa...@chromium.org, Dec 2 2017 
Repro steps, see screencast too.

1) go to chrome://settings/certificates
2) See errors and warnings in the console about missing a style file.
3) Expand the some certificates, styling is broken.

Not sure if this regression made it to M64, but if it did, I think a fix should be merged.
css_file_missing.mp4
303 KB View Download

Comment 1 by dpa...@chromium.org, Dec 2 2017 

Also I am  reproducing this with "optimize_webui = false" in GN flags. This might not be reproducible with optimize_webui = true, in which case, it would not affect Stable users.

Comment 2 by dpa...@chromium.org, Dec 2 2017

Cc: reillyg@chromium.org
Owner: dpa...@chromium.org
Status: Started (was: Available)
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 4 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6fb985fcca5d982de74bd9faad387956562613cd

commit 6fb985fcca5d982de74bd9faad387956562613cd
Author: dpapad <dpapad@chromium.org>
Date: Mon Dec 04 18:50:36 2017

WebUI: Add missing compress="gzip" attribute in certificate_shared_css.html.

Bug:  791195 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I129cfb90b0e0feb7fda89a431063fdd92de054d3
Reviewed-on: https://chromium-review.googlesource.com/804679
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521397}
[modify] https://crrev.com/6fb985fcca5d982de74bd9faad387956562613cd/ui/webui/resources/cr_components/cr_components_resources.grdp

Comment 5 by dpa...@chromium.org, Dec 4 2017

Status: Fixed (was: Started)

Comment 6 by dbeam@chromium.org, Dec 12 2017 

have i mentioned that bug 738243 would fix this :)?
►

Sign in to add a comment