9c304f1e78
When the 'y' flag was shipped, the property RegExp.prototype.unicode was accidentally also shipped. However, the existence of this property should be a usable feature testing point. This patch adds the 'unicode' getter on RegExp.prototype only if the --harmony-regexp-unicode flag is turned on. R=cbruni CC=yangguo BUG=v8:4644 LOG=Y Review URL: https://codereview.chromium.org/1550713002 Cr-Commit-Position: refs/heads/master@{#33049}
25 lines
847 B
JavaScript
25 lines
847 B
JavaScript
// Copyright 2015 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Before Unicode RegExps are shipped, we shouldn't have the 'unicode'
|
|
// property on RegExp.prototype, or read it from 'flags'.
|
|
// mjsunit/es6/regexp-flags tests that the property is there when the
|
|
// flag is on.
|
|
|
|
// Flags: --harmony-regexp
|
|
|
|
'use strict';
|
|
|
|
assertFalse(RegExp.prototype.hasOwnProperty('unicode'));
|
|
|
|
// If we were going to be really strict, we could have a test like this,
|
|
// with the assertTrue replaced by assertFalse, since flags shouldn't
|
|
// Get the 'unicode' property. However, it is probably OK to omit this
|
|
// detailed fix.
|
|
var x = /a/;
|
|
var y = false;
|
|
Object.defineProperty(x, 'unicode', { get() { y = true; } });
|
|
assertEquals("", x.flags);
|
|
assertTrue(y);
|