wbamberg

exception: Timestamp: 13-03-27 5:02:33 PM
Error: sitecheckr: An exception occurred.
TypeError: _window.InspectorUI is undefined
resource://sitecheckr-at-sebastianstoehr-dot-de/sitecheckr/lib/inspector.js 63
Traceback (most recent call last):
  File "resource://sitecheckr-at-sebastianstoehr-dot-de/addon-sdk/lib/sdk/timers.js", line 31, in notify
    callback.apply(null, args);
  File "resource://sitecheckr-at-sebastianstoehr-dot-de/addon-sdk/lib/sdk/content/worker.js", line 111, in onContentEvent/<
    self._emit.apply(self, JSON.parse(args));
  File "resource://sitecheckr-at-sebastianstoehr-dot-de/addon-sdk/lib/sdk/deprecated/events.js", line 123, in _emit

wbamberg

Hi

As you might already know, Firefox 20 makes a major change in the
way private-browsing is implemented, and this inevitably affects
add-ons that use it.

Add-ons that use private-browsing must be repacked with SDK 1.14
if they are to run on Firefox 20, and need code updates if they
are to be able to see private windows.

wbamberg

Where are we now?

Pages that are on MDN

• The landing page: this does have links to most devtools. But:
  1. some links are missing
  2. it has many links that look quite out of date: we should go through and figure out which should be removed, marked as obsolete, or just moved somewhere less prominent
  3. it is just a list of links: it should present something about what the devtools are, what they do, why you should care.
  4. it should look nicer

wbamberg

I've been looking through the developer tools documentation on MDN, and started to make a sort of quick assessment of the current status of it, and a sort of plan for what I should work on next.

It's quite rough, and more than possible that I'm missing lots of important stuff, but I'd love to get some feedback on it, and/or some answers to some of the questions.

Current status

These are a few things I noticed from looking through the current docs on MDN.

• Developer tools landing page: it looks to me like the Tools landing page is the nearest thing to a developer tools home on MDN. But it has a lot of links that seem quite old, some of which are perhaps not very useful and some which we might want to de-emphasise in favour of the newer tools. I think we should either refocus it much more closely on the newer developer tools (my preference) or create a new page focused on the newer developer tools. We should also add more context about the developer tools: what they are, what they do, and why yo

wbamberg

let { method } = require("sdk/lang/functional");
let myNumber = {
  add: method(add),
  number: 1
};
 
function add (target, x, y, z) { return target.number + x + y + z; }
 
console.log(myNumber.add(20, 10, 10));      // 10

wbamberg

var components = assertion.split(".");
var decodedPayload = atob(components[1]);
var email = JSON.parse(decodedPayload).principal.email;

wbamberg

manifest:

{
  "name": "Where am I?",
  "description": "A simple web app",
  "launch_path": "/index.html",
  "icons": {
    "128": "/style/icons/earth.png"
  },
  "permissions": {

wbamberg

var clickme = document.getElementById('clickme');
var started = false;
var profileName = "Profile 1";

clickme.onclick = function() {
  if (!started) {
    clickme.innerHTML = "Stop";
    started = true;
    console.profile(profileName);
    console.log("starting profile: " + profileName);

wbamberg

Firefox 22 shipped today, Firefox 23 entered Beta, and Firefox 24 entered Aurora.

This is the first time the SDK modules in a release of Firefox have diverged from the modules shipping in the last independent release of the SDK, which was 1.14. So we've updated the docs for this release, and also added docs for Firefoxes 23 and 24:

<a href="https://addons.mozilla.org/en-US/developers/docs/sdk/Firefox-22/">https://addons.mozilla.org/en-US/developers/docs/sdk/Firefox-22/</a>
<a href="https://addons.mozilla.org/en-US/developers/docs/sdk/Firefox-23/">https://addons.mozilla.org/en-US/developers/docs/sdk/Firefox-23/</a>
<a href="https://addons.mozilla.org/en-US/developers/docs/sdk/Firefox-24/">https://addons.mozilla.org/en-US/developers/docs/sdk/Firefox-24/</a>

Once we landed the SDK in Firefox we started work on some larger projects to deliver features we've wanted for some time. So Firefox 22 didn't include many user-visible changes to the SDK.

wbamberg

<html>

<head>

<style>
.fullwidth-table {
  width:100%;
}