Closed
Bug 951795
Opened 11 years ago
Closed 10 years ago
Use WidgetMethod's empty text attribute instead of a deck in the tracer
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 29
People
(Reporter: fitzgen, Assigned: vporof)
References
Details
Attachments
(1 file, 1 obsolete file)
30.73 KB,
patch
|
fitzgen
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•11 years ago
|
||
<accidental submit> We should use emptyText instead of having a deck and a custom <description> element for when the tracer doesn't have any logs. Question: Should we differentiate between not-tracing and tracing-but-no-logs-yet? Right now we do, but with emptyText, I'm not sure we would without going out of our way to do so.
Summary: Use WidgetMethod → Use WidgetMethod's empty text attribute instead of a deck in the tracer
Assignee | ||
Comment 2•11 years ago
|
||
(In reply to Nick Fitzgerald [:fitzgen] from comment #1) I think this should work fine by changing the emptyText value when clearing the logs, and when stopping tracing.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → vporof
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•11 years ago
|
||
Works. Needs a test.
Assignee | ||
Comment 5•10 years ago
|
||
Added test.
Attachment #8349984 -
Attachment is obsolete: true
Attachment #8355791 -
Flags: review?(nfitzgerald)
Reporter | ||
Comment 6•10 years ago
|
||
Comment on attachment 8355791 [details] [diff] [review] v2 Review of attachment 8355791 [details] [diff] [review]: ----------------------------------------------------------------- LGTM ::: browser/devtools/debugger/test/browser_dbg_tracing-05.js @@ +23,5 @@ > + waitForSourceShown(gPanel, "code_tracing-01.js") > + .then(testTracingNotStartedText) > + .then(() => gTracer._onStartTracing()) > + .then(testFunctionCallsUnavailableText) > + .then(clickButton) Task.jsm if you want. ::: browser/themes/osx/devtools/widgets.css @@ +297,5 @@ > +} > + > +.theme-light .fast-list-widget-empty-text { > + padding: 4px 8px; > + color: GrayText; I thought we weren't supposed to be using |GrayText| in theme CSS? Why did you change the colors at all? They were theme colors before.
Attachment #8355791 -
Flags: review?(nfitzgerald) → review+
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Nick Fitzgerald [:fitzgen] from comment #6) > > I thought we weren't supposed to be using |GrayText| in theme CSS? > Why did you change the colors at all? They were theme colors before. Normalization. I'm taking better care of that in bug 943883.
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/19a7e3bd47c3
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 29
Comment 9•10 years ago
|
||
I see transform:translateZ(0), but on other places it is: transform:translateZ(1px). 1. Will 0 also work? 2. Will 1px have possibly other unwanted effects?
Assignee | ||
Comment 10•10 years ago
|
||
(In reply to Alfred Kayser from comment #9) > I see transform:translateZ(0), but on other places it is: > transform:translateZ(1px). > 1. Will 0 also work? > 2. Will 1px have possibly other unwanted effects? Both work, and should have no side-effects (apart from hw accel) as far as I know.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•