he same engine.
[1] https://developer.mozilla.org/en/Core_JavaScript_1.5_Reference
[2] https://developer.mozilla.org/en/Core_JavaScript_1.5_Guide
--
David "liorean" Andersson
***
List Guidelines: http://webstandardsgroup.org/ma
> liorean wrote:
>> (Netscape had originally intended to use the name LiveScript.)
2008/10/28 Hassan Schroeder <[EMAIL PROTECTED]>:
> Actually, it was initially released as LiveScript and renamed later.
IIRC Navigator 2.0 also supported a mocha: pseudo-protocol like the
2008/10/28 liorean <[EMAIL PROTECTED]>:
> Yes, it's a registred trademark of Sun,
Actually a Trademark, not a Registred Trademark, apparently.
--
David "liorean" Andersson
***
List Guidelines: http://we
most of
the Netscape/Mozilla JavaScript additions to ECMAScript.
The name JavaScript is very seldom used by Microsoft. If you read
Microsoft employee blogs and official statements, you almost never
encounter that term. They prefer to either use their own JScript name
or the ECMAScript name.
--
David
hem on top of the language, but you don't get
support for it for ordinary language elements or for built in
operators.
You're still not getting around that there's no built in support for
classical inheritance, other than the pseudo-classes that are used in
the ECM
rought up
the fact it has prototypal inheritance and this is one of the
mechanisms that makes it object oriented several times.
--
David "liorean" Andersson
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
it is
> prototype-based, you really should edit them as it must be a
> miss-representation of javascript.
We're not arguing against the articles. We've been arguing constantly
throughout this thread that JavaScript may be prototype-based, but
that does not make it any less obje
2008/10/27 liorean <[EMAIL PROTECTED]>:
> The first implementation of JavaScript is still alive in the form of
> Mozilla SpiredMonkey
Or SpiderMonkey, as it is properly called :)
--
David "liorean" Andersson
*
ance to an object
based system.
Anthony Ziebell is arguing that it's not object oriented based on the
false premise that classical inheritance is the way to achieve object
orientation and prototypal inheritance is not, despite himself linking
articles stating the cont
s a really good place to find tutorials or articles about
separate areas of JavaScript:
http://www.d.umn.edu/itss/support/Training/Online/webdesign/javascript.html>
--
David "liorean" Andersson
***
List Guidelines: http:
languages that
are more object oriented. But they use classical inheritance, and
because JavaScript does not some people have got into their heads that
Classical inheritance == OOP which means JavaScritp != OOP. But that's
a
> 2008/10/24 Anthony Ziebell <[EMAIL PROTECTED]>:
> Forgot to clarify one thing: ECMAScript is fully OO in my opinion, however
> JavaScript is not a full implementation of ECMAScript, unfortunately.
> liorean wrote:
> JavaScript is a superset of ECMAScript. If ECMAScript is o
wer/useful plant is all in the perspective of the beholder.
--
David "liorean" Andersson
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
ce and a deep type
hierarchy system. Some have a separate interface scheme that is about
object and function signatures connected with the type system but that
does not allow code inheritance.
Some have only this and no implementation inheritance mechanism.
--
David "liorean" And
variable size and not dense integer keyed arrays of fixed size. In
fact, true arrays are only available in JavaScript in the form of
strings, and those are read only.
--
David "liorean" Andersson
***
List Guidelin
ed language.
It has imperative and functional properties, it has a
statement-expression curlies-and-semicolons, it has object orientation
and higher order programming features, it has reified closures and
lexical scope with a few dynamic scope features etc. It's a hybrid
lang
cks, let expressions etc.
1b. Implementing standard library only fearures. (.hashcode property
on all values is an example I'd like to see here)
2. Implementing the features of ES4 in order of what is perceived to
give most benefit to web developers with some kind of opt-in flag รก la
&qu
y is it better to let developers send code specifically for
fixing a bug, which creates a dependency of that code on the bug in
question, than fixing the bug? If such dependencies are created, they
make it harder to actually fix bugs.
--
David "liorean" Andersson
***
butes are deprecated in HTML4.01 but
really ought not be since they convey semantics that are inherent to
the document structure and aren't purely presentational. It's likely
they will be un-deprecated in HTML5.
--
David
g this? I'm pretty sure you're wrong about
getElementById having to traverse the full DOM.
--
David "liorean" Andersson
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/selectors-api/Overview.html?content-type=text/html;%20charset=utf-8>
--
David "liorean" Andersson
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
ish)?
Elements that behave like block level elements, I'd say.
--
David "liorean" Andersson
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
The code size server side has entirely
different impact because of that.
Coming to JS from a back-end developer perspective I find this very strange.
The perspective difference is quite a lot of the reason, I feel.
Different consideration
On 29/05/07, Alastair Campbell <[EMAIL PROTECTED]> wrote:
On 5/29/07, liorean <[EMAIL PROTECTED]> wrote:
> > It seems strange that the closing slash is
> > taken as the close, rather than the greater than sign, is that in the
> > HTML spec somewhere?
> Yes, in th
ments:
http://liorean.net/samplelayout.html>
http://liorean.net/sgml-goodness.html>
http://liorean.net/xhtmllayout.xhtml>
All of them are valid documents and except for DOCTYPE, XML prologue
and XHTML namespace the document they describe is identical.
--
David "liorean"
ave zero false positives.
I've also been doing some work on trying to present syntax-semantics
in a way that lends itself to a SUCCESS/FAILURE/CRASH/PEG result on
each feature, but that's trickier...
If anyone is interested in helping me writing test cases for that
testsuite, just sen
optional for form control
input elements (i.e. all type attribute values other than reset and
submit, including the value button, entirely independent of whether
the form control may be successful or not).
--
David "liorean" Andersson
value of
submit or reset). The name attribute is required on form controls but
not on form functionality. The DTD format doesn't allow this type of
granularity however.
In other words, just because something is valid according to the HTML
DTD doesn't mean it's valid according to t
e sure it is either
whitelisted or otherwise excluded from the autoresponder. See
http://web-graphics.com/mtarchive/001730.php>
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
The discussion list for http://webst
nce there might be a release of ie7b2 to
follow. Hopefully Microsoft will realise the risk of confusion and
make the next release ie7b3, but I wouldn't count on that.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
s two top posts which quote
your entire message without any trimming...
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/gui
efinition of how to handle that if no presentational or
behavioral hints exists explicitly in the document, because the
defaults on not-strictly-semantical aspects are also part of the
semantic sets (In my view, at least. Which isn't neccesarily canon...)
Counter arguments a
ia. Default in Windows is 96
(Windows even calls it DPI), or 120 for large size.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup
On 11/01/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote:
> liorean wrote:
> > Character references refer to Unicode code points independent of the
> > document encoding and character set. At least for HTML4 and XML, if
> > not for HTML3.2.
>
> As far as character refer
responding
character references.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
ields instead of coming
through the main page? The main page is just a part of the
application, not the whole thing.
These considerations probably make CSS layout an even better choice
for reducing bandwidth consumption.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
no CSS support.
- Dynamic elements:
Things such as being logged in/not logged in, having Google Desktop or
not, sponsored links, search listings etc. all need be take in
consideration.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
eing the first Windows browser to pass it.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
no elements in between.
You currently have
div > form > input
But the input need to be contained in one of the listed elements - for
example like this:
form > div > input
It's a question of direct parent, not ancestor.
--
, "fieldset", "ins",
> "del" start-tag
>
> I do not understand at all.
Another way to say it: The element that wraps the input MUST be one of
the above listed. Those are the only elements that allow input elments
in their contents. You probably have yo
Strict document that no browser in common
use handles due to their lack of SGML parsing.
--
David "liorean" Andersson
http://liorean.web-graphics.com/>
**
The discussion list for http://webstandardsgroup.org/
See http://webstandar
41 matches
Mail list logo