m.
>
> Then why not take just one more tiny step and encourage everyone to do
> so?
You were asking for requirements before. If you just want encouragement,
then write a blog post about the matter, or add a page to the wiki, or
write a tutorial or opinion piece or whatever. It's out of scope for the
specification.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
nteresting. I don't have the time to set
something like this up, sadly. However, if you are willing to help, I
would definitely be open to chatting on IRC to explain various design
decisions which you could then document on the wiki or in blog posts.
--
Ian
made, and contribute
> with feedback instead of having to ask for the reasons of the desicions
> first.
Feel free to ask the questions. :-) Often, there might not be any
conscious reeasoning, and having the question asked may highlight problems
that had not previously been considered.
--
On Thu, 14 Dec 2006, Anne van Kesteren wrote:
>
> For a string like:
>
> TEST
>
> The current text seems to suggest the following DOM (not including everything
> here):
>
>
>
> "TEST"
>
> Because is not a phrasing nor a formatting
ven't examined the proposal yet), I just want to
make the point that the fact that one non-implemented feature is not a
solution because it isn't implemented yet is not an argument in favour of
another feature that is just as unimplemented but even less well defined. :-)
--
Ian Hicks
ot;
>
> The second sentence should probably say "xml:lang", not "lang", since
> HTML authors are actually supposed to use lang.
Good catch. Thanks. Fixed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/
that gets associated with it (if any).
> """
>
> I assume the "it" in "it must be dropped" refers to the attribute being
> currently parsed, not the one which were already there on the token (at
> least, this is what was assumed in python'
rates an index (e.g.
index.whatwg.org or maybe a page auto-maintained on the wiki or something)
please send me an e-mail off-list and we can set something up.
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hix
On Thu, 21 Dec 2006, Karl Dubost wrote:
>
> Le 21 d�c. 2006 � 14:19, Ian Hickson a �crit :
> > If anyone (Karl?) wants to maintain an index page somewhere that
> > autogenerates an index
>
> http://esw.w3.org/topic/HtmlIndex
On Thu, 21 Dec 2006, Matt McDonald wrote:
>
st affects whether to use
strict mode or quirks mode, it doesn't affect anything else, and in
particular has no bearing on whether the document itself has parse errors
or not.
> So I'll just code it so that these are "correct":
>
>
> and every other lowercase/up
nts
> in a few processing rules. What is the status of this element? I cannot
> find any discussion of its fate in the mailing list archives.
will be defined in due course.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http:/
s of the HTML5 spec is dealing with tag soup, I
> would think that a scope that does not attempt to address that issue is
> A Bad Thing(tm).
The "tag soup" is just the parsing rules. The parsing rules are part of
the markup language. The markup language is explicitly in scope.
HTH,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
hooray, that's someone who isn't misusing ".
For the record, note that is now in HTML5. If I recall correctly,
the only element now missing is , and that will be added in due
course (when I get around to speccing what WYSIWYG editors are allowed to
do).
--
Ian Hickson
sers
> handle them. Thoughts?
>
> [1] http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.src.html
> [2] http://xulplanet.com/ndeakin/xul/specs/scrollspec.html
I believe Anne is working on the spec ([1]) to cover these. Anne?
If he's not, then yeah, I'll have to make sure the
e popped of from the stack of open elements.
> Shouldn't that be covered?
Doesn't matter how they are popped from the stack. You could just throw
the stack away and be done. Once you stop parsing, the stack is never
again used, and never affects the document.
--
Ian Hickson
On Thu, 4 Jan 2007, Anne van Kesteren wrote:
>
> On Thu, 04 Jan 2007 00:57:46 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > For the record, note that is now in HTML5. If I recall correctly,
> > the only element now missing is , and that will be added in due
> >
switch to using the new elements. We have
to balance making life easier for early adopters with making life better
on the long run.
What's the use case for elements containing inlines?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/
On Thu, 4 Jan 2007, Anne van Kesteren wrote:
> On Thu, 04 Jan 2007 01:50:34 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > >
> > > There are of course far more elements not in HTML5 than just .
> > > It's not really clear to me what you mean here. Ca
de is not a body node, this is a parse
> error.
Isn't this just reversing the two paragraphs and moving the Otherwise to
the other paragraph? What's the practical difference? I'm confused.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Thu, 4 Jan 2007, Kornel Lesinski wrote:
> On Thu, 04 Jan 2007 00:58:34 -0000, Ian Hickson <[EMAIL PROTECTED]> wrote:
>
> > What's the use case for elements containing inlines?
>
> From microformats.org:
>
>
> http://tantek.com/";>Tante
On Thu, 4 Jan 2007, Anne van Kesteren wrote:
> On Thu, 04 Jan 2007 02:14:37 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > How doesn't it introduce a condition? It's one big "if". In fact, it's two
> > of them.
>
> To me it's ambiguous
On Thu, 4 Jan 2007, Anne van Kesteren wrote:
> On Thu, 04 Jan 2007 02:27:33 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > On Thu, 4 Jan 2007, Anne van Kesteren wrote:
> > > On Thu, 04 Jan 2007 02:14:37 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > >
to post such suggestions on the blog (to gather feedback)
and then to create Wiki pages detailing the suggestions and including
summaries of the feedback you received. You could have suggestions for UI
for browsers for various features in the spec, as well as including
suggestions
o might see me generate a fair number of
> separate emails.)
Either is fine by me. Whatever is easier for you is best.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
There are no rules. Things can always be fixed
later, that's the magic of Wikis! :-)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
e non-conformant, but what should UAs do?
The specs on Ruby currently at the W3C (both for CSS and for XHTML) are
woefully inadequate in terms of describing error handling rules right now.
--
Ian Hickson U+1047E)\._.,--..
n WF2 is integrated with WA1, unless
there are interoperability issues that mean it should be dropped.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ere any of those, too, etc.)
So any other bug -- like the missing EOF -- is quite minor. :-)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ng authors to copy them from one to hte other
> format and back.
Indeed.
On Mon, 15 Jan 2007, Stefan Haustein wrote:
>
> could somebody please clarify whether the unusual parameter order is
> intended -- or simply a bug in the specification?
It was a bug in the specification.
C
to introduce a special behaviour
for a newline at the start of a element. IE actually does it for
more than just the element (e.g. it does it for , though not
) but compatibility with the Web only seems to require it for
since that's all that the other browsers do it for.
Fixed
On Fri, 19 Jan 2007, Sam Ruby wrote:
> > >
> > > [in standards mode]
> >
> > I couldn't reproduce this. In Firefox trunk, with:
> >
> > http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%3Cstyle%3Epre%20%7B%20border%3A%20solid%3B%20%7D%3C/style%3E%0A%3Cpre%3E%0Ax%0A%3
On Sun, 21 Jan 2007, Allan Sandfeld Jensen wrote:
>
> On Saturday 20 January 2007 01:08, Ian Hickson wrote:
> >
> > In HTML5, we're dropping that requirement, since everyone ignores it.
> > However, we will, as you point out, have to introduce a special behaviour
>
o follow to appear perfectly
> on both
I'm afraid this is not a help support mailing list. I recommend contacting
your browser vendor manufacturers to report the differences.
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
h
ince this editor artifact is harmless in browsers and useful in
> editors, it would be nice if the spec made it conforming at least on the
> element in XHTML5.
It's automatically conforming everywhere, no? Isn't it an XML thing?
--
Ian Hickson U+1047E
g.
Right now I haven't made any effort to conform to one or the other, as
which one is eventually used depends on where the spec ends up. Before the
spec is finished it will have a spelling cleanup.
--
Ian Hickson U+1047E)\._.,--,'
his work in progress could be made public, it would
be a great help. Some of the ideas in the XForms-Tiny examples look
interesting, but without seeing the overall model they really are not
clear enough to use as feedback on the Web Forms 2 W3C working draft.
Cheers,
--
Ian Hic
ly as Google managed to index it, and they obey robots.txt).
For the record, the document in question is permanently archived at:
http://lists.w3.org/Archives/Member/w3c-archive/2003Sep/att-0014/hfp.html
Cheers,
--
Ian Hickson U+1047E)\._.,--,'
wards-multi-touch-in-the-browser
An interesting point.
I recommend bringing this up with the WebAPI working group, who are
working on mouse events and the DOM events model in general.
http://www.w3.org/2006/webapi/
--
Ian Hickson U+1047E
the form *node* the control is associated with.
> Turning that into a list of strings will break a lot of existing content
> like
>
>
>
> I'd rename the form attribute to formsList . (Name is up for discussion
> of course..)
The "form attribute" in the
s stuff which might list others.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
rking group at the W3C work on the suggested "DOM Bindings
For ECMAScript" specification before going ahead, since there's no point
duplicating effort.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/,
anything else wrong (in particular, I didn't test what should happen
outside the "start" circle).
Thanks,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
by handling each case specifically or stating in general that the
> specified algorithms always apply or something.
Ok.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
aList;
>
> }
>
> Admittedly these are much less likely to be toggled at runtime in the
> browser than the class, but it may be useful for scripts that search the
> document for anchors with particular relationships, for example.
mediaList is complicated, but will get its own
atibilities, the XHTML5 specification will be fixed to match.
I hope this answers your questions. There were a number of other e-mails
on this thread, which I will reply in due course, though not for some
time. If people want specific e-mails replied to sooner, pleas
ipt Bindings for DOM or something in case of ECMAScript.
I agree. And once that spec exists...
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
consistent authoring styles for this stuff.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
signMode is how they handle scripting and events.
> So my question is, should this be stated within the contentEditable
> section, or within the to-be-written designMode section?
I have added it to the now-written designMode section.
Cheers,
--
Ian Hic
atch the research I have done -- could you elaborate
on the methodology you used to obtain these numbers? Based on my own
research I would say that 45% is far over-estimating the number of pages
on the Web that are generated using PHP.
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
to avoid the mess that the
.defaultFoo stuff has caused over the years. Do you disagree with this
decision?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Mon, 19 Feb 2007, Vlad Alexander (xhtml.com) wrote:
>
> Why do we need X/HTML 5? When did this need become apparent?
HTML started as a document language for scientist to share their
work. It evolved over time; for example the element was added,
forms were added, WYSIWYG features were added, an
eb sites)?
According to some other research we did for the HTML5 effort, over 95% of
the Web today is HTML, with the rest being mostly a smattering of PDF,
Word, and plain text. Under what definition of the word could it be
considered "dead"? Web designers never stopped writing HTML pages. I don't
think we'll have any difficulty convincing them to continue doing so.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
the best we can do is design the language to make "the right
thing" easier, and invest more heavily in education. In this regard HTML
is in the same boat as more important subjects; I imagine that as we
improve the quality of education in general, understanding of the
importance of
, actually. The IETF has done a good job of being open.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
oblems. However, we have a
separate mailing list for design problems, which you are welcome to join.
It is [EMAIL PROTECTED] See more information here:
http://lists.whatwg.org/listinfo.cgi/help-whatwg.org
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.f
#x27;d love to make the spec easier to use for education.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
elated to code that's
doing stuff.
On 24 Oct 2006, then again on 6 Dec 2006, Alexey Feldgendler wrote:
>
> Why do we need an <event-source> element in the markup? It only makes
> sense in conjunction with scripting, so I think it would be better to
> drop this element and have the event source objects only created by
> scripts. Similar practices are already established for objects like
> XMLHttpRequest, XSLTransform (to name a few).
Primarily for ease of scripting. This:
<script>
function process(msg) {
// ...
}
...is easier than:
function process(msg) {
// ...
}
document.addEventListener('message',
function (event) { process(event.data) },
false);
document.addEventSource('stocks.cgi');
However, looking forward, especially in conjunction with XBL2, one could
imagine systems built around responding to events, such that we could end
up having things like:
...where the stockTicker element is implemented by XBL, and expects a
stream of messages to be targetted at, or to bubble past, the bound
element; the event-source element can then provide these events without
any scripting on the part of the author.
There were also some comments about the event-source format itself related
to what happens with feeds with no trailing newline. I fixed the format
description.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
the connection in 60,000 milliseconds (1
> minute).
I've added this to the spec as a comment.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
x27;message'.
Fixed the example.
> Editorial: in the "Message events" section the definition "message" is
> not marked up with . And the "onmessage" event handler points
> doesn't point to it.
Is that still there? I couldn't find it.
--
Ian
er-side system can include such events at the start of the
feed, certainly. But I don't see that you'd want to see the events from
the previous page load itself. If anything, if you're reloading the page
it's to get rid of the existing content, no?
> > I can see cases (e.g. games) where you'd want all events since the
> > page was generated, to make sure the game state since then can be
> > represented -- but that's easy enough, two techniques would be first
> > to include a generation number in the URI, and second to make the
> > first event sent back be a complete update of the current state.
>
> Yes, the first techniques require the server to dynamically generate the
> URI on a per-client basis. I think.
Certainly. I'd fully expect this to be the case. I don't see how this
differs from the case you give.
Thanks again for your input! Please do keep it coming. :-)
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ed
> > > | not to display frames.
> > > |
> >
> > That's a pretty convincing argument against this element. :-)
>
> I get what you're saying, but I don't see a better solution for
> backwards compatibility.
Showing the content itself w
On Wed, 28 Feb 2007, Anne van Kesteren wrote:
> On Wed, 28 Feb 2007 04:01:55 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > > Editorial: in the "Message events" section the definition "message" is
> > > not marked up with . And the "onmes
but requires UAs to
support both. Please let me know if that satisfies your request -- I know
it's not quite what you asked for, but allowing both seemed pointless.
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A
On Sat, 8 Jan 2005, Matthew Thomas wrote:
> On 8 Jan, 2005, at 3:47 AM, Ian Hickson wrote:
> > ...
> > http://www.whatwg.org/specs/web-forms/current-work/#form-submission
> > ...
> > Incidentally, the markup in this section suggests to me that Web Apps
> > is goin
irectly inside DL. (In XML Schema you can express such a thing, not
> sure if it is possible using DTDs.)
On Sat, 12 Mar 2005, Matthew Raymond wrote:
>
> I did a quick test, and using in a produces a bullet on
> Firefox, IE and Opera, whereas and the complete lack of a parent
The spec
still allows them for now.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
the content models for XHTML, I see no reason not too.
Given your arguments in [EMAIL PROTECTED] and your comments in #whatwg, I
assume you have changed your mind. :-)
(The answer is that must be usable in pure-text enviroments --
indeed, the whole point of is pur
rrect. Perhaps it should be explicitly stated
> that text/xml should not be used, with a reference to the webarch
> recommendation.
I never did understand why people don't like text/*. It's nice and short
and all these types are text, so...
I've made no changes to the
k,
> etc. Could some of these be improved and included within web apps?
>
> [1] http://lachy.id.au/dev/markup/specs/wclr/
permalink = bookmark
feed = feed
via = don't have that one, do we need it?
related = it seems implicit that all links are related
referral = don't under
te of the TABLE element type) so it could as well be:
> border NUMBER #IMPLIED -- controls frame width around table --
Given that HTML5 has no DTD, this is presumably not an issue.
--
Ian Hickson U+1047E)\._.,--,'``.
for the new file.
I think this is an interesting idea, though I don't know how much demand
there is for this. I would recommend following this up with the group
documenting the NPAPI. The HTML language basically already supports what
you're asking for; although most UAs would implement
On Fri, 2 Mar 2007, Anne van Kesteren wrote:
>
> Currently it's only clear what should happen when you mutate the
> attribute. There's an assumption that there will be a new value which
> doesn't have to be the case. For instance, if the src="" attribute is
actly as written now you still get an error.
> This fails to locate the character encoding in e.g.: http-equiv="Content-Type Obviously one possibility
> is to get all attributes and then, if the current byte is ASCII < move
> the position back one.
You shouldn't get the charac
at seems like a useful feature to me.
The question isn't whether or not you should have the ability to scale
images; it's clear that this is desirable. The question is whether it
makes sense to put this in HTML as opposed to CSS. Why would HTML be the
place to put this? If we p
x27;s an open issues in HTML5. In HTML4, there's a Content-Script-Type
thing that can be used, I guess we could move this into HTML5 too now that
we have the pragma directives thing.
--
Ian Hickson U+1047E)\._.,--,'``.fL
ht
pare the algorithm for collecting the field name/value/index and
repetition block data to the algorithm for text/plain serialisation and
you'll see not all the data is used. The sentence you quote is merely
making that observation. (It's a non-normative statement.)
--
I
osted a WHATWG blog entry with this information:
http://blog.whatwg.org/w3c-restarts-html-effort
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
can't join the list without going through the
working group membership process.
But yes, it is refreshing to see the W3C adopt an approach so much more
open than most previous W3C working groups.
--
Ian Hickson U+1047E)\._.,--,'``.fL
ht
ply to
you. There's a separate set of steps for members:
http://www.w3.org/2004/01/pp-impl/40318/instructions
HTH,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
our current proposals.
http://www.whatwg.org/mailing-list#specs
http://www.whatwg.org/specs/web-apps/current-work/
> I look forward to working on HTML with you.
Indeed!
On behalf of the WHATWG,
--
Ian Hickson U+1047E)\._.
g.org/specs/web-forms/current-work/#the-autocomplete
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
don't see what you describe as a problem, but as a strength.
Sure, it's less "pure", but it is far more pragmatic, and far more likely
to actually work and remain maintainable on the long term.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
the user agent processed it and reached
> the last step of this list of steps), then abort these steps."
>
> [1] http://www.whatwg.org/specs/web-apps/current-work/#pragma
Fixed, thanks.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.
it's worth, search engine engineers I have
spoken to have told me that what browsers do is far more important than
what a particular version of a search engine does in terms of what the
specification should say, because their results are better when their
algorithms match the b
imagine the complexity of
having to implement three dozen variants just to render content written
from 2035 to 2080?
> In effect, I'm suggesting a structure like this:
>
> --Base rendering engine
> |
> +- HTML 4 quirks mode
> +- HTML 5 (
On Mon, 12 Mar 2007, Matthew Ratzloff wrote:
> On Mon, March 12, 2007 10:39 am, Ian Hickson wrote:
> >>
> >> It's tempting to think that browser makers will get it right the
> >> first time, but I'm not sure I believe it. might
> >> introduc
ng any element -
> unless we want to stick to the boring world where theres only the
> elements that enough people could agree upon.
I really don't understand what you're proposing here. What is the
problem you are trying to solve?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ion.
However, this will require coordination with the CSS working group.
datagrid::row(odd)
datagrid::row(even)
datagrid::row(.foo.bar) /* to match rows with foo and bar classes */
...etc. I'll note your list of examples for when we get to that.
Cheers,
--
Ian
o apply in real life...
Don't worry, the WHATWG basic principles put pragmatism first. It's the
only way to get a spec implemented, and without implementations, specs are
somewhat academic.
--
Ian Hickson U+1047E)\._.,--,'``.fL
ht
n do that to any select widget, whether in
a repetition template or not. If you're trying to prefixx a _form_, then
you do that at the form level, and the spec describes how it works for
repetition fields. I have no idea what you would mean by a "data"
attribute on an eleme
eturn result;
}
By the way, the [EMAIL PROTECTED] mailing list is probably more appropriate
for this thread. (That's our authoring help mailing list.)
HTH,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
way?
This is what the (not yet begun) Web Controls 1.0 specification is
intended to cover. However, there is no estimated time for work on this
specification to begin. In the meantime, I recommend contacting your
browser vendor directly.
--
Ian Hickson U+1047E)
te between
playing it and playing the content of the rest of the page; in neither
case would you simply treat the content of the media as inserted into the
playback stream with no ability to pause it independently of the main
document content).
ON SMIL
On Tue, 31 Oct 2006, Bjo
earch engines is not
important. That is what is relevant in the context of Henri's thesis.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
togglePause()
pause(true)pause()
pause(false) play()
There are (good?) reasons for the differences; I looked at the Flash API
very closely. I'll reply in more detail next week.
--
Ian Hickson
evidence suggests that we should avoid making the
mistakes SMIL made, if we want to address author needs successfully.
On Sat, 17 Mar 2007, H�kon Wium Lie wrote:
>
> Also sprach Bjoern Hoehrmann [corrected by Ian Hickson]:
>
> > ++-+
terms of solutions instead of impossibilities, you could simply have a
> property HTMLObject.objectController, which then gets you an object
> specific to the ‘media group’.
It wouldn't be "simply", though. You'd need to define how to determine
what the media group is, you'd need to define how to change from one type
to another, you'd need to have browsers implement all this on top of all
their existing bugs -- sometimes, it's just better to keep things
separate, even if they seem like they could be abstracted out into one
concept. We can't ignore our past experiences in designing HTML5.
(Incidentally, this message and the previous one was BCC'ed to everyone
who wrote e-mails that I took into account when designing the changes to
the spec. I didn't necessarily actually reply to each one, because many of
them said the same thing. Apologies for any confusion if you were BCC'ed
but didn't know why.)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
is?
* Time triggers, or cue marks, are a useful feature that has currently
been left in the v2 list; I've heard some demand for this though and I
would not be opposed to putting this in v1 if people think we should.
* I have no objection to adding more events. Once we have a bet
On Thu, 22 Mar 2007, Ian Hickson wrote:
>
> * The "mute" feature is IMHO better left at the UI level, with the API
> only having a single volume attribute. This is because there are
> multiple ways to implement muting, and it seems better to not bias the
> API to
ietary technologies are those that
are under the control of a single vendor. MPEG-4 is not proprietary.
It's not available under royalty free licensing. But it is not under the
control of a single vendor. That is the important difference, not whether
the technology is patented or not.
--
701 - 800 of 5345 matches
Mail list logo
