Referer to remove
the relative URI thing, since, to my knowledge at least, nobody uses it.
The other is that we can define the magic value to be #PING instead,
since that's a non-conforming Referer value right now.
Would that work for people? dolphinling? Darin?
If (X-)Ping-From/Ping
that there may be other ways of blocking this attack vector, but the
question here is whether the referer is needed, as it doesn't seem to make any
new legitimate things possible, and would help in this case (and perhaps
others--e.g. privacy).
--
dolphinling
http://dolphinling.net/
!
--
dolphinling
http://dolphinling.net/
in 8px Monaco on a canvas, and
do the same thing in a span, the span will have the same size as the
canvas version. But that seems to make sense to me.)
What if the canvas and span are surrounded by something with font-weight:bold?
Will the text in the canvas be drawn bold, too?
--
dolphinling
namespace syntax shouldn't be added to HTML?
--
dolphinling
http://dolphinling.net/
to everything.
(Note that I haven't thought about it much, though, and I do have a vague hazy
memory of not liking something about the way XHTML 2 is doing it. I would
definitely want more thought put into it than I have.)
--
dolphinling
http://dolphinling.net/
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.
--
dolphinling
http://dolphinling.net/
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 after email
Anne van Kesteren wrote:
Quoting dolphinling [EMAIL PROTECTED]:
All the links to the IETF website in the references section are broken.
It looks like they're just missing extensions. Is this a temporary bug
in their site, a permanent change, or has it always been that way?
Why don't you ask
All the links to the IETF website in the references section are broken.
It looks like they're just missing extensions. Is this a temporary bug
in their site, a permanent change, or has it always been that way?
--
dolphinling
http://dolphinling.net/
?
--
dolphinling
http://dolphinling.net/
dolphinling wrote:
HTML5 brings back the |start| attribute on ordered lists. This allows a
list to semantically start with a number other than one. It seems like
the major use case for this is to split lists up, so that a single list
is marked by multiple ols.
Would it therefore make sense
dolphinling wrote:
As for how this would interact with CSS Counters... It appears counters
in CSS 3 are insufficient even to handle the already-in-spec start= and
value= attributes. That should probably be taken up with the CSS WG.
I've mailed www-style (not with any ideas, just bringing
own.
--
dolphinling
http://dolphinling.net/
Mihai Sucan wrote:
Le Tue, 27 Jun 2006 13:00:21 +0300, dolphinling [EMAIL PROTECTED]
a écrit:
fantasai wrote:
I'm wondering what WA1 considers appropriate markup for
a figure with a caption.
~fantasai
What's wrong with
div
img src=
pThis is the caption./p
/div
? That's how I think
all that be an abuse, and something that's one list should use
only one ?l ?
--
dolphinling
http://dolphinling.net/
implementatino
--
dolphinling
http://dolphinling.net/
like the difference
between blue and #aa
* Actually, it should probably be input type=select and input
type=multiselect. But again, backwards comaptibility.
--
dolphinling
http://dolphinling.net/
, it *is* HTML 4).
--
dolphinling
http://dolphinling.net/
dolphinling wrote:
What do current UAs do with known non-option elements and
unknown elements in select?
Replying to myself, it seems that Firefox trunk ignores all three of
text not in any element, text in a known non-option element, and text in
an unknown element, when served as text/html
browsers? Are there small differences needed because
what's being parsed is a document fragment instead of a document? And
when it's re-serialized, how closely will today's browsers interpret the
original and the new?
--
dolphinling
http://dolphinling.net/
=002_email value=[EMAIL PROTECTED]
...and when the user changes jane doe to janet doe, you get
001_name=janet doe
...? Then all you need to do is update the 001_name.
--
dolphinling
http://dolphinling.net/
, and
would read the content as-is, likely confusing the user.
--
dolphinling
http://dolphinling.net/
Ian Hickson wrote:
On Sun, 5 Feb 2006, dolphinling wrote:
Actually, the javascript solution would be _superior_ to the XBL one in
this case. The screenreader wouldn't pick up on the XBL at all, and
would read the content as-is, likely confusing the user.
Um, there's no reason an aural
Henri Sivonen wrote:
On Jan 23, 2006, at 18:43, dolphinling wrote:
Second, it could force authoring tools to produce invalid documents
if the author did not provide any alt text. However, those documents
would be non-conformant anyway, so this is not a huge problem.
It is. Authoring
so the template attributes only apply to
fieldsets and wherever else they need to because of current parsing, as
opposed to all elements?
I believe this would mean it applied to fieldset, tr, and li (and
perhaps td, though that would be a strange thing to do).
--
dolphinling
http
Anne van Kesteren wrote:
Quoting dolphinling [EMAIL PROTECTED]:
Okay, it still bugs me that template attributes apply to all elements
when I think they should only apply to fieldsets. I do realize though
that because of backwards compatibility and because in current
browsers there are places
in it).
...
But there is already a better idea: redirects. As dolphinling said,
redirects will work while ping= doesn't. And the script you provided to
get around that not only adds even more complexity, it also won't work
for the 10 percent of visitors who don't have JavaScript turned on,
while redirects still work
Kind regards,
Anne
FWIW, I agree.
--
dolphinling
http://dolphinling.net/
, and the person chose to do X, the license agreement would be
disabled.
--
dolphinling
http://dolphinling.net/
for being 3 months late to the discussion. I'm 600 mails
behind now, trying to catch up. Also sorry if this thread has come up
elsewhere, I didn't see it in the subjects.
--
dolphinling
http://dolphinling.net/
Ian Hickson wrote:
On Thu, 14 Jul 2005, dolphinling wrote:
Other elements that I could see being nested inside a paragraph are:
* ol
* ul
* dl
It's been said that no one will use these except people who write about
this kind of thing on their weblogs.
Note that people who write
support gif/jpg/png in OBJECT? If not, allow it in both for
backwards compatablity. I agree, though, it should be focused on OBJECT.
--
dolphinling
http://dolphinling.net/
something here? What semantics does canvas have?
--
dolphinling
http://dolphinling.net/
34 matches
Mail list logo
