Comment 16 for bug 182832

Is this actually fixed, or are there just workarounds implemented for the affected extensions? I ran into this myself when writing my own extension. Unless it's really fixed I'd like to reopen it (or write a new bug).