Apparently all YouTube comments have a UTF-8 BOM... at the end. YouTube, don't drink and webdev. @FakeUnicodepic.twitter.com/QSnzPdNhti
-
It’s not a BOM - it’s a ZWNBSP. It’s a valid character and only a BOM if it’s at the beginning. As the actual bytes. It certainly is never a BOM if & encoded or encoded in any other form than the bytes defined as BOM.
U+FEFF is deprecated in favor of U+2060 when not a BOM. It is not &-encoded; that's Chrome being useful and making it explicit in the dev tools. The character comes back as a UTF-8 BOM (EF BB BF) in the JSON request for the comments. It's a BOM, in a stupid place.pic.twitter.com/jj0YXmRu4k
-
-
U+2060 is only the new preferred word joiner, U+FEFF is still ZWNBSP: http://ftp.unicode.org/Public/UNIDATA/UnicodeData.txt … It’s only BOM if it’s the UTF-8/16/32 bytes at start. But since the actual bytes are in here rather than & encoded, I now agree it’s most likely a template with a BOM being concatenated.
-
Of course if it were a BOM used the way BOMs are intended to be used it would have to be at the beginning of the file. There's no reason to have a legacy ZWNBSP here, so the point is it's most likely a BOM that snuck into a stupid place due to bad code.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.