Issue 2692253005: Do not show available bytes in media views.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2692253005: Do not show available bytes in media views. (Closed)

Created:
3 years, 10 months ago by Shuhei Takahashi

Modified:
3 years, 10 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/pending/branch-heads/2987

Project:
chromium

Visibility:
Public.

Do not show available bytes in media views. BUG=chromium:691110 TEST=Available bytes is not shown in media views. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2690853003 Cr-Commit-Position: refs/heads/master@{#450248} (cherry picked from commit 1824eba89c684de0b5fe91a013708caaafcf9081) Review-Url: https://codereview.chromium.org/2692253005 . Cr-Commit-Position: refs/branch-heads/2987@{#517} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} Committed: https://chromium.googlesource.com/chromium/src/+/d6f8642f7dd31ec13856376f74d57dec07e3f536

Created: 3 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+3 lines, -1 line)			Patch
	M	ui/file_manager/file_manager/foreground/js/gear_menu_controller.js	View		1 chunk	+3 lines, -1 line	0 comments	Download

Total messages: 2 (1 generated)

Shuhei Takahashi

3 years, 10 months ago (2017-02-15 05:37:26 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
d6f8642f7dd31ec13856376f74d57dec07e3f536.