- From: Aryeh Gregor <Simetrical+w3c@gmail.com>
- Date: Fri, 25 Mar 2011 13:15:16 -0400
On Thu, Mar 24, 2011 at 12:31 AM, Ehsan Akhgari <ehsan at mozilla.com> wrote: > This is what Gecko does in Firefox 4. ?Webkit, however, implements the > "non-space-eating" approach on all platforms. ?I think this is an advantage, > because it means that the consumers of the API can rely on the behavior of > the API without having to resort to User-Agent sniffing. ?So, I modified the > behavior of Gecko today[1] to match that of Webkit (i.e., not eating spaces > between words). > > I wanted to see what others think about this issue. ?Feedback is most > welcome. What are the use-cases for this API if it doesn't match platform conventions? Actually, for that matter, what are the use-cases altogether? I've seen some author interest, but I'm not clear on what it's used for. It's hard to say what the expected behavior should be without use-cases.
Received on Friday, 25 March 2011 10:15:16 UTC