Panel doc linked to a bug, but since the doc system automatically linkifies text of the form "bug 123456", the link text ended up malformed in the browser. It's a trivial fix, so I'm making it. a=myk (from bug 569708 comment 4)
authorDrew Willcoxon <adw@mozilla.com>
Wed, 18 Aug 2010 23:42:27 -0700
changeset 739 c0bbaab6c23675bc73fc9926eb9180e498184572
parent 738 bd8facc11775679ad0b18d3761ecbb318686388b
child 740 5aa64c4190d87a03593d8519ec37f04f4cac1b04
push id270
push userdwillcoxon@mozilla.com
push dateThu, 19 Aug 2010 06:43:56 +0000
reviewersmyk
bugs123456, 569708
Panel doc linked to a bug, but since the doc system automatically linkifies text of the form "bug 123456", the link text ended up malformed in the browser. It's a trivial fix, so I'm making it. a=myk (from bug 569708 comment 4)
packages/jetpack-core/docs/panel.md
--- a/packages/jetpack-core/docs/panel.md
+++ b/packages/jetpack-core/docs/panel.md
@@ -22,17 +22,17 @@ and the content remains loaded when a pa
 to keep a panel around in the background, updating its content as appropriate
 in preparation for the next time it is shown.
 
 Panels can be anchored to a particular element in a DOM window, including both
 chrome elements, i.e. parts of the host application interface, and content
 elements, i.e. parts of a web page in an application tab.  Panels that are
 anchored to an element should have an arrow that points from the panel to the
 element, but that has not yet been implemented.  The work to implement it is
-tracked in [bug 554937](https://bugzilla.mozilla.org/show_bug.cgi?id=554937).
+tracked in bug 554937.
 
 Panels have associated content scripts, which are JavaScript scripts that have
 access to the content loaded into the panels.  Programs can specify one or more
 content scripts to load for a panel, and the program can communicate with those
 scripts via an asynchronous message passing API.
 
 Examples
 --------