I vote for this.
Consider doing any diagramming. It's a necessary feature.
Eventually, I think canvas could be used for UML. Hey, wouldn't that
be neat? You could have a llibrary that uses a canvas to do round-trip
UML to generate real code.
Dashed lines.
--
site still down.
Most libraries now are providing a way to serialize a form.
It would be useful to have:
HTMLFormElement.prototype.toJSONString
HTMLFormElement.prototype.getDataSetString
HTMLFormElement.prototype.toJSONString would return an object literal
that contains the enabled (not readonly) form element
On 8/8/07, Garrett Smith dhtmlkitchen at gmail.com wrote:
Most libraries now are providing a way to serialize a form.
It would be useful to have:
HTMLFormElement.prototype.toJSONString
HTMLFormElement.prototype.getDataSetString
HTMLFormElement.prototype.toJSONString would
I've noticed a case when developing Ajax apps that I often end up
duplicating a call to hide loading.gif (for example) when the call
is over.
Progress Events
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/progress/Progress.html?rev=1.16content-type=text/html;%20charset=iso-8859-1#XHR
Helps
On 8/26/07, Weston Ruter [EMAIL PROTECTED] wrote:
This proposal is similar to the callbacks that Prototype's Ajax.Request
makes available. Instead of a done event, it provides the callback
onComplete: http://prototypejs.org/api/ajax/options
Thanks!
This is evidence of a real-world use case
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Garrett Smith
Sent: Sunday, August 26, 2007 8:25 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [whatwg] Progress Events done event
==
function showImage(imageHref
Section 2.3
I didn't get any responses on this. It doesn't have any cool like ajax
offline; it is a more fundamental (basic) requirement.
There is a shortcoming in the specification.
2.3. Extensions to the select element
Previous
Regarding the [type] attribute:
interface HTMLTextAreaElement : HTMLElement {
attribute DOMString defaultValue;
readonly attribute HTMLFormElement form;
attribute DOMString accessKey;
attribute long
I found a few mistakes in the spec.
===
5.1. Successful form controls
The controls that are successful are those that are included in the
submission (in the form data set) when their form is submitted.
All form controls are successful
On 9/13/07, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 13 Sep 2007, Garrett Smith wrote:
snipola
(WF2 is just a delta spec, it doesn't define anything that is already in
HTML4 and DOM2 HTML. When WF2 is merged with the rest of HTML5, it will be
turned into a real spec.)
There isn't any
Yes, I was assuming. That was my mistake. type is in fact a DOM
property, not an attribute. Should have thought twice before posting.
On 9/15/07, Magnus Kristiansen [EMAIL PROTECTED] wrote:
On Fri, 14 Sep 2007 02:52:33 +0200, Garrett Smith [EMAIL PROTECTED]
wrote:
Regarding the [type
window.onerror
There needs to be a way to capture errors on the window.
A method that passes an Error to the handler. One possible solution
would be to leverage the existing event system:
addEventListener( error, genericErrorEventHandler, false );
function genericErrorEventHandler( errorEvent
On 9/20/07, Asbjørn Ulsberg [EMAIL PROTECTED] wrote:
On Tue, 11 Sep 2007 22:22:55 +0200, Garrett Smith [EMAIL PROTECTED]
wrote:
interface HTMLFormElement {
string getDataSetString(); raises FileException
string toJSONString(); raises FileException
};
I like the idea
I've cross-posted. Bad. I'm putting this back on WHAT WG
It's a web-app thing, but related to HTML5. HTML 5 has two lists.
On 9/24/07, Subbu Allamaraju [EMAIL PROTECTED] wrote:
Does this approach take the enctype into account? What is the behavior if a
given form can't be serialized for a
On 5/21/07, Ian Hickson [EMAIL PROTECTED] wrote:
On 5/19/07, Garrett Smith [EMAIL PROTECTED] wrote:
Consider doing any diagramming. It's a necessary feature.
Not really. For straight lines it's pretty trivial to do today anyway
(either by drawing actual dashed lines or faking
On 9/26/07, Asbjørn Ulsberg [EMAIL PROTECTED] wrote:
On Tue, 25 Sep 2007 12:32:05 +0200, Asbjørn Ulsberg [EMAIL PROTECTED]
wrote:
Can't overload in JS.
Not in the normal sense, but I think you understand what I'm looking for.
There isn't any toString on HTMLFormElement.
So it can't be
nextSibling and previousSibling are useful, but not always what I want.
I usually want to get a siblingElement than a sibling, which might be
a text node.
Dom.findNextSiblingElement = function(el) {
for(var ns = el.nextSibling; ns != null; ns = ns.nextSibling)
Alpha component is equal to 1.
The color is an uppercase six-digit hexadecimal value, prefixed with a
# character
(U+0023 NUMBER SIGN), with the first two digits representing the red component,
the next two digits representing the green component, and the last two
digits representing the blue
On Jan 24, 2008 5:40 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 23 Jan 2008, Garrett Smith wrote:
nextSibling and previousSibling are useful, but not always what I want.
I usually want to get a siblingElement than a sibling, which might be a
text node.
One of the following
On Wed, Mar 26, 2008 at 10:42 AM, Tab Atkins Jr. [EMAIL PROTECTED] wrote:
On Tue, Mar 25, 2008 at 2:44 PM, Keryx Web [EMAIL PROTECTED] wrote:
I'm coming around to the opinion that dl, ul, and ol (and the new list
elements in html5) should allow a larger set of elements as their direct
On Mon, Jul 14, 2008 at 11:36 AM, Brady Eidson [EMAIL PROTECTED] wrote:
From the current spec:
onscroll - Must be invoked whenever a scroll event is targeted at or
bubbles through the element.
Link to the spec: http://www.whatwg.org/specs/web-apps/current-work/#onscroll
Yet IE and Firefox
On Mon, Jul 14, 2008 at 12:39 PM, Garrett Smith [EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 11:36 AM, Brady Eidson [EMAIL PROTECTED] wrote:
// captures bubbled change.
aForm.addEventListener(change, formChanged, false);
// doesn't capture bubbled change.
aForm.onchange
I took a brief look at the WF 2.0 document yesterday and found some
serious misconceptions and examples of programming by coincidence.
These reflect very poorly on html5.
The errors can be found on the link:
http://www.whatwg.org/specs/web-forms/current-work/#select-check-default
Doc Bugs:
1)
Examples should work.
Citation from:
http://www.whatwg.org/specs/web-apps/current-work/#outlines
The following JavaScript function shows how the tree walk could be
implemented. The root argument is the root of the tree to
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Garrett Smith
Sent: Wednesday, July 30, 2008 8:34 AM
To: [EMAIL PROTECTED]
Subject: [whatwg] HTML 5 : Misconceptions Documented
I took a brief look at the WF 2.0 document yesterday and found some
On Wed, Jul 30, 2008 at 2:42 AM, Ian Hickson [EMAIL PROTECTED] wrote:
On Tue, 29 Jul 2008, Garrett Smith wrote:
var s = ;
test(document,
function (a) { s += enter + a + \n; },
function (a) { s += exit + a + \n; });
s
The output was what I expected. There were
.
Typing HTMLCollection is longer than typing array but it is misleading.
But that still leaves the other two issues. The first is the worst, I
think, because it relies on deprecated behavior and isn't very good
practice.
Garrett
On Tue, Jul 29, 2008 at 11:33 PM, Garrett Smith [EMAIL PROTECTED
On Mon, Aug 4, 2008 at 3:17 PM, Thomas Broyer [EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 8:33 AM, Garrett Smith wrote:
(3) There is no specification for a special [[Get]] for the elements
HTMLCollection as a shortcut to namedItem, either (though this would not
seem to be a problem
On Tue, Aug 5, 2008 at 4:02 PM, Thomas Broyer [EMAIL PROTECTED] wrote:
On Tue, Aug 5, 2008 at 8:03 AM, Garrett Smith wrote:
On Mon, Aug 4, 2008 at 3:17 PM, Thomas Broyer wrote:
Actually, there is:
http://www.w3.org/TR/html5/dom.html#htmlcollection
and I believe the elements property
On Wed, Aug 6, 2008 at 2:29 AM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 6, 2008, at 12:27 AM, Cameron McCormack wrote:
Hi Garrett.
Garrett Smith:
[snip]
Your tests do show that the HTML collections expose items through real
properties rather than fake ones returned through
On Wed, Aug 6, 2008 at 7:03 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 6, 2008, at 11:23 AM, Garrett Smith wrote:
My apologies for being rude.
What would you suggest, Maciej?
I would suggest:
a) Point out mistakes courteously.
Done.
b) Preferably do so in the appropriate
On Wed, Aug 6, 2008 at 7:06 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 6, 2008, at 7:17 AM, Thomas Broyer wrote:
On Wed, Aug 6, 2008 at 11:29 AM, Maciej Stachowiak wrote:
I think Web IDL should provide a formalism to cater to this, because
nearly
all bindings with special
(put back on list, forgot to reply-all)
On Thu, Aug 7, 2008 at 2:16 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 7, 2008, at 1:51 PM, Garrett Smith wrote:
On Wed, Aug 6, 2008 at 7:06 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 6, 2008, at 7:17 AM, Thomas Broyer wrote
On Thu, Aug 7, 2008 at 4:37 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 7, 2008, at 3:44 PM, Garrett Smith wrote:
I'd like to put this back on the list, and it doesn't contain anything
personal, so I'm taking the liberty here.
I'm not sure what you mean by in the binding.
I meant
Of Garrett Smith
Sent: Saturday, August 09, 2008 2:06 AM
To: WHATWG List
Cc: Maciej Stachowiak
Subject: Re: [whatwg] HTML 5 : Misconceptions Documented
On Thu, Aug 7, 2008 at 4:37 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Aug 7, 2008, at 3:44 PM, Garrett Smith wrote:
I'd
(to list)
-- Forwarded message --
From: Garrett Smith [EMAIL PROTECTED]
Date: Tue, Aug 12, 2008 at 11:00 AM
Subject: Re: [whatwg] HTML 5 : Misconceptions Documented
To: Kristof Zelechovski [EMAIL PROTECTED]
On Tue, Aug 12, 2008 at 4:53 AM, Kristof Zelechovski
[EMAIL PROTECTED
[back to whatwg list.]
-- Forwarded message --
From: Garrett Smith [EMAIL PROTECTED]
Date: 2008/8/12
Subject: Fwd: [whatwg] HTML 5 : Misconceptions Documented
To: CSS 3 W3C Group [EMAIL PROTECTED]
2008/8/12 Křištof Želechovski [EMAIL PROTECTED]:
Another top post.
Reading
On Wed, Aug 13, 2008 at 2:02 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 13 Aug 2008, Kristof Zelechovski wrote:
While we are at collections and arrays, it is worth noting that the
{coll.length} attribute is a misnomer. I would always ask for
{coll.count} when I was learning and
On Thu, Aug 14, 2008 at 6:15 PM, Garrett Smith [EMAIL PROTECTED] wrote:
On Wed, Aug 13, 2008 at 2:02 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 13 Aug 2008, Kristof Zelechovski wrote:
While we are at collections and arrays, it is worth noting that the
{coll.length} attribute
On Tue, Aug 19, 2008 at 6:16 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Sat, 22 Sep 2007, Garrett Smith wrote:
window.onerror
There needs to be a way to capture errors on the window.
Is window.onerror not enough?
window.onerror would be sufficient if it:
* accepted an Error parameter
On Tue, Aug 19, 2008 at 6:13 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 15 Aug 2007, Leons Petrazickis wrote:
On 8/15/07, Michael A. Puls II [EMAIL PROTECTED] wrote:
On 8/14/07, Ian Hickson [EMAIL PROTECTED] wrote:
On Sat, 11 Aug 2007, Michael A. Puls II wrote:
We ended up using
On Thu, Aug 14, 2008 at 1:18 AM, timeless [EMAIL PROTECTED] wrote:
On Tue, Aug 12, 2008 at 12:53 AM, Kristof Zelechovski
[EMAIL PROTECTED] wrote:
I have considered inline response. I have two options: do it by hand (I am
rather busy) and do it for every reply (which makes business people
On Wed, Aug 20, 2008 at 11:00 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 20 Aug 2008, Garrett Smith wrote:
http://www.whatwg.org/specs/web-apps/current-work/#onhashchange
| onhashchange
|
|Must be invoked whenever a hashchange event
| is targeted at or bubbles through the element
On Thu, Aug 21, 2008 at 4:09 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 21 Aug 2008, Garrett Smith wrote:
HTML 5 expands hashchange to any element. Any element, such as div
or pre? How can you know if an element supports hashchange or not?
I'm not sure what you mean. In HTML5, all
On Tue, May 6, 2008 at 4:04 AM, Ian Hickson [EMAIL PROTECTED] wrote:
heycam -- see at the end for a request for WebIDL.
On Mon, 25 Apr 2005, Brad Neuberg wrote:
True, but having prototypes on DOM objects can be extremely useful and
provide all sorts of very powerful options. Mozilla allows
On Sat, Aug 30, 2008 at 8:50 PM, Biju [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
http://www.w3schools.com/ is a very popular tutorial site.
Yes, that is annoying. It's always at the top of the search result.
w3schools has no relationship with the w3c. It is not the most
reliable source of
On Thu, Aug 21, 2008 at 4:09 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 21 Aug 2008, Garrett Smith wrote:
HTML 5 expands hashchange to any element. Any element, such as div
or pre? How can you know if an element supports hashchange or not?
I still wonder about this.
hashchange seems
On Tue, Sep 9, 2008 at 1:49 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Tue, 9 Sep 2008, Garrett Smith wrote:
Please be patient. There are literally thousands of e-mails that will need
to be dealt with before yours.
I am being patient.
There may very well be a list subscriber who has
On Tue, Sep 9, 2008 at 12:48 PM, Garrett Smith [EMAIL PROTECTED] wrote:
On Thu, Aug 21, 2008 at 4:09 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 21 Aug 2008, Garrett Smith wrote:
and what if you have:
body onhashchange=alert(document.body.ohashchange
On Tue, Sep 9, 2008 at 12:48 PM, Garrett Smith [EMAIL PROTECTED] wrote:
On Thu, Aug 21, 2008 at 4:09 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 21 Aug 2008, Garrett Smith wrote:
and what if you have:
body onhashchange=alert(document.body.ohashchange
On Fri, Sep 12, 2008 at 1:44 PM, Brenton Strine
[EMAIL PROTECTED] wrote:
Is there some place that documents the parts of HTML 5 that are already up
and running? Can I use canvas or video? In which browsers?
http://www.whatwg.org/specs/web-apps/current-work/#the-canvas
What other tags can I
On Fri, Sep 19, 2008 at 3:41 PM, Ozob the Great [EMAIL PROTECTED] wrote:
Thoughts?
It doesn't work in any browser.
Be creative and use classes.
.function
.identifier
.operator
.paren
.bracket
You might even be able to find some microformat for that. (Microformat
is becoming a bit of a
On Sat, Sep 20, 2008 at 4:08 PM, Ozob the Great [EMAIL PROTECTED] wrote:
On Sat, Sep 20, 2008 at 6:41 PM, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
Ozob the Great wrote:
Making HTML that much richer would require duplicating a large chunk of
MathML, which is undesirable.
There's
On Tue, Sep 30, 2008 at 12:37 AM, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
Garrett Smith wrote:
|placeholder| sounds a little like |alt|. Alt is a property and an
attribute on INPUT.
How is placeholder content for a form field alternative text?
If and until user enters text
-- Forwarded message --
From: Garrett Smith [EMAIL PROTECTED]
Date: Tue, Sep 30, 2008 at 11:49 AM
Subject: Re: [whatwg] Placeholder option for text input boxes
To: Tab Atkins Jr. [EMAIL PROTECTED]
On Tue, Sep 30, 2008 at 10:04 AM, Tab Atkins Jr. [EMAIL PROTECTED] wrote:
On Tue
On Tue, Sep 30, 2008 at 12:14 PM, Nils Dagsson Moskopp
[EMAIL PROTECTED] wrote:
Am Dienstag, den 30.09.2008, 11:49 -0700 schrieb Garrett Smith:
Are there any arguments against a |placeholder| property on INPUT?
Missing semantics ? It is a purely presentational attribute.
The semantics would
to
work for new attributes.
Can you provide an example or evidence of DOM properties becoming
obsolete (other than safari not supporting input.placeholder)?
Garrett
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Garrett Smith
Sent: Tuesday
On Tue, Sep 30, 2008 at 3:46 PM, Andy Lyttle [EMAIL PROTECTED] wrote:
On Sep 30, 2008, at 2:55 PM, Christoph Päper wrote:
Anyhow, the appearance of this or other types of |input| should not be
specified by HTML5 / WF2+.
Of course browsers could choose what the icon should look like;
Would
On Wed, Oct 1, 2008 at 5:11 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Oct 1, 2008, at 10:27 AM, Aaron Boodman wrote:
On Wed, Oct 1, 2008 at 10:05 AM, Kristof Zelechovski
[EMAIL PROTECTED] wrote:
Please. This thread is not abort how to write JavaScript code in
general.
It is about
On Thu, Oct 2, 2008 at 4:34 PM, Tab Atkins Jr. [EMAIL PROTECTED] wrote:
On Thu, Oct 2, 2008 at 6:27 PM, Brenton Strine [EMAIL PROTECTED]
wrote:
On Tue, Sep 30, 2008 at 11:36 AM, Andy Lyttle [EMAIL PROTECTED] wrote:
Of course, it's still not in any way semantic. The only difference between
On Fri, Oct 3, 2008 at 8:05 AM, Tab Atkins Jr. [EMAIL PROTECTED] wrote:
On Fri, Oct 3, 2008 at 9:32 AM, Garrett Smith [EMAIL PROTECTED]
wrote:
On Thu, Oct 2, 2008 at 4:34 PM, Tab Atkins Jr. [EMAIL PROTECTED]
wrote:
On Thu, Oct 2, 2008 at 6:27 PM, Brenton Strine
[EMAIL PROTECTED]
wrote
On Sun, Oct 5, 2008 at 1:07 PM, L. David Baron [EMAIL PROTECTED] wrote:
On Sunday 2008-10-05 12:20 -0700, Garrett Smith wrote:
But what if the designer wants to use an image?
input type=search placeholder=ybang.gif
Would display the text:
bang.gif
- not the binary resource of the image
On Sun, Oct 5, 2008 at 1:33 PM, Garrett Smith [EMAIL PROTECTED] wrote:
On Sun, Oct 5, 2008 at 1:07 PM, L. David Baron [EMAIL PROTECTED] wrote:
On Sunday 2008-10-05 12:20 -0700, Garrett Smith wrote:
What other use case did you have?
Were you t hinking of allowing styling of the placeholder
Excerpt:
prevents script from reading the document.cookies DOM attribute.
http://www.whatwg.org/specs/web-apps/current-work/#sandboxed-origin-browsing-context-flag
Should this be |document.cookie| instead of document.cookies?
Garrett
-- Forwarded message --
From: Garrett Smith [EMAIL PROTECTED]
Date: Sun, Oct 19, 2008 at 9:12 AM
Subject: Re: [whatwg] a and button
To: Håkon Wium Lie [EMAIL PROTECTED]
Håkon Wium Lie wrote:
Also sprach Kornel Lesinski:
It's not a link. I'd like for buttons to work
Ian Hickson wrote:
On Wed, 6 Jun 2007, Sander wrote:
The specs say that for select ...the change event shall be fired when
the selection is completed Does this mean that, when using a
keyboard for navigation, the change event is fired when the user hits
'enter' or when she navigates from
On Mon, Nov 10, 2008 at 7:59 AM, Ian Hickson [EMAIL PROTECTED] wrote:
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
On Mon, 10 Nov 2008, Tommy Thorsen wrote:
From an implementors point of view, it's good to have clearly defined
boundaries between modules. An implementation would typically have
On Tue, Nov 11, 2008 at 11:21 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Tue, 11 Nov 2008, Garrett Smith wrote:
Unfortunately, we have little choice in the matter. Scripting and XML
both allow you to unambiguously create highly non-conforming DOMs,
e.g. with title elements as the root
On Mon, Nov 10, 2008 at 12:56 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 14 Aug 2008, Garrett Smith wrote:
There is no note in the WF 2.0 specification, nor the HTML 4.01, nor the
HTML DOM specifications that an element should not be named submit or
action to avoid such consequences
On Sat, Dec 6, 2008 at 7:09 PM, Calogero Alex Baldacchino
[EMAIL PROTECTED] wrote:
Simon Pieters ha scritto:
On Fri, 05 Dec 2008 19:19:04 +0100, Calogero Alex Baldacchino
[EMAIL PROTECTED] wrote:
[...]
(I'm currently the editor of that proposal, currently located at
On Wed, Dec 10, 2008 at 8:10 AM, Calogero Alex Baldacchino
[EMAIL PROTECTED] wrote:
Garrett Smith ha scritto:
On Sat, Dec 6, 2008 at 7:09 PM, Calogero Alex Baldacchino
[EMAIL PROTECTED] wrote:
Simon Pieters ha scritto:
On Fri, 05 Dec 2008 19:19:04 +0100, Calogero Alex Baldacchino
[EMAIL
On Thu, Feb 28, 2008 at 10:31 AM, h...@nczonline.net wrote:
We then, as developers, could use that attribute as we see fit and
the document would still validate (for people who care about such
things).
-
Are people who care about things are the
On Mon, Dec 15, 2008 at 6:32 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Sat, Dec 13, 2008 at 1:40 AM, Garrett Smith dhtmlkitc...@gmail.com
wrote:
On Thu, Feb 28, 2008 at 10:31 AM, h...@nczonline.net wrote:
We then, as developers, could use that attribute as we see fit
On Mon, Dec 15, 2008 at 8:02 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
You're not Nicholas. We don't know if that is what Nicholas expects
his HTML to do or if he is expecting something else. In absence of an
example, I can't do much more than guess. I cannot expect your
assumptions to be
On Mon, Dec 15, 2008 at 6:36 PM, Garrett Smith dhtmlkitc...@gmail.com wrote:
On Mon, Dec 15, 2008 at 8:02 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Valid HTML can have a clear and expected outcome. If something is done
according to standard, it can be expected that that something
On Tue, Dec 16, 2008 at 5:14 AM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
Maybe so-called invalid HTML attributes are not the only solution, but in
my opinion it is a simple way to embed metadata within any element.
Imagine that such markup is then passed to a web application through
On Sun, Dec 21, 2008 at 10:12 AM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
Please Note: all the following is my personal humble opinion.
parser is involved), events are far better handled by DOM3Events, styling is
included by CSSOM
Styling is done in css.
I don't have time to go
On Thu, Dec 25, 2008 at 9:51 AM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
2008/12/25 Ian Hickson i...@hixie.ch
XMLHttpRequest was invented by Netscape, now it is a W3C Technical Report (I
don't remember what maturity level). The same with so called DOM level 0
(now HTML5)
No,
On Tue, Jan 6, 2009 at 9:11 PM, Michael A. Puls II shadow2...@gmail.com wrote:
On Tue, 06 Jan 2009 17:07:00 -0500, Ian Hickson i...@hixie.ch wrote:
On Tue, 6 Jan 2009, Michael A. Puls II wrote:
Are browsers actually buggy here?
You probably won't buy it, but I like the idea of using a
(back on list)
On Wed, Jan 14, 2009 at 2:04 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 13 Jan 2009, Garrett Smith wrote:
On Tue, Jan 13, 2009 at 6:41 PM, Ian Hickson i...@hixie.ch wrote:
There were a number of e-mails on this thread regarding how Collections
Which thread are referring
On Thu, Jan 15, 2009 at 11:40 AM, Ian Hickson i...@hixie.ch wrote:
On Thu, 15 Jan 2009, Garrett Smith wrote:
If I understand this correctly, given a FORM with an INPUT named 'b', if
I change the name of that INPUT to 'a', then form.b should return the
element with name=a.
That isn't how
On Wed, Feb 4, 2009 at 2:45 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 4 Feb 2009, Robert O'Rourke wrote:
Are there any plans to bring list headers from HTML3 into HTML5? They'd
make a lot of markup patterns simpler and be very very useful when it
comes to styling.
You can do this in
On Wed, Feb 4, 2009 at 2:50 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
Christian Svindseth wrote:
On Feb 4, 2009, at 11:13 AM, Robert O'Rourke wrote:
Are there any plans to bring list headers from HTML3 into HTML5? They'd
make a lot of markup patterns simpler and be very very useful
Sometimes a document's resources are not needed all at first. For
example, a script that is not needed until after the document is
parsed can be given the defer attribute (for browsers that support
defer).
External css can also be a blocking download. Scripts have defer
attribute, but style and
On Sun, Feb 8, 2009 at 9:20 PM, Ian Hickson i...@hixie.ch wrote:
On Sun, 8 Feb 2009, Garrett Smith wrote:
Sometimes a document's resources are not needed all at first. For
example, a script that is not needed until after the document is parsed
can be given the defer attribute (for browsers
On Mon, Feb 9, 2009 at 2:26 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 9 Feb 2009, Garrett Smith wrote:
On Sun, Feb 8, 2009 at 9:20 PM, Ian Hickson i...@hixie.ch wrote:
On Sun, 8 Feb 2009, Garrett Smith wrote:
Sometimes a document's resources are not needed all at first. For
example
On Mon, Feb 9, 2009 at 9:42 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Garrett Smith wrote:
The script's defer attribute does not work in a majority of
implementations. For such browsers, it makes sense to put the script
lower on the page for performance reasons, not before the linked
On Mon, Feb 9, 2009 at 11:54 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Garrett Smith wrote:
There are two/three issues.
1) want to load stylesheets without having scripts block
Already doable for alternate stylesheets, right?
An html document could contain an alternate stylesheet, intended
On Mon, Feb 9, 2009 at 7:37 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Garrett Smith wrote:
In general, I want better declarative control over loading external
resources. The solution(s) should not cause compatibility problems
with existing browsers (because I have to support IE6 and Firefox 2
On Thu, Feb 12, 2009 at 8:41 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Garrett Smith wrote:
In Shiretoko, a script, even a deferred script, will not run until the
stylesheet is loaded.
Correct.
Can we make an improvement on that, or to make that improvement
configurable to the page
is waited on? Does it happen for all scripts? For example,
if a script inserts a style sheet and then a script, does that script wait
for the style sheet to load?
On Mon, 9 Feb 2009, Garrett Smith wrote:
If I put the script at the bottom of the page, and a linked stylesheet
in the head
On Sun, Feb 15, 2009 at 9:54 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Garrett Smith wrote:
Because you have scripts after your stylesheets, not just stylesheets.
Really, controlled experiments are hard. You have to hold all but one
variable constant.
OK, I modified the example:
http
On Sat, Feb 21, 2009 at 8:27 AM, Tom Duhamel tom420.duha...@gmail.com wrote:
On Sat, Feb 21, 2009 at 7:37 AM, mikemi...@verizon.net wrote:
I have a suggestion for HTML5 involving the currently planned doctype,
!DOCTYPE HTML.
It came to my mind that there could be many a web developer,
On Fri, Mar 6, 2009 at 8:40 PM, Oliver Hunt oli...@apple.com wrote:
So I've been looking at importScripts
(http://www.whatwg.org/specs/web-workers/current-work/#importing-scripts-and-libraries )
I dislike the synchronous design of that feature.
An asynchronous solution brought up very recently
On Sat, Mar 14, 2009 at 1:48 PM, Greg Houston gregory.hous...@gmail.com wrote:
This is a request for the link element to be given an onload attribute.
I see.
Often when lazy loading a plugin into an web app it is necessary for
the plugin's stylesheets to be applied before the plugin's
On Sat, Mar 14, 2009 at 5:24 PM, Greg Houston gregory.hous...@gmail.com wrote:
On Sat, Mar 14, 2009 at 4:46 PM, Garrett Smith dhtmlkitc...@gmail.com wrote:
I proposed a solution to a similar problem not too long ago.
script depends=[idref] .../script
For me to implement my own depends lazy
On Sat, Mar 14, 2009 at 6:54 PM, Jonas Sicking jo...@sicking.cc wrote:
On Sat, Mar 14, 2009 at 1:48 PM, Greg Houston gregory.hous...@gmail.com
wrote:
[...]
Garrett: Whatever we decide when it comes to the defer attribute, it
is always useful to have scripting APIs as well. There is just no
On Sun, Mar 15, 2009 at 12:07 AM, Jonas Sicking jo...@sicking.cc wrote:
On Sat, Mar 14, 2009 at 10:21 PM, Garrett Smith dhtmlkitc...@gmail.com
wrote:
On Sat, Mar 14, 2009 at 6:54 PM, Jonas Sicking jo...@sicking.cc wrote:
On Sat, Mar 14, 2009 at 1:48 PM, Greg Houston gregory.hous...@gmail.com
On Fri, Apr 24, 2009 at 2:59 PM, Ojan Vafai o...@chromium.org wrote:
On Fri, Apr 24, 2009 at 2:43 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Erik Arvidsson wrote:
I do agree that the EventTarget API is suboptimal and so are most of
the DOM APIs but it is what we got and we need tie the lose
On Wed, Apr 29, 2009 at 11:39 AM, Alex Russell slightly...@google.com wrote:
On Fri, Apr 24, 2009 at 6:37 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Ojan Vafai wrote:
A workable system that improves on the current state should *at least*
return disconnectable handles, and hopefully also
1 - 100 of 234 matches
Mail list logo
