Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(273)

Issue 160093: Let theme values that previous had to be real be specified as ints.... (Closed)

Created:
11 years, 5 months ago by Glen Murphy
Modified:
9 years, 5 months ago
Reviewers:
Aaron Boodman
CC:
chromium-reviews_googlegroups.com, Erik does not do reviews, Ben Goodger (Google)
Visibility:
Public.

Description

Let theme values that previous had to be real be specified as ints. Also bonus update to background_tab_text naming. BUG=16892 TEST=Create and install a theme with integer values for ntp_section opacity or tint values. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=21519

Patch Set 1 #

Total comments: 2

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+25 lines, -13 lines) Patch
M chrome/browser/browser_theme_provider.cc View 1 3 chunks +17 lines, -8 lines 0 comments Download
M chrome/common/extensions/extension.cc View 2 chunks +8 lines, -5 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Glen Murphy
11 years, 5 months ago (2009-07-24 07:16:21 UTC) #1
Aaron Boodman
11 years, 5 months ago (2009-07-24 07:26:24 UTC) #2
lgtm with nits

http://codereview.chromium.org/160093/diff/1/2
File chrome/browser/browser_theme_provider.cc (right):

http://codereview.chromium.org/160093/diff/1/2#newcode567
Line 567: int value;
Initialize this guy.

http://codereview.chromium.org/160093/diff/1/2#newcode569
Line 569: tint_list->GetInteger(0, &value);
Also, I realize the manifest validation should have ensured there are values
here, but I think it is worth being defensive:

if (tint_list->GetInteger(...)) {
  hsl.x = ...
}

Otherwise, if GetInteger() fails, you are setting the hsl component to whatever
happened to be in value before.

Powered by Google App Engine
This is Rietveld 408576698