[Firefox Desktop] Issues found: January 9th to January 13th

Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *January 09 - January 13* (week 2). Additional details on the team's priorities last week, as well as the plans for the current week are available at:

Re: Deprecating XUL in new UI

Hi Dave, I am glad that we are having this conversation. To be honest, two of features spinning in Taipei are already partly implemented in HTML, out of the expectations that, dealing with familiar tech means faster development and less regressions. They are - Desktop video control UI within

Deprecating XUL in new UI

One of the things I've been investigating since moving back to the desktop team is how we can remove XUL from the application as much as possible. The benefits for doing this are varied, some obvious examples: * XUL is a proprietary standard and we barely maintain it. * Shallower learning curve

Re: Deprecating XUL in new UI

On Tue, Jan 17, 2017 at 11:41 AM, Sebastian Zartner < sebastianzart...@gmail.com> wrote: > https://bugzilla.mozilla.org/show_bug.cgi?id=740910 My comments in that bug still apply. Ellipsizing in the centre when the line contains more than just a single text node is really hard. Rob -- lbir

Re: Deprecating XUL in new UI

On 1/16/2017 2:43 PM, Dave Townsend wrote: One of the things I've been investigating since moving back to the desktop team is how we can remove XUL from the application as much as possible. The benefits for doing this are varied, some obvious examples: * XUL is a proprietary standard and we

Re: Deprecating XUL in new UI

On 1/16/17 9:43 PM, Dave Townsend wrote: > One of the things I've been investigating since moving back to the > desktop team is how we can remove XUL from the application as much as > possible. The necessary first step of reducing XUL use is to stop > adding any more UI that uses XUL and here I'm

Re: Deprecating XUL in new UI

Hello Dave, while contributing to some of the devtools.html refactoring projects, I noticed the following further issues: - the XUL label element has attribute crop=start|center|end, which can be used to truncate the label text and insert an ellipsis character at the place of your choice. HTML

Re: Deprecating XUL in new UI

On Mon, Jan 16, 2017 at 1:33 PM, Mike Connor wrote: > I think the rule is fine, subject to the reality that the scope of totally > new doc-level UX is fairly limited. I think you'll want to be a little > more aggressive up front if you want to shift the overall codebase in

Re: Deprecating XUL in new UI

Trees! I knew I was forgetting something, thank you. Yeah those are things we're going to need some sane replacements for. AS far as XBL goes, while I suspect it works from HTML documents I think we want to be phasing out use of XBL too for pretty much the same reasons as XUL. Web components seem

Re: Deprecating XUL in new UI

Thanks for your feedback Jaroslav, it's really helpful. The issue around mixing XUL and HTML is one in particular where I think we may end up having to make some platform fixes to at least make the transition away from XUL possible. On Mon, Jan 16, 2017 at 1:31 PM, Jaroslav Šnajdr

GPU Process Experiment Results

Hello Platform folks, Over the Christmas break I rolled out a Telemetry Experiment on Nightly to measure the stability impact of the GPU Process. This experiment concluded on January 11. Having had time to analyze the data I've published a report on my blog: https://ashughes.com/?p=374 It should

Re: Deprecating XUL in new UI

On 01/16/2017 10:43 PM, Dave Townsend wrote: One of the things I've been investigating since moving back to the desktop team is how we can remove XUL from the application as much as possible. The benefits for doing this are varied, some obvious examples: * XUL is a proprietary standard and we

Re: GPU Process Experiment Results

My one-sentence summary of the article - If anything, the test cohort with the GPU process saw improved stability, especially for graphics crashes. Which is awesome! May need error bars for the figures to see how much of the results you saw we might have to attribute to the noise of reported

Re: Deprecating XUL in new UI

Trees are the big thing that come to mind. I've heard about three non-XUL re-implementations (IIRC mostly in devtools) which sounds like a maintainability issue and potentially redundancy. I would rather keep using XUL trees than have even more different tree implementations (though I'd be fine

Re: GPU Process Experiment Results

Thanks for the feedback Chris. Graphs measuring crash rates is "crashes per 1000 hours" for Telemetry data via the crash_aggregates table (links to my re:dash queries are link at the bottom of the post) and "crashes per install_time cardinality" for Socorro data. I tried to focus on crash rate

Re: Deprecating XUL in new UI

I think the rule is fine, subject to the reality that the scope of totally new doc-level UX is fairly limited. I think you'll want to be a little more aggressive up front if you want to shift the overall codebase in finite time. To that end, I'd propose an additional requirement that any major