Ignore:
Timestamp:
Dec 1, 2015, 1:06:25 AM (10 years ago)
Author:
[email protected]
Message:

[Streams API] streams should not directly use Number and related methods
https://bugs.webkit.org/show_bug.cgi?id=151499

Reviewed by Darin Adler.

Source/JavaScriptCore:

  • runtime/CommonIdentifiers.h: Adding isNaN as private symbol.
  • runtime/JSGlobalObject.cpp:

(JSC::JSGlobalObject::init): Adding @isNaN function.

Source/WebCore:

Covered by updated test.

Using @Number, @isFinite and @isNaN in place of Number, Number.isFinite and Number.isNaN.

  • Modules/streams/ReadableStreamInternals.js:

(enqueueInReadableStream):

  • Modules/streams/StreamInternals.js:

(validateAndNormalizeQueuingStrategy):
(enqueueValueWithSize):

LayoutTests:

Added a non-regression test.

  • streams/streams-promises-expected.txt:
  • streams/streams-promises.html:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/ChangeLog

    r192873 r192874  
     12015-12-01  Youenn Fablet  <[email protected]>
     2
     3        [Streams API] streams should not directly use Number and related methods
     4        https://bugs.webkit.org/show_bug.cgi?id=151499
     5
     6        Reviewed by Darin Adler.
     7
     8        * runtime/CommonIdentifiers.h: Adding isNaN as private symbol.
     9        * runtime/JSGlobalObject.cpp:
     10        (JSC::JSGlobalObject::init): Adding @isNaN function.
     11
    1122015-12-01  Csaba Osztrogonác  <[email protected]>
    213
Note: See TracChangeset for help on using the changeset viewer.