Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (go version)?

1.6.3 linux/amd64

1. What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/kminehart/Work/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"

Not sure questions 3, 4 and 5 are relevant.

I'd like to make a pull request but I'd also like some discussion beforehand so I don't waste anyone's time.

I think some added functionality to the x/net/html would be nice.

For example, several of the functions on the Node type require that a node not be attached before it is used, like

func (n *Node) InsertBefore(newChild, oldChild *Node)

which will panic if a node has a parent or siblings. Handling this is fairly straightforward, but there are some unexpected nuances that would be easily solved (and universally avoided) with a function like

func (n *Node) Detach()

In order to fix InsertBefore's panic, one could simply set "newChild.NextSibling", "newChild.PrevSibling", "newChild.Parent" to "nil". This would break the Linked Tree because its next and previous siblings, as well as its parent, would still point to that node. So everyone would essentially have to make their own "Detach" function anyways if they plan on moving nodes around in a tree.

So I'm proposing adding a Detach function. Your thoughts?