-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/net/html: parser should conform current w3c specifications #23071
Comments
Change https://golang.org/cl/83075 mentions this issue: |
Any progress on this? |
@nigeltao I've commented my opinion at the CL. |
It (updating x/net/html's HTML5 implementation to the latest algorithmic spec) is a valid issue, but it's probably a non-trivial amount of work, and I don't have much spare time right now. Sorry. |
If I can put my two cents in, I'd like to get small changes for adding template element correctly. |
I'm working to incorporate template insertion mode into this implementation. |
The typo in the issue link has been fixed, just not rolled out yet. Will investigate the former. |
Change https://golang.org/cl/94355 mentions this issue: |
Updates golang/go#23071 See https://html.spec.whatwg.org/multipage/ Change-Id: I1bde6e07ae9270ba7b320474b9bec8ec09a79f16 Reviewed-on: https://go-review.googlesource.com/94355 Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/94837 mentions this issue: |
See https://html.spec.whatwg.org/multipage/parsing.html#the-list-of-active-formatting-elements Updates golang/go#23071 Change-Id: I015c394ed34d721e9e4a4d3e797d06d750c1864e Reviewed-on: https://go-review.googlesource.com/94837 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Change https://golang.org/cl/94838 mentions this issue: |
I'm going to send the last CL for adding the "in template" insertion mode after resolving CL94838. |
When importing from chromium's test, I found another problem about the ruby elements and a bit. I'd like to fix the problems after fixing the original issue about the "in template" inserttion mode. |
See: https://html.spec.whatwg.org/multipage/parsing.html#parsing-main-intemplate Updates golang/go#23071 Change-Id: I36529b7cf5d2adf159ed5c471fba9f67890b7eb9 Reviewed-on: https://go-review.googlesource.com/94838 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/107198 mentions this issue: |
Change https://golang.org/cl/107379 mentions this issue: |
Updates golang/go#23071 Change-Id: I07aae04757e83a3a03681a2ce92e4cab194ef64a Reviewed-on: https://go-review.googlesource.com/107198 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
Updates golang/go#23071 Change-Id: I73d7302c5bde4441aa824093fdcce52e8bb51e31 Reviewed-on: https://go-review.googlesource.com/107379 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/107575 mentions this issue: |
Updates golang/go#23071 Change-Id: Ifef79e077801422eb273af3e5a541c85c63bfce4 Reviewed-on: https://go-review.googlesource.com/107575 Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/120658 mentions this issue: |
See: https://html.spec.whatwg.org/multipage/parsing.html#parsing-main-inbody Fixes golang/go#25703 Updates golang/go#23071 Change-Id: I09db4c2d07a242cb45c3e37b499c609809dd0b83 Reviewed-on: https://go-review.googlesource.com/120658 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/123776 mentions this issue: |
Change https://golang.org/cl/123920 mentions this issue: |
Updates golang/go#23071 Change-Id: I36b0ee58f61b7de25730e0fb082eeb7ef2787594 Reviewed-on: https://go-review.googlesource.com/123920 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
See more details: https://bugs.chromium.org/p/chromium/issues/detail?id=829668 Updates golang/go#23071 Change-Id: Ib9c963269f814c3f21d3784754729df57dcc8f90 Reviewed-on: https://go-review.googlesource.com/123776 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/130795 mentions this issue: |
Updates golang/go#23071 Change-Id: I02a61109b5738759a9ee3e448981778de7d0ff62 Reviewed-on: https://go-review.googlesource.com/130795 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
Change https://golang.org/cl/131178 mentions this issue: |
Updates golang/go#23071 Change-Id: I1fdf3fe8c94efdf3c4bf9c39900468381159a032 Reviewed-on: https://go-review.googlesource.com/131178 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Change https://golang.org/cl/131475 mentions this issue: |
Fixes golang/go#23071 Change-Id: I383e13bfd87e32ffb775dff54c46b66b090e5017 Reviewed-on: https://go-review.googlesource.com/131475 Run-TryBot: Kunpei Sakai <namusyaka@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Nigel Tao <nigeltao@golang.org>
What version of Go are you using (
go version
)?go version devel +25363de Fri Dec 8 16:54:20 2017 +0000 darwin/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?What did you do?
While investigating #23064, I noticed that the template element(it's metadata content) was not interpreted correctly.
I'd like to add this element.
[Additonal Notes: 2018/02/15]
We should implement the "in template" insertion mode.
https://play.golang.org/p/k_Q95lq-6T
What did you expect to see?
<html><head><meta/><template>foo</template></head><body></body></html>
What did you see instead?
<html><head><meta/></head><body><template>foo</template></body></html>
The text was updated successfully, but these errors were encountered: