Another week, another update!

With help from Axel and Zibi I was able to land the ported menubar in
the larch twig:

    https://bugzilla.mozilla.org/show_bug.cgi?id=1288406#c63

While working on this bug I ran into a few issues which I'd like to
call out here. They will be important for the end-game goal of landing
the ported menubar in mozilla-central.  It would be great if over next
two weeks someone could look into them in detail.

    Bug 1292128 - TypeError: menuPopup is undefined in
browser/base/content/test/general/browser_page_style_menu.js
    https://bugzilla.mozilla.org/show_bug.cgi?id=1292128

    Bug 1291915 - Using OS() with [xul/key] breaks the key shortcut
    https://bugzilla.mozilla.org/show_bug.cgi?id=1291915

    Bug 1291695 - Missing { references } can break bindings
    https://bugzilla.mozilla.org/show_bug.cgi?id=1291695

    Bug 1288443 - Improve fallback for label attributes in XUL
    https://bugzilla.mozilla.org/show_bug.cgi?id=1288443

I'll be back on August 17th and I'll be happy to take whatever remains
from the list.  I will also focus on improving and documenting
MessageContext as part of my Sprint 5 goals:

    
https://wiki.mozilla.org/L20n/Firefox#Sprint_5:_August_16_.E2.80.94_August_21

I know Zibi plans to work on performance of L20n for XUL (using the
ported menubar) as well as L20n for chrome HTML in the coming days.
Here's are the relevant bugs for references.  Zibi, can you file bugs
for chrome HTML as well, please?

    Bug 1289530 - Evaluate the performance of Firefox's menubar in L20n
    https://bugzilla.mozilla.org/show_bug.cgi?id=1289530

    Bug 1289535 - Speed up l20n-chrome-xul
    https://bugzilla.mozilla.org/show_bug.cgi?id=1289535

Onwards!
Staś

On Thu, Jul 28, 2016 at 6:33 PM, Staś Małolepszy <[email protected]> wrote:
> An update on this:  we now have a project integration repository [1] set up 
> and  we're very close to having the complete Menu bar ported to L20n/FTL [2].
>
> Currently larch is set up with a a changeset from mozilla-central.  I would 
> like to suggest that we work in bugs and go through a proper review process 
> before we land on larch.  This will give us an opportunity to take another 
> look at code that we landed in gecko-dev/l20n before MozLondon and land it 
> selectively as needed.  What do you think?
>
> The first two candidates would then be L10nRegistry [3] and MessageContext 
> [4] which are both required to land the migrated Menu bar.
>
> Tools like git-cinnabar [5] exist to make it possible to work with hg repos 
> from git.  I tried going full-hg today and using bookmarks and MozReview [6] 
> looks very promising.  I might try doing that exclusively from now on.
>
> Thanks,
> Stas
>
>
> [1] http://hg.mozilla.org/projects/larch/
> [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1288406
> [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1280671
> [4] https://bugzilla.mozilla.org/show_bug.cgi?id=1288639
> [5] https://github.com/glandium/git-cinnabar/wiki
> [6] 
> http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview.html
> _______________________________________________
> tools-l10n mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/tools-l10n
_______________________________________________
tools-l10n mailing list
[email protected]
https://lists.mozilla.org/listinfo/tools-l10n

Reply via email to