Changes to FAQ

[Garrett Smith]

Changes to FAQ:

* 4.1 How do I format a date with javascript?
formatDate now throws RangeError where it used to throw Error.
(kangax)

* 7.1 How do I trim whitespace?
Add link to:
http://thinkweb2.com/projects/prototype/whitespace-deviations/
(kangax)

* How do I close a window and why does it not work on the first one?
Clarification to windowRef.closed property, change XML for newsgroup posts.
(Lahn)

* How do I access a frame's content?
(was: How do I communicate between frames?)
(-TNO-, Honnen, Stockton)

* 3.2 What online resources are available?
Browser Documentation
BlackBerry JavaScript Reference
http://docs.blackberry.com/en/devel...e=21&category=BlackBerry+Browser&subCategory=

(Smith)

* 9 Windows and Frames
(smith)
| The window object (also referred to by self) is "DOM Level 0".
| No formal standard for it exists.
(that initially existed in the draft to "How do I access a frame's
content," but is appropriate for the entire section.

Garrett

 

[Thomas 'PointedEars' Lahn]

Changes to FAQ:
[...]
* 3.2 What online resources are available?
Browser Documentation
BlackBerry JavaScript Reference
http://docs.blackberry.com/en/devel...e=21&category=BlackBerry+Browser&subCategory=

(Smith)

JFTR: I have provided the reference URL as
<http://na.blackberry.com/eng/deliverables/8861/Overview_790346_11.jsp> in
<
Anyhow, thanks for the update.


PointedEars

 

[Garrett Smith]

Changes to FAQ:
[...]
* 3.2 What online resources are available?
Browser Documentation
BlackBerry JavaScript Reference
http://docs.blackberry.com/en/devel...e=21&category=BlackBerry+Browser&subCategory=

(Smith)

JFTR: I have provided the reference URL as
<http://na.blackberry.com/eng/deliverables/8861/Overview_790346_11.jsp> in
<

Oh, I see that, I remember reading parts of that thread about __proto__
being restorable in Blackberry but didn't click the link at the time.

I recently found the link during an attempt at getting the Blackberry
simulator going, where kangax emailed me the link for the simulator. I'
don't like disclosing personal details but I can't see why he would
object to it here:-

| I have one on Windows. You can download them here -
| http://na.blackberry.com/eng/developers/resources/simulators.jsp
| but you have to register first, fill in a couple of annoying forms,
| also get some additional MDS service simulator (which needs to be run
| in order to emulate network access for simulators). In other words,
| it's pain in the ass, but can be done.

Pain in the ass it is.

That link ought to be added to the FAQ, but I feel odd about advocating
it while not being able get the damned thing running myself. Seems the
MDS doesn't like my classpath settings. Will try and fix it.

Garrett

 

[-TNO-]

Changes to FAQ: ...
  * 7.1 How do I trim whitespace?
Add link to:http://thinkweb2.com/projects/prototype/whitespace-deviations/
(kangax)

I think it should be mentioned that JavaScript 1.8.1 now supports the
string prototype methods ".trim()", ".trimLeft()", and ".trimRight()".
reference:
https://developer.mozilla.org/en/New_in_JavaScript_1.8.1

Also that the ES5 specification will support the ".trim()" method
reference:
The ES5 Approval Draft standard (1 September 2009) section
15.5.4.20
http://wiki.ecmascript.org/doku.php?id=es3.1:es3.1_proposal_working_draft

 

[Thomas 'PointedEars' Lahn]

I think it should be mentioned that JavaScript 1.8.1 now supports the
string prototype methods ".trim()", ".trimLeft()", and ".trimRight()".

Yes, and it would be good if tests would be made first as to which
characters are considered whitespace by this implementation.

reference:
https://developer.mozilla.org/en/New_in_JavaScript_1.8.1

Also that the ES5 specification will support the ".trim()" method
reference:

s/will/might/


PointedEars

 

[-TNO-]

s/will/might/

I chose the word "will" knowingly, and based the following comment:

https://mail.mozilla.org/pipermail/es5-discuss/2009-August/002969.html

 

[Thomas 'PointedEars' Lahn]

I chose the word "will" knowingly, and based the following comment:

https://mail.mozilla.org/pipermail/es5-discuss/2009-August/002969.html

If you read that announcement more carefully, you might observe that while
the draft is "technically complete", not only there is not yet a
Specification, and any more than one serious item "could jeopardize the 2009
release", approval by several panels if there is a Specification to be
submitted, is still pending. So using `will' is certainly not justified.

Much less justified is referring to ECMAScript Edition 5 as something that
would be usable as a whole; when and if it is approved and published by Ecma
International, it would still not be fully implemented. There is also no
indication yet that it would be cross-browser compatible (by contrast to
Mozilla.org, Microsoft has not indicated in recent JScript releases that
they are interested in implementing features suggested by this draft in
JScript). So I strongly suggest to use more caution here.


PointedEars

 

[-TNO-]

If you read that announcement more carefully, you might observe that while
the draft is "technically complete", not only there is not yet a
Specification, and any more than one serious item "could jeopardize the 2009
release", approval by several panels if there is a Specification to be
submitted, is still pending.  So using `will' is certainly not justified.
...
So I strongly suggest to use more caution here.

I have no issue with waiting until the final specification is stamped.
I have no desire to argue the semantics of the word "will" in regards
to probability and statements.

Much less justified is referring to ECMAScript Edition 5 as something that
would be usable as a whole;

Where do you think I did such a thing?

...
when and if it is approved and published by Ecma
International, it would still not be fully implemented.  There is also no
indication yet that it would be cross-browser compatible

Something similar can be stated for existing implementations of ES3,
so I don't see the point of the argument and how it applies to my
statement that the shortly upcoming specification currently lists this
method.

(by contrast to Mozilla.org, Microsoft has not indicated in recent JScript releases that
they are interested in implementing features suggested by this draft in
JScript).  

I think they have, plus in other ways:

http://es5conform.codeplex.com/
Allen-Wirfs statements on the es-discuss lists.
http://blogs.msdn.com/jscript/archi...-compatible-ecmascript-5-implementations.aspx
http://blogs.msdn.com/jscript/archi...script-fifth-edition-draft-specification.aspx

 

[Dr J R Stockton]

In comp.lang.javascript message <5fff185b-9f07-449f-8335-ac40af4461e4@f3
3g2000vbm.googlegroups.com>, Sun, 13 Sep 2009 11:29:41, -TNO-

I think it should be mentioned that JavaScript 1.8.1 now supports the
string prototype methods ".trim()", ".trimLeft()", and ".trimRight()".
reference:
https://developer.mozilla.org/en/New_in_JavaScript_1.8.1

Also that the ES5 specification will support the ".trim()" method
reference:
The ES5 Approval Draft standard (1 September 2009) section
15.5.4.20
http://wiki.ecmascript.org/doku.php?id=es3.1:es3.1_proposal_working_draft

However, there should also be a strong warning against relying on those
and other new features on the open Web until it has been shown that
almost all browsers in use implement them correctly.



Judging from the FD, there's not much added to Version 5 that will help
average semi-intelligent programmers.

For an example of the work of the latter class, view source of
http://saturn.jpl.nasa.gov/index.cfm, and watch its countdown clock when
getFullYear() != getUTCFullYear() . It also includes the first usages
I've seen of the use of M/DD/YYY for a current date (lines 59/60).

At least it does not set all font sizes in px : it does have a
"font-size: 1px;" but that applies to no characters.