diff options
author | Guillaume Crico <gcrico@fede.org> | 2014-11-17 13:31:29 +0100 |
---|---|---|
committer | Guillaume Crico <gcrico@fede.org> | 2014-11-17 13:31:29 +0100 |
commit | ab76ca32ad353c3196357b02069e93267928751e (patch) | |
tree | 6fd01cfd9c4ed19689f06e0802596cace6cdea11 /data | |
parent | c507d164f5856779d23ef030c2a656391707a5ac (diff) |
Fix Issue 202 - Catch RangeError thrown by native String.fromCodePoint (js implementation)
When using a JS engine that provides a native String.fromCodePoint ES6 implementation (e.g. SpiderMonkey), a RangeError is thrown if the codepoint is invalid.
When adding the from-code-point.js polyfill, the js implementation was modified in order to handle invalid code point by returning the 0xFFFD placeholder glyph. So this is not a real "polyfill", but an specific implementation (adapted to the parser needs).
So, if a native String.fromCodePoint implementation is availbale, the fromCodePoint function should catch the RangeError and return the 0xFFFD placeholder glyph.
Diffstat (limited to 'data')
0 files changed, 0 insertions, 0 deletions