String.prototype.split with undefined separator and limit 0
waldron.rick at gmail.com
Fri Jul 27 10:00:33 PDT 2012
On Fri, Jul 27, 2012 at 9:01 AM, Steven Levithan <steves_list at hotmail.com>wrote:
> This paragraph remains verbatim in the latest ES 6 draft (Rev 9).
> This is ambiguous about whether the limit argument applies when
> separator is undefined. The algorithm steps that follow, by my reading,
> specify that limit should not affect the result if separator is undefined.
> In other words, 'undefined'.split(undefined, 0) should return
> ['undefined'], not . Was this special case for the limit argument
> intentional? Every browser I’ve tested, with the exception of Chrome, gets
> something wrong about the handling of undefined as the separator. Test
> results follow:
Would you mind filing a spec bug for this?
> -- Steven Levithan
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss