Re: [FileAPI] Updates to FileAPI Editor's Draft

Sorry if these have all been discussed before. I just read the File API for
the first time and 2 random questions popped in my head.

1) If I'm using readAsText with a particular encoding and the data in the
file is not actually in that encoding such that code points in the file can
not be mapped to valid code points what happens? Is that implementation
specific or is it specified? I can imagine at least 3 different behaviors.

2) If I'm reading using readAsText a multibyte encoding (utf-8, shift-jis,
etc..) is it implementation dependent whether or not it can return partial
characters when returning partial results during reading? In other words,
 Let's say the next character in a file is a 3 byte code point but the
reader has only read 2 of those 3 bytes so far. Is implementation dependent
whether result includes those 2 bytes before reading the 3rd byte or not?