Re: How to debugging the testing code in mozmill test tree.

Hi, For mozmill tests, when we need to find elements in Firefox by ID, class or other attributes, we use Firebug or Dom Inspector. For the mozmill code itself, you'll need to add dump lines inside of it, where it's relevant for your code. Like dump("Element: " + element); You can get the env

Re: I am willing to getting treecell to rendering vbox/hbox inside. Where should I start?

Maybe you want to look at this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=441414 Yonggang Luo wrote: > I am already located the code in > void > nsTreeBodyFrame::PaintCell(int32_t aRowIndex, >nsTreeColumn*aColumn, >

I am willing to getting treecell to rendering vbox/hbox inside. Where should I start?

I am already located the code in void nsTreeBodyFrame::PaintCell(int32_t aRowIndex, nsTreeColumn*aColumn, const nsRect&aCellRect, nsPresContext* aPresContext,

How to debugging the testing code in mozmill test tree.

Such as using firebug or something alike. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Telemetry alerts for histograms

On 5/08/2014 17:07, rviti...@mozilla.com wrote: > The dashboard of the alerting system is available at > http://vitillo.github.io/cerberus/dashboard/. Does this filter on any cpp_guards? -- GCP ___ dev-platform mailing list dev-platform@lists.mozilla.o

If I want to getting to extend richilistbox have the high performance with tree

What I need to do, where should I to start? ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform