J. Graham wrote:
On Sat, 22 Oct 2005, Lachlan Hunt wrote:
It could be defined in reverse, where the ping attribute (probably
given a more suitable name, but I'll use ping for now) could be
advisory information about the final destination and the href
attribute defines the ping destination
:
| ...so that the user agent can [improve] the user's experience.
--
Lachlan Hunt
http://lachy.id.au/
is tagged as being 'unsafe'.
I think your confusing this with the fact that using GET requests for
data modification is unsafe, and seem to be saying that POST is unsafe
when used as intended!?
--
Lachlan Hunt
http://lachy.id.au/
.
That sounds like an implementation issue, I don't think the spec needs
to address this at all.
--
Lachlan Hunt
http://lachy.id.au/
noembed is just hidden anyway, it really shouldn't matter how its
content is parsed and parsing it like #PCDATA makes the most sense.
--
Lachlan Hunt
http://lachy.id.au/
Blake Kaplan wrote:
Lachlan Hunt wrote:
Why does it need to parse it differently depending on the mode? Since
noembed is just hidden anyway, it really shouldn't matter how its
content is parsed and parsing it like #PCDATA makes the most sense.
At least in Gecko, we parse the contents
Ian Hickson wrote:
On Mon, 28 Nov 2005, Lachlan Hunt wrote:
How about this, or some variation of:
form ...
menubar
libutton type=submit for=foo name=menuFoo/button
select id=foo name=foo
...
/select
/li
...
/menubar
/form
Interesting idea. I like the non-JS
Matthew Raymond wrote:
Lachlan Hunt wrote:
I don't believe my suggestion was altering the semantics of any element.
The intention was the use the semantics of existing controls in a way
that can rendered as a single widget that performs the functions of both
(selection and submission
Matthew Raymond wrote:
Lachlan Hunt wrote:
No, command in the current spec represents an abstract form control for
sharing features among several real form controls.
The command element is most certainly not a form control, since it
can't be submitted
I know that, I said *abstract* form
Ian Hickson wrote:
On Sat, 3 Dec 2005, Lachlan Hunt wrote:
Earlier, Ian Hickson wrote:
1. Providing a menu bar for the entire window (or application, on Mac)...
I just had a thought that maybe this could be marked up by including the
menu within the head element...
However, this would only
.
--
Lachlan Hunt
http://lachy.id.au/
Nate H. wrote:
I'm guessing nesting a select within another select will break current UAs.
Sub-menus like that will be handled with nested optgroup elements.
--
Lachlan Hunt
http://lachy.id.au/
by default would be better.
--
Lachlan Hunt
http://lachy.id.au/
annoying bugs with it.
--
Lachlan Hunt
http://lachy.id.au/
element. Although,
such cases will be reduced significantly now that we have the various
sectioning elements.
--
Lachlan Hunt
http://lachy.id.au/
a comment before it? Won't the script be executed in
exactly the same way in both cases?
However, don't take this as support for choosing to reparse it, I don't
like the concept of doing that at all for other reasons, I just don't
understand this security concern.
--
Lachlan Hunt
http
Ian Hickson wrote:
On Mon, 23 Jan 2006, Lachlan Hunt wrote:
Well, for what it's worth, I still don't think you were being stupid, I think
you were right all along and had this been implemented by more than just
Mozilla 7 years ago, the result may have been different.
Authors find the -- thing
Alexey Feldgendler wrote:
AFAIK, document.write is not standardized anywhere at all (am I right?)
http://www.w3.org/TR/2001/WD-DOM-Level-2-HTML-20011210/html.html#ID-75233634
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Tue, 24 Jan 2006, Lachlan Hunt wrote:
PA!- !--SS -- | - ! | PASS --
Comment should be - !-- IMHO. It's still a bogus comment (in HTML5
nomenclature), the -- part is irrelevant.
Ok, so if a comment only starts with '!' then it ends
Ian Hickson wrote:
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
Ian Hickson wrote:
On Tue, 24 Jan 2006, Lachlan Hunt wrote:
PA!-- FAIL -- SS | FAIL| PASS
Disagree. The terminator should be --, not -- S* . I don't see any
good reason to have -- S* .
I was working
Ian Hickson wrote:
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
I tested the following in the live dom viewer using Firefox 1.5.0.1 Win
and Mac, Opera 8.5/Mac, Opera 9 Win and Mac, Safari 2.0.3, IE6, OmniWeb
5.1.2 and iCab 3.0.1.
!DOCTYPE html
PA!-- FAIL -- SS
This triggers SGML comment
certainly, predictability. It also seems perfectly backwards compatible
with the rendering achieved in all browsers, but with a much saner DOM
under the hood.
[1] http://ln.hixie.ch/?start=1138169545count=1
--
Lachlan Hunt
http://lachy.id.au/
Billy Wong wrote:
On 1/25/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
I'm not saying it won't break anything, but every single change we make
to the parsing could possibly break any number of the billions of pages
on the web in any number of browsers.
But using your method (swapping inline node
Simon Pieters wrote:
Hi,
From: Lachlan Hunt [EMAIL PROTECTED]
However, there may be a 5th option available. Consider this, using
the following markup samples from the article.
1.
empX/emY/p
BODY
+ P
+ EM
+ #text: X
+ #text: Y
Why would you drop the first EM? Why should
came up again in July 2004 [2]
[1] http://www.w3.org/mid/[EMAIL PROTECTED]
[2] http://www.w3.org/mid/[EMAIL PROTECTED]
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Sat, 28 Jan 2006, Lachlan Hunt wrote:
Why can't it just be defined that noframes and noscript content gets
parsed exactly as regular markup
Because there are a _lot_ of side-effects of parsing as regular markup.
e.g.
noframes
style.../style
i Foo
Simon Pieters wrote:
Hi,
From: Lachlan Hunt [EMAIL PROTECTED]
As far as I can tell both of these DOCTYPEs are considered conformant,
but shouldn't the first be an easy parse error?
!DOCTYPEhtml
!DOCTYPE html
Why? Both trigger standards mode as far as I can tell. :-)
It did
Blanchard, Todd wrote:
Lachlan Hunt wrote:
Blanchard, Todd wrote:
What I want to know is: if the cloned node has an id
attribute, and id is meant to be unique, then how do we resolve
this conflict?
The ID attributes need to be duplicated in such cases, that's what
existing browsers do
Gervase Markham wrote:
Lachlan Hunt wrote:
Errors caused by the result of duplicate IDs either in the markup or
indirectly as a result of badly nested elements can be fixed by a quick
visit to the validator (or other conformance tool) or by making use of
any or all of those tools I mentioned
of the class names in the markup
is irrelevant. The order of the rules specified in the CSS is relevant
and the latter rule of equal specificity takes precedence.
--
Lachlan Hunt
http://lachy.id.au/
discussing.
The only case that won't happen is if that markup is written as a result
of document.write() or innerHTML.
--
Lachlan Hunt
http://lachy.id.au/
(href), attr(title));
}
I know it's not an extremely well thought out idea, it's just a bit of
brainstorming, but it could always be improved. It also seems to be a
little out of scope for the WhatWG.
--
Lachlan Hunt
http://lachy.id.au/
Lachlan Hunt wrote:
For example, using this CSS-like syntax (but it's not CSS).
selector {
event-name: function();
}
I just remembered BECSS, which is pretty much that exact thing. Strange
how didn't occur to me at all, though it must have been buried in my
subconscious somewhere
), all the custom JS implementations count for exactly
zero native implementations in UAs, which is what really counts.
--
Lachlan Hunt
http://lachy.id.au/
to a selected resource.
--
Lachlan Hunt
http://lachy.id.au/
at least UTF-8, US-ASCII,
ISO-8859-1 and Windows-1252.
And probably UTF-16 as well.
--
Lachlan Hunt
http://lachy.id.au/
random delays between requests and address any other
security concerns raised.
That way, if the conditions are met by both the script and server, the
UA could allow access to the response, otherwise treat it as an XSS
attack of some sort and deny it.
--
Lachlan Hunt
http://lachy.id.au/
be inserted
into the DOM as an empty element, but UAs should ignore it. UAs may
choose to support it at their own risk, but must not do so by breaking
the DOM like IE does.
--
Lachlan Hunt
http://lachy.id.au/
', authors could get used
to it.
--
Lachlan Hunt
http://lachy.id.au/
to express, I've got no idea what the parameter could be called.
--
Lachlan Hunt
http://lachy.id.au/
a hyphen instead: application/json-request
--
Lachlan Hunt
http://lachy.id.au/
about extending the caption element, currently used
with table, to img, object and embed?
--
Lachlan Hunt
http://lachy.id.au/
=\./\);
/SCRIPT
OBJECT type=text/html data=./
palternate content for when both scripts and the object isn't
supported/p
script
document.write(\/object);/scriptptest/OBJECT/BODY/html
--
Lachlan Hunt
http://lachy.id.au/
. What would happen if you used the Array push() function on the
NodeList?
pNodes.push(newNode);
Where in the DOM would that new node be added?
--
Lachlan Hunt
http://lachy.id.au/
.
--
Lachlan Hunt
http://lachy.id.au/
from that documentation, that actually
doesn't do the same thing as the functions you originally described
because it returns an Element, not a boolean.
[1] http://www.terrainformatica.com/sciter/Element.whtm
--
Lachlan Hunt
http://lachy.id.au/
that potentially differs from the page's encoding?
e.g. if the page were served as text/html;charset=UTF-8 and contained
input type=text accept=text/plain;charset=ISO-8859-1
Then how would that interact with form accept-charset=X?
--
Lachlan Hunt
http://lachy.id.au/
comments like this:
!--[if !IE]--button type=addAdd (!IE)/button!--![endif]--
!--[if IE]button type=submitAdd (IE)/button![endif]--
--
Lachlan Hunt
http://lachy.id.au/
don't know they exist and it's much more
convenient to type regular letters.
--
Lachlan Hunt
http://lachy.id.au/
in the hope of achieving specific behaviour.
--
Lachlan Hunt
http://lachy.id.au/
*is not* presentation, it is UA functionality
and so it does not belong in the presentation layer.
--
Lachlan Hunt
http://lachy.id.au/
Alexey Feldgendler wrote:
On Sun, 11 Jun 2006 21:54:16 +0700, Lachlan Hunt
[EMAIL PROTECTED] wrote:
One can also say that authors should not have explicit control over
whether hyperlinks are underlined or not.
The difference is that underlining is presentation, spell checking
.
--
Lachlan Hunt
http://lachy.id.au/
entering code into a contenteditable section, UAs
should be able to automatically disable spell checking for that content,
while still checking the surrounding text.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=339127#c7
--
Lachlan Hunt
http://lachy.id.au/
)
* pattern
--
Lachlan Hunt
http://lachy.id.au/
Alexey Feldgendler wrote:
On Fri, 23 Jun 2006 10:22:34 +0700, Lachlan Hunt
[EMAIL PROTECTED] wrote:
Roughly what percentage of all use cases would you expect heuristics
and user preferences to give suboptimal results, and thus require the
author's suggestion?
IMHO we should not rely
. The user visits a page with lang=de. Since the user hasn't
indicated that they can understand or write the language, the browser
can default to the user's most preferred language (either en or fr).
In any case, the UA could always offer the user a way to change it at
any time.
--
Lachlan Hunt
. ignoring
elements and attributes in textareas accepting text/html or XML).
--
Lachlan Hunt
http://lachy.id.au/
Matthew Paul Thomas wrote:
On Jun 25, 2006, at 2:02 AM, Lachlan Hunt wrote:
...
However, the proposed spellcheck attribute has one major advantage
over all of those: it's being designed to allow the user to easily
override it if they want to.
But realistically, browsers won't allow the user
implementations have difficulty with re-numbering list items in
linked lists, when a new li is dynamically inserted into a previous list?
--
Lachlan Hunt
http://lachy.id.au/
Matthew Paul Thomas wrote:
On Jun 25, 2006, at 11:59 PM, Lachlan Hunt wrote:
Matthew Paul Thomas wrote:
...
But realistically, browsers won't allow the user to easily override
it if they want to, because any interface for doing that would be
absurd.
...
I'm sure there are other people
Henri Sivonen wrote:
On Jun 27, 2006, at 09:46, Lachlan Hunt wrote:
ol id=part1
...
/ol
ol id=part2 continue=part1
...
/ol
However, there are several issues that would need to be addressed:
Hopefully, the issue list adequately demonstrates that the continue
attribute is way too complicated
support those
events, which would make a JS implementation quite limited.
--
Lachlan Hunt
http://lachy.id.au/
/serialization/Chapter06.html#h1-1715
--
Lachlan Hunt
http://lachy.id.au/
) I think that would cover
every use case for captions.
--
Lachlan Hunt
http://lachy.id.au/
also identify some real use
cases where it is actually useful for authors.
The rev attribute is important for allowing what I call opaque
semantics.
Can you more clearly define what you mean by opaque semantics?
--
Lachlan Hunt
http://lachy.id.au/
.
--
Lachlan Hunt
http://lachy.id.au/
dolphinling wrote:
Lachlan Hunt wrote:
dolphinling wrote:
http://www.w3.org/TR/web-forms-2/#the-autocomplete
| The autocomplete attribute applies to the text, password date-related,
| time-related, numeric, email, and url controls.
There needs to be a comma after password.
And no comma
for XHTML elements.
--
Lachlan Hunt
http://lachy.id.au/
when you consider the
abilities of many authoring tools these days.
--
Lachlan Hunt
http://lachy.id.au/
of an element
doesn't change the way a parser needs to work. Ian's example above is
very similar to some real world examples I've seen and browser's already
handle it just fine.
The DOM looks like this:
A
+-H2
+ P
--
Lachlan Hunt
http://lachy.id.au/
Andrew Fedoniouk wrote:
Lachlan Hunt wrote:
Andrew Fedoniouk wrote:
Ian Hickson wrote:
a href=
h2.../h2
p.../p
/a
If we will change model of A from
!ELEMENT A - - (%inline;)* -(A) -- anchor --
to something else then it will create implications for parser.
What implications
liinsSome list item/ins/li
lidelAnother list item/del/li
/ul
--
Lachlan Hunt
http://lachy.id.au/
Andrew Fedoniouk wrote:
someListElement.select( li:not(li li), foo);
That selector won't work anyway, because (according to the Selectors
spec) :not() can only contain a single simple selector.
--
Lachlan Hunt
http://lachy.id.au/
.
That way, we could use this:
ul
li edit=insertedSome list item/li
li edit=deletedAnother list item/li
li edit=changedModified list item/li
li edit=movedMoved list item/li
/ul
[1] http://www.w3.org/TR/xhtml2/mod-edit.html
--
Lachlan Hunt
http://lachy.id.au/
it be useful to have it saved in HTML?
--
Lachlan Hunt
http://lachy.id.au/
somewhat backwards compatible with current browsers.
--
Lachlan Hunt
http://lachy.id.au/
Lachlan Hunt wrote:
we could introduce the edit and datetime attributes from the XHTML
2.0 draft's Edit Attributes Module [1].
I just realised that the datetime attribute from the Edit module would
clash with the proposed datetime attribute of the t element [1].
e.g. What would the datetime
Francisco Monteiro wrote:
What does tags have to do with the DOM?
We're talking about the DOM that IE produces when given specific markup.
It has everything to do with the DOM!
Exactly, is this thread becoming a Opera marketing ploy?
What the...?
--
Lachlan Hunt
http://lachy.id.au/
was implicitly declaring the
namespace of all Custom Tags in my tests.
[1] http://lachy.id.au/dev/2006/09/custom-tags
--
Lachlan Hunt
http://lachy.id.au/
the same namespace. If we don't resolve the incompatibilities,
one of the specs will simply be doomed to failure.
--
Lachlan Hunt
http://lachy.id.au/
Ian Hickson wrote:
On Mon, 28 Aug 2006, Lachlan Hunt wrote:
dolphinling wrote:
http://www.w3.org/TR/web-forms-2/#the-autocomplete
| The autocomplete attribute applies to the text, password date-related,
| time-related, numeric, email, and url controls.
There needs to be a comma after
text on canvas. This technique has certainly got
many limitations and could never be made as good as a native
implementation, but it works Firefox, Opera and Safari.
http://lachy.id.au/dev/2006/10/canvas-text
--
Lachlan Hunt
http://lachy.id.au/
* rowspan
* colspan
COL and COLGROUP
* span
[1] http://www.w3.org/TR/CSS21/tables.html#q7
--
Lachlan Hunt
http://lachy.id.au/
Anne van Kesteren wrote:
foo
bar/
bar/
/foo
How can foo.innerHTML be well-formed here?
It could be if it were treated as an external parsed entity.
http://www.w3.org/TR/REC-xml/#NT-extParsedEnt
--
Lachlan Hunt
http://lachy.id.au/
of the suggestions
are already included or have at least been discussed, but some a new and
worth looking into.
--
Lachlan Hunt
http://lachy.id.au/
of existing web sites.
--
Lachlan Hunt
http://lachy.id.au/
. However, he's keeping it top secret. There's virtually no
information about it and no way to participate or even keep track of the
work without an invitation.
http://alistapart.com/articles/tohellwithwcag2/#WCAG-documents:WCAGSamurai
http://wcagsamurai.org/
--
Lachlan Hunt
http://lachy.id.au/
Charles Iliya Krempeaux wrote:
http://lachy.id.au/log/2006/10/fixing-html
That link doesn't work. (I get a 404.)
Fixed, thanks. There seems to ge a bug WordPress that causes posts to
get marked as private for some unknown reason.
--
Lachlan Hunt
http://lachy.id.au/
, instead of
MPEG and Quick Time. Aside from the companies who have a stake in
proprietary formats, I'm sure they would like to because they could save
money on licensing fees.
--
Lachlan Hunt
http://lachy.id.au/
Charles Iliya Krempeaux wrote:
On 10/30/06, Lachlan Hunt [EMAIL PROTECTED] wrote:
Places like YouTube and Google Video work around this by
building their own interface using Flash, which handles multiple formats
seamlessly for the user.
Not exactly. Flash players only play FLV video files
successful plugins. Many others that
have failed.
--
Lachlan Hunt
http://lachy.id.au/
could render them as footnotes at the bottom of each page.
--
Lachlan Hunt
http://lachy.id.au/
for confusion about
whether it takes a name or id in this context.
Also, label already supported, so there's fewer backwards
compatibility issues.
--
Lachlan Hunt
http://lachy.id.au/
time soon.
--
Lachlan Hunt
http://lachy.id.au/
| attributes and not the
value of |info| attributes, thus eliminating the need for |info|.
Assuming you meant label group=, that's exactly what I intended in
my examples.
--
Lachlan Hunt
http://lachy.id.au/
Lachlan Hunt wrote:
Ian Hickson wrote:
Joe Clark wrote:
http://blog.fawny.org/2006/10/28/tbl-html/
FYI, my response to that his here.
http://lachy.id.au/log/2006/10/fixing-html
Joe Clark has responed.
http://lachy.id.au/log/2006/10/fixing-html#comment-713
His comment is copied here
James Graham wrote:
Lachlan Hunt wrote:
Abbreviation expansions should only be supplied when they help the
reader to understand the content, not just because the word happens to
be an abbreviation.
I agree, unless using abbr with no title is useful to get the correct
rendering
on the next page and log in
* Disable the Mail Delivery option
2. Send your comments directly to Ian Hickson.
* whatwg at hixie.ch
3. Join the discussion on IRC.
* #whatwg on freenode.
--
Lachlan Hunt
http://lachy.id.au/
different from toSource()?
http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference:Global_Objects:Object:toSource
--
Lachlan Hunt
http://lachy.id.au/
1 - 100 of 328 matches
Mail list logo
