Agenda

• High Priority Work
  • Private Browsing Bug Tree
  • Cross-domain content scripts
  • Panel positioning
  • SDK 1.14 Repacks
• Q2 Goals
• SDK
  • 1.14rc1 available (but not working correctly?)!
  • land content-policy?
  • Blockers?
• Roundtable
  • Aim at the long tail - Erik
    • chrome.manifest
    • devtools
    • ubiquity

Awesomeness Schedule

Bugs

Triage Followups

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Open Bugs

Attendees

• Wes
• Jeff
• Mossop
• Erik
• Will
• Alex
• Jordan
• Irakli
• Matteo
• Eddy

Minutes

High Priority Work

Private Browsing

Landed! But a problem: if you repack your add-on, and it opts into PB, and you use a panel, then your add-on will throw an exception on startup. We will need to live with this in Firefox 20.

Cross-domain content scripts

Gabor's on vacation this week.

Panel positioning

Matteo plans to fix it this week.

SDK 1.14 Repacks

We are only repacking add-ons that use private-browsing, which we expect to be on the order of tens, rather than hundreds. We will repack after SDK 1.14 ships, to give us more time to make sure it works properly.

Q2 Goals

We need to define the Q2 goals. Does anyone have anything they'd like to see more of/less of?

SDK

1.14 RC1

1.14rc1 is available. Everyone should test it.

Content Policy

Should we land content-policy in the core? Mossop: can we support the API long-term? It should be asynch, but the content policy service isn't. The feeling is that we should not worry too much about the very long term here.

Blockers?

Roundtable

Aim at the long tail - Erik

• we should do more to support people doing deep integration: test pilot, simulator, collusion
• for example, porting ubiquity
• we should have less emphasis on UX work

Jeff: we should finish this UX work in Q2. It's a message of support to add-on developers that we care about them, people want it, we can also make add-ons be more smoothly integrated into Firefox. We have had integrating the awesomebar as a goal for years. It's a big data source for add-ons.

Add-on debugger

Eddy: can we start working on a proper add-on debugger? It's scheduled for Q3, but can start sooner. Needs help from UX, and also needs the browser toolbox (global toolbox) to be ready, which is coming, but not there yet.