Confirmed users
933
edits
Firefox/Meeting/29-Sep-2015: Difference between revisions
Firefox/Meeting/29-Sep-2015 (view source)
Revision as of 14:38, 30 September 2015
, 30 September 2015fix import formatting
(Page generated from https://fx-team.etherpad.mozilla.org/desktop-meeting by Special:ImportFromEtherpad) |
m (fix import formatting) |
||
| Line 1: | Line 1: | ||
== Actions from last meeting == | == Actions from last meeting == | ||
* Invite Nick Nguyen to talk about ideas for the Spring release | * Invite Nick Nguyen to talk about ideas for the Spring release | ||
| Line 7: | Line 7: | ||
== General Topics / Roundtable == | == General Topics / Roundtable == | ||
(tips/tricks/FYI, productivity improvements, industry news)<br /> | (tips/tricks/FYI, productivity improvements, industry news)<br /> | ||
| Line 27: | Line 27: | ||
== Friends of the Firefox team == | == Friends of the Firefox team == | ||
(Give a shoutout/thanks to people for helping fix and test bugs. Introductions)<br /> | (Give a shoutout/thanks to people for helping fix and test bugs. Introductions)<br /> | ||
| Line 40: | Line 40: | ||
== Project Updates == | == Project Updates == | ||
=== add-ons === | === add-ons === | ||
* Add-ons team has joined the Firefox team | * Add-ons team has joined the Firefox team | ||
| Line 46: | Line 46: | ||
=== e10s === | === e10s === | ||
* Still on M8 - but we've cracked the 60 bug count, which we've been floating around for a month or so | * Still on M8 - but we've cracked the 60 bug count, which we've been floating around for a month or so | ||
| Line 54: | Line 54: | ||
=== Go Faster === | === Go Faster === | ||
* In progress updating of system add-ons | * In progress updating of system add-ons | ||
| Line 60: | Line 60: | ||
=== Hello === | === Hello === | ||
* Link clickers clicking their own links now open in Firefox | * Link clickers clicking their own links now open in Firefox | ||
| Line 66: | Line 66: | ||
=== Notifications === | === Notifications === | ||
* New team starting to work on (Push) Notifications | * New team starting to work on (Push) Notifications | ||
| Line 81: | Line 81: | ||
=== Privacy/Security === | === Privacy/Security === | ||
* Password manager password column has changed behaviour. Double-click to edit/view a password inline | * Password manager password column has changed behaviour. Double-click to edit/view a password inline | ||
| Line 95: | Line 95: | ||
=== Search === | === Search === | ||
* | * | ||
<br /> | <br /> | ||
=== Windows 10 === | === Windows 10 === | ||
* Edge migration stuff: | * Edge migration stuff: | ||
| Line 109: | Line 109: | ||
=== Quick Team Update === | === Quick Team Update === | ||
* Tim Taubert has moved to the platform security team. His reports will now report to Panos. | * Tim Taubert has moved to the platform security team. His reports will now report to Panos. | ||
== This week I learned… == | == This week I learned… == | ||
* [mconley] I've seen this trick used by bz and ehsan a few times - if you're debugging the native code, and you need to set a breakpoint that's normally hit very often (ex: Element::DispatchEvent), and you only want it to break after some JS that you call, set a breakpoint at js::math_sin, and call that before your special JS code. Then, when you hit that breakpoint, set up / enable your other breakpoints. Voila! | * [mconley] I've seen this trick used by bz and ehsan a few times - if you're debugging the native code, and you need to set a breakpoint that's normally hit very often (ex: Element::DispatchEvent), and you only want it to break after some JS that you call, set a breakpoint at js::math_sin, and call that before your special JS code. Then, when you hit that breakpoint, set up / enable your other breakpoints. Voila! | ||
* [kitcambridge] UNIFIED_SOURCES are concatenated together, then compiled. If one source file doesn't include a required header, but another one does, and they're merged into the same unified file, everything will build fine. If you add a new source file, it affects how they're merged, so you can get unrelated breakages. | * [kitcambridge] UNIFIED_SOURCES are concatenated together, then compiled. If one source file doesn't include a required header, but another one does, and they're merged into the same unified file, everything will build fine. If you add a new source file, it affects how they're merged, so you can get unrelated breakages. | ||