18710 2012-08-27 18:59:32 +0000 [Templates]: Trigger parse errors when template content does not match the template context. 2015-08-28 07:39:27 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC Windows NT RESOLVED INVALID P2 normal Unsorted 15476 1 tross ian annevk hayato mike contributor oldest_to_newest 72835 0 tross 2012-08-27 18:59:32 +0000 Functionally we want templates to be declared anywhere and be able to declare anything. That said, I suspect this behavior could confuse some authors who mistakenly put content in a template that would normally be inappropriate for the context in which the template has been declared (e.g. <table><template><div>). To help authors identify these scenarios (which are likely mistakes), I suggest we consider including context-sensitive parse errors. Functionally everything would still parse the same, but we would trigger an error for unexpected content (like <table><template><div>). We would not trigger these new errors for templates declared within <head> regardless of content. 121616 1 hayato 2015-07-06 07:16:19 +0000 Changing the category: From: WebAppsWG => Components Model To: WHATWG => HTML 122824 2 annevk 2015-08-28 07:39:27 +0000 This should not have been moved without considering whether the issue was already resolved, which I think it is.