21–30 of 99 posts
isn't this just a case of using something incorrectly and getting an undefined result? just leaves me wondering why errors like this aren't reported or at least warned about by the browser.
if this was the compiler for any language that wasn't HTML (cringes at the thought of that being a language and not just a data format) it would never ship in such a poor state...
Wow. I haven't seen a tag in years. My thought processes loading this: • Ok, that is in fact green. • I wonder if this is related to the colour name parsing weirdness that was on HN a couple of weeks ago? • Heeeey, those aren't ASCII quotes!
http://www.whatwg.org/specs/web-apps/current-work/multipage/... = ”red” = 0red0 (" is not ascii so make 0) = 00ed0 (r is not hex so make 0) = 00ed00 (pad)
Wow. I haven't seen a tag in years. My thought processes loading this: • Ok, that is in fact green. • I wonder if this is related to the colour name parsing weirdness that was on HN a couple of weeks ago? • Heeeey, those aren't ASCII quotes!
Wow. I haven't seen a tag in years. My thought processes loading this: • Ok, that is in fact green. • I wonder if this is related to the colour name parsing weirdness that was on HN a couple of weeks ago? • Heeeey, those aren't ASCII quotes!
Cute. Use normal quotes ;) HTML colour parsing for invalidly specified colours is odd to say the least.
Hard to spot. I can imagine this happening in the real world. Several blogs engines seem to like automatically converting normal quotes to curly quotes in an attempt to prettify their text rendering. I remember copy and pasting code snippets in the and having to fix this.