Re: [whatwg] : Issue reported by the web developers
On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters wrote: > Make the end tag optional and have , and generate > implied end tags. (Maybe other tags like and can also > imply .) The label attribute be honored if specified, otherwise > use the textContent with leading and trailing whitespace trimmed. > > This would allow either syntax unless I'm missing something. File an issue on doing this? Are Firefox and Chrome (behind a flag) implementing this feature identical otherwise? Anything they don't implement from the setup? It seems at this point we should cut our losses and remove unimplemented markup features and defer to custom elements for the foreseeable future. -- https://annevankesteren.nl/
Re: [whatwg] : Issue reported by the web developers
So, here's one example of a page putting content inside of : https://developer.apple.com/library/prerelease/ios/documentation/HealthKit/Reference/HealthKit_Constants/index.html#//apple_ref/c/econst/HKBodyTemperatureSensorLocationRectum If you use Chrome with the Experimental Web Platform Features flag turned on (so we actually parse , rather than it being parsed as an unknown element), you'll see a ton of crap overlaying the page from the s. I'm leaning pretty heavily toward this being a coincidental name collision; that is, it looks like they're intentionally unknown elements that happen to be named /; the markup has no relation whatsoever to what is specced. ~TJ