published the ISO 16262 in December yet we didn’t
Clayton set up the
Tom Green will be
representing the WAP folks from now on.
He works for Lotus and was invited to this meeting
The next meeting at
Microsoft on May 20th/21st. AC to send out details of where/when etc.
Agenda: List of open items and any edition 4
10:30 – 5:00 first
9:30 – 5:00 second
NSCP to host June
MM couldn’t find
information this time. We will discuss
this at the next meeting
WH didn’t have any
work for this so we will defer to the May meeting
over whether the array functions should walk up the prototype chain.
WH suggested making
the behavior undefined allowing each of the implementation to keep their
existing behavior. MC suggested coming
up with a standard mechanism for behavior.
DR & MM will go
away and discuss what the code impact would be with the complex scenarios. Deadline will be May 7th for
posting a proposal
Should it be lower
case since all other methods start in lower case? The name was changed to encodeURI and decodeURI to reflect this.
DR will write this
up and send it off to martin duerst and the group to review the content. DR will send this by May 14th.
locale object parameter was removed from the standard since the
internationalization library wouldn’t exist for ECMAScript 2. It was suggested that a non normative note
be added specifying that the optional final parameter could become significant
in the future
dependencies on the internationalization library were removed since the library
doesn’t exist yet
to meet Mike Ksar’s comments at last meeting.
The paragraph will be sent to Mike Ksar for final approval.
out the URL’s to the Unicode website
out Unicode character map since it’s already part of the Unicode standard
will check to see if “Unicode character” is used in the ECMA spec. Changes to the paragraph to clarify the
meaning of “Unicode character”
of Unicode value in the tables it was proposed to be Codepoint value.
information from the Unicode standard rather than relying on a link to the
BI-DI chars in identifiers will be difficult given the existing wording of the
standard. It was agreed that this was
an agreeable course of action given the difficulty of implementation.
agreement to use elements rather than characters in the text.
removed the argument
through the first parameter rather than all the parameters
to get rid of the locale parameter throughout the text.
over behavior. It was agreed that there
should be no locale specific behavior for toLowerCase.
to remove the locale parameter from the doc
suggested that rather having a locale parameter that toLocaleUpperCase and
toLocaleLowerCase be added. It was
agreed that this made sense and should be added to the standard
the locale parameter from number.toLocaleString
all references to System Locale to be Host Environment Locale to cope with the
hosting environments locale that is passed into the language
the changes other than the 2 new methods are moved to content agreed
by new draft
proposed that case (or ignorecase) be an argument so that it could just return
1,0 or –1
was agreed that this method should be added to the ECMAScript 2 standard. The spec will be updated for May 7th
write up a proposal including toLocaleDateString, toLocaleTimeString,
toTimeString, toDateString. Will
provide a version for May meeting
Unicode in regular
provide write up for May meeting
MM will update the exceptions
document for the May meeting
Completion codes –
deleted from the work items since nobody could remember what the work item was