Comment 1:

Issue #2229 has been merged into this issue.

Comment 2:

Issue #1889 has been merged into this issue.

Comment 3:

Issue #1751 has been merged into this issue.

Comment 4:

Issue #1661 has been merged into this issue.

Comment 5:

Labels changed: added priority-later, removed priority-medium.

Comment 6:

Labels changed: added priority-go1.

Comment 7:

Owner changed to builder@golang.org.

Comment 8:

It's time to stop working on new code.  Is package html done?
If so, great.  If not, let's move to exp/html and maybe it can be
in Go 1.1.  Thanks.

Owner changed to @nigeltao.

Comment 9 by nigel.tao.gnome:

It's not done, in that it's not fully conformant with HTML5. But I don't expect any API
changes between now and getting 100% of the test cases passing. It already handles
trickiness like <svg> and <math>. But there might be some dark corner of
HTML5 which isn't explored yet.
I guess that that means that package html should move to exp/html.
Is html/template unaffected? It currently depends on exp/html for a small utility
function (html.UnescapeString), but that's copy/pastable.

Comment 10:

Do you want people using html in production
and complaining when it fails?  If not, then
it should be in exp/html.
Yes, please copy/paste the utility function.

Comment 11:

I've got second thoughts on copy/paste. There's non-trivial code [0] and a large look-up
table [1].
[0] http://golang.org/src/pkg/html/escape.go?h=func+unescapeEntity#L57
[1] http://golang.org/src/pkg/html/entity.go?h=var+entity#L16
How about keeping html.EscapeString and htmlUnescapeString, but moving all the
tokenization and parsing code to exp/html?
The other option is moving html/template to exp/html/template.

Comment 12:

html/template needs to stay; it is done and very useful.
It seems fine to leave behind an html package with just EscapeString.
Russ

Comment 13:

This issue was closed by revision 324513b.

Status changed to Fixed.