Markdown processing breaks with a link

Full text I had issues with:

- lots of more work on function re-lazification. Fixing the last intermittend test failures turns out to entail about as much work as I already spent on this (bug 886193, wip)
- fix Set and Map to treat -0 and 0 as the same key (bug 952870, needs review)
- fix String#startsWith and #endsWith spec compliance issues (bug 952898, needs review)
- implement Array#fill (bug 911147, needs review)
- implemented ArrayBuffer.isView (bug 896105, needs landing)
- investigated perf issues with accessors on objects instead of prototypes in bug 782913, got efaust on the case (bug 861759)
- reviewed final version of SIMD interpreter support patch, which landed since (bug 946042)

Shumway:
- enabled installing custom functions on the ShumwayWorker's global (bug 949992, wip)
- improved FF extension's [error reporting facility](https://github.com/tschneidereit/shumway/tree/issues) (wip)
- started porting error reporting backend to Mozilla's PaaS cloud platform
- more work on splitting rendering into a front- and a backend part, enabling the backend to efficiently run on another thread
- filed bug 952539 proposing a WebGL extension to allow on-GPU copying of texture regions from a canvas2d into a WebGL texture

Other:
- engaged in Twitter discussion about users being irritated/frightened after accidentally opening the devtools console. Filed bug 953166

I suspect, however, that the github link is to blame, as markup worked after removing it. Changing [error reporting facility](https://github.com/tschneidereit/shumway/tree/issues) (wip) to error reporting facility (https://github.com/tschneidereit/shumway/tree/issues, wip) made marked-up text appear.

bsmedberg / mozilla-weekly-updates

Markdown processing breaks with a link #3