Confirmed users
471
edits
| Line 40: | Line 40: | ||
** how to mark chrome-authority-needing packages (warner) | ** how to mark chrome-authority-needing packages (warner) | ||
** Page Worker API | ** Page Worker API | ||
** directory of community-created packages (atul) | |||
*** well-defined SDK search path for added packages (warner) | |||
** JS catch-alls or other tooling to enable security wrappers, maybe Simple Storage (atul) | |||
** unforgeable JID (warner) | |||
** SDK test harness HTTP server: allow package tests to use it to test XHR, etc | |||
** "the other APIs" (misses from 0.3) | |||
** content exposure module | |||
** factor out shared code between page mods, context menu, tabs. RE "the active tab" | |||
** post-release "find and merge similar code" party (atul) | |||
** code similarity analysis tools (in flighdeck?) (warner) | |||
** module usage static analysis for package size optimizations ('require' scanner / minimal linker / import-security-enforcement) | |||
** toolbar button API (phase one) | |||
** Twitter example third-party API (enable community to create non-chrome components) | |||
** docs restructuring: tutorial, philosophy, API reference | |||
** "cfx" tool reference: list of commands, options, on 'cfx docs' webpage | |||
** docs: change language: split philosophy ("it's not here yet, but here's where we want it to go") from actual-present parts ("this is how it works right now") | |||
** doc contribution process (from community) | |||
= Followups = | = Followups = | ||
* piotr needs docs MD-to-JSON tool from warner | * piotr needs docs MD-to-JSON tool from warner | ||