On Mon, Nov 17, 2008 at 11:33 PM, Robert O'Callahan [EMAIL PROTECTED]wrote:
On Tue, Nov 18, 2008 at 7:28 PM, Sander van Zoest [EMAIL PROTECTED]wrote:
By the way, the pixel-aspect-ratio on video caps in the GStreamer
framework has precisely the same meaning as this attribute, overriding
or
something?
If you are going to keep it, how about pixelfloat, as it clearly is not
presented as a ratio. The word display makes me think DAR.
-- Sander
On Wed, Oct 15, 2008 at 8:14 AM, Anne van Kesteren [EMAIL PROTECTED] wrote:
On Wed, 15 Oct 2008 17:01:22 +0200, Sander van Zoest [EMAIL PROTECTED]
wrote:
I hate to say it, but if it was enough, I wouldn't be commenting here. It
simply isn't accurate
enough to store it as a float.
How
On Wed, Oct 15, 2008 at 11:11 AM, Ralph Giles [EMAIL PROTECTED] wrote:
On Wed, Oct 15, 2008 at 2:40 AM, Ian Hickson [EMAIL PROTECTED] wrote:
Is that not enough?
It is enough. Sander and Eduard have provided excellent arguments why
the pixel aspect ratio, and especially the frame rate
On Wed, Oct 15, 2008 at 2:48 PM, Eric Carlson [EMAIL PROTECTED]wrote:
On Oct 15, 2008, at 1:04 PM, Ralph Giles wrote:
On Wed, Oct 15, 2008 at 12:31 PM, Sander van Zoest [EMAIL PROTECTED]
wrote:
Following that logic, why add the attribute at all?
Well, I like the pixelaspect attribute
NTSC --
video pixelratio=59:54 !-- 625 composite PAL --
video pixelratio=1018:1062 !-- 1920x1035 HDTV SMPTE RP 187-1995 --
video parhSpacing=10 parvSpacing=11
Container formats tend to store this information in a ratio like this and
not in a float.
Best,
--
Sander van Zoest
[EMAIL PROTECTED]
San
On Tue, Oct 14, 2008 at 9:39 AM, Sander van Zoest [EMAIL PROTECTED]wrote:
Hi,
I just recently started looking at HTML5 and noticed the video tag. Neat
addition.
I also noticed that it as an attribute named 'pixelratio', however, as you
know this
is never an integer, but rather
aware which frame is the
active one; and the UA will probably hand the active frame's selection to a
script, when the script asks for 'the' selection. (I'm not a javascripter;
this just seems logical to assume.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
a link to a document that is optimized for print, but does it
also trigger the print function?
cheers,
Sander
links that don't require
client-side scripting, an HTML-alternative to javascript:print();
I don't agree with you that printing is an obsolete practice. Not yet at
least, as people not all have mobile access to the internet or in cases
like the example you came up with yourself.
cheers,
Sander
Sander Tekelenburg schreef:
At 07:12 +0200 UTC, on 2007-07-28, Sander wrote:
Well, it can be usefull from a usability point of view to offer this
function from within the web page, for instance: you may want to print
this confirmation, where print is a link that actually prints the page
Stijn Peeters schreef:
Sander schreef:
Křištof Želechovski schreef:
The acronym URL expands to Uniform Resource **Locator**”. The
string “print:#” does not match this spec: it is not a locator, it
is a processing instruction. BTW, the full form of the local URL “#”
can be viewed as “html
At 20:02 +0200 UTC, on 2007-07-28, Sander wrote:
Sander Tekelenburg schreef:
At 07:12 +0200 UTC, on 2007-07-28, Sander wrote:
[...]
incosistency makes things harder to use. A print method that works the same
across web sites is much more usable.
I don't think it's confusing
Sander Tekelenburg schreef:
Your main argument for a print links seemed to be that some people might not
know where to find their UA's print command (hard to believe -- even IE by
default presents a shiny print button always).
Well, Opera doesn't show a print button for instance.
Giving
as it is now. Even with unobtrusive JavaScript I
can not check whether a printer is installed and connected.
cheers,
Sander
At 23:02 +0200 UTC, on 2007-07-28, Sander wrote:
Sander Tekelenburg schreef:
Your main argument for a print links seemed to be that some people might not
know where to find their UA's print command (hard to believe -- even IE by
default presents a shiny print button always).
Well, Opera
Sander Tekelenburg schreef:
So if you'd really want to help those people, you would not
provide a print link. You'd let them figure out how to print, or you could
add a help page that explains how to print a web page (making sure that
you're clear about which specific browsing environment you
the document could be used to only
print that node (#content).
My personal favorite would be the pseudo-protocol as I think this
function is more inline with that of the email link.
cheers,
Sander
-protocol then? If you have no
configurated email client installed on the system you're working on then
that won't work either.
Perhaps a solution would be for user agents that don't have a print
feature to hide these print links or, even better, to provide a way to
print to file.
cheers,
Sander
At 05:23 +0200 UTC, on 2007-07-28, Sander wrote:
[...]
I'd like to see an extension of the hyperlink to give it an HTML-only print
function. Nowadays making a print link available from within a website
always involves client-side scripting.
What is the point of such print links anyway? UAs
Sander Tekelenburg schreef:
What is the point of such print links anyway? UAs already provide their own
built-in print buttons. Just like they provide back buttons. What's the point
of making something that already works the same across different sites, make
more difficult for users by making
='color' would not have that
problem (and probably fallback gracefully in environments that cannot present
a color picker).
All provide their own unique, different UI, which is confusing to users.
Users would benefit from a UI that works the same across sites.
--
Sander Tekelenburg
The Web
as there can be a lot of addresses situated on top of each
other.
cheers,
Sander
At 21:08 +0200 UTC, on 2007-07-14, Sander wrote:
Martin Atkins schreef:
Benjamin Joffe wrote:
[...]
type=color
The user agent would display an appropriate colour picker and would
send a hexidecimal string represting that colour to the server.
I like this idea. It's simple and it's
the last element or the 5th? I guess selecting
the last element can be just as usefull as the furst.
I'm curious, Sander: what is the objection to having both?
It seemed a bit overdone and somewhat arbitrary (why not an option for
selecting the last element?). I think performance is a good
should return all nodes
that have the particular attribute, no matter what its value is.
The method overlaps with both getElementsByClassName,
getElementsByTagName and getElementById, as these filter on attribute
value as well, but it still adds extra opportunities.
cheers,
Sander
Dan Dorman schreef:
On 7/6/07, Sander [EMAIL PROTECTED] wrote:
I haven't read the whole draft yet so maybe it's in there, but can you,
or anyone else, explain why there is both a selectElement and a
selectAllElements method?
I'm no authority, but:
If you know you're after one element, you
;-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Oistein E. Andersen
Sent: Saturday, June 23, 2007 11:28 PM
To: [EMAIL PROTECTED]
Subject: Re: [whatwg] Entity parsing [trema/diaresis vs umlaut]
Sander wrote:
Only the vowel U can have either
Øistein E. Andersen schreef:
French dictionaries require loan-words like angström, führer and länder (plural
of land) to be spelt with an umlaut, but these are of course too rare for
a differentiation tréma/umlaut to have developed, and I would imagine
German imports with umlaut to be only
I hadn't thought of that one ;-) (in Dutch there are no native words
with umlauts, only some of German or Scandinavian descent).
My question was about char-sets that contain both a trema version and a
(seperate) umlaut version of the same character. Are there any?
cheers,
Sander
Kristof
Anne van Kesteren schreef:
On Thu, 07 Jun 2007 21:21:44 +0200, Sander [EMAIL PROTECTED] wrote:
Before HTML5 there was no HTML validation (as opposed to JS
validation) for form controls. So truncating the input value was
probably the only way to force the given maxlength (perhaps that's
also
true or false instead or rename the
attribute to noautocomplete. If it's a backward compatibilty issue then
I suggest both on/off and true/false should be allowed.
cheers,
Sander
option to another? I assume it's
the former, but I just to be sure as selectboxes with change event
handlers are often (ab)used for navigation purposes. So, can anyone
confirm my assumption?
Thanks.
cheers,
Sander
Anne van Kesteren schreef:
On Wed, 06 Jun 2007 12:56:23 +0200, Sander [EMAIL PROTECTED] wrote:
--- minlength ---
I'd like to see a minlength attribute that can be used on the same
elements as the maxlength attribute. ...
Why can't you use pattern= for this?
Maybe I could use
scary.
cheers,
Sander
Thomas Broyer schreef:
2007/6/6, Sander:
But if you can use pattern to define a minimal length, than I'm sure you
can define a minimal length bigger than 0, which makes it required.
No, because Controls with no value selected do not need to match
their pattern. (Although if they are required
already. And I
think I know what the arguments against it are and I believe to
understand the logics underneath them. But it's for the sake of the
authors that I request this feature as I believe that regular
expressions are just too complicated for most of them.
cheers,
Sander
At 16:42 +1200 UTC, on 2007-05-27, Matthew Paul Thomas wrote:
On May 23, 2007, at 2:05 PM, Sander Tekelenburg wrote:
[...]
The argument for using file name extensions is that they can provide a
clue as to what sort of file is being pointed to
[...]
http://urlx.org/google.com/0a8e8
to comprehend.
cheers,
Sander
this is. But I think it would be very valuable,
because it would make it much easier for many people to review the spec,
which would lead to less confusion over what is meant, and thus easier
discussion.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
it?
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
by marking what is obviously not needed by authors. From there it will
get clear how much more detailed this should be done, if it all.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
time marker.../time/di
di
time...time of this reply.../time
dt.../dt
dd.../dd
/di
/dialog
cheers!
Sander
At 00:38 + UTC, on 2007-05-25, Ian Hickson wrote:
On Fri, 25 May 2007, Sander Tekelenburg wrote:
[...]
pIf a codedl/code element contains only codedd/code
elements, then it consists of one group with values but no names,
and the document is non-conforming./p
Should
to continue it. Environment variables tend to change, which can
make the seemingly impossble possible -- unless you've cosed the door.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 09:10 +0100 UTC, on 2007-05-04, Benjamin Hawkes-Lewis wrote:
[...]
keyboard or switch rather than mouse. (I can't work out how to tab
between anchors in iCab
I might be mistaken but I don't think that's currently poissible in iCab.
--
Sander Tekelenburg
The Web Repair Initiative: http
At 01:32 -0700 UTC, on 2007-05-04, Maciej Stachowiak wrote:
On Apr 29, 2007, at 9:21 AM, Sander Tekelenburg wrote:
[...]
FWIW, iCab[*] indicateds such cases by a change of cursor [...]
Safari indicates in the status bar hover feedback when a link will
open in a new window, new frame or new
complicated to me ;)
As to 5, I don't understand what the use is to allow font color. The only
argument I've heard is that apparently today's HTML-PDF converters ignore
CSS. (Well, the affordable ones, that is :))
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 11:01 +1000 UTC, on 2007-05-02, Adrian Sutton wrote:
On 2/5/07 1:28 AM, Sander Tekelenburg [EMAIL PROTECTED] wrote:
[...]
can you explain exactly how span is much more difficult to work
with, and for whom?
Quite a number of the cheap HTML to PDF conversion processes don't support
CSS
authors? Or the users of
EditLive?
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
in them would need
to implement a common communication method. (Which would be very useful, for
example to make it easier to embed conformance checkers. But that's another
story.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
, tying it to
some undefined tool is useless -- at best everyone authoring font will
bother to claim to be a WYSIWG editor.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
hovering over
the link. (You get the same cursor when you Cmd-click or Cmd-Shift-click the
link, to load it in a new window on purpose.) This way you can keep such UA
functionaility in the chrome -- no need to mess with the content's
presentation itself.
[*] http://icab.de/
--
Sander Tekelenburg
is required or
desired, and has no practical drawback if the error is left in (given the
state of HTML email standardisation...).
Given that given that might be the best approach, yes.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
if that were true
Be surpirsed: http://santek.no-ip.org/~st/tests/backslash/
I've no idea how many sites rely on this, but given that Safari copied this
behaviour apparently Apple found the problem big enough to bother.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 09:54 +0200 UTC, on 2007-04-02, Anne van Kesteren wrote:
On Mon, 02 Apr 2007 09:59:50 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
[...]
Surely we're not trying to ensure that a Web page
is presented the same in every browsing environment? What would be the
use of that?
That's
(s).
Agreed.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 12:52 +0200 UTC, on 2007-04-02, Asbjørn Ulsberg wrote:
On Mon, 02 Apr 2007 09:59:50 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
[display: block and inline]
Defining preseantation up to *that* level is no problem IMO.
Great! Then let's.
The current (HTML 4) spec already does so
At 03:18 -0400 UTC, on 2007-04-02, Mike Schinkel wrote:
Sander Tekelenburg wrote:
[...]
What exactly, in the context of presentation, would be good about
consistency
*across* UAs?
See Jakob's Law of Internet User Experience
http://www.useit.com/alertbox/2723.html
I fail to see
-04-02, Mike Schinkel wrote:
Sander Tekelenburg wrote:
[...]
[http://www.whatwg.org/specs/web-apps/current-work/#rendering]
What instead this should say is something like When taken to a fragment
identifier, UAs must clearly indicate the referenced point in the content to
the user. Because
At 19:30 +0200 UTC, on 2007-04-01, Anne van Kesteren wrote:
On Sun, 01 Apr 2007 20:16:12 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
Who are we (as spec definers) to decide that x is the only correct
behaviour or presentation? And why should we want to stifle innovation
by requiring
Web Publishing Systems.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
wrong.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
[My apologies for initially responding off-list. That was unintentional. I'm
posting an updated version.]
At 20:04 + UTC, on 2007-03-21, Martin Atkins wrote:
Sander Tekelenburg wrote:
[...] URL:http://domain.example/movie.ogg#21:08, to mean fetch the
movie and start playing it at 21
At 19:46 + UTC, on 2007-03-22, Nicholas Shanks wrote:
On 22 Mar 2007, at 19:23, Sander Tekelenburg wrote:
[...]
We're not talking about IDs, just fragment identifiers. My point
was that
with video, you could use fragment identifiers *without* the need
for the author to provide IDs.
I
fetch the
data you want, but it doesn't offer the user the benefit of easily being able
to refer to a specific point in any movie (in a video element).
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
such
functionality.
IMO this is no different than CSS being icing on the cake. It's nice to allow
authors to suggest UI-styling and even add functionaility, but it's a mistake
to make basic functinality (start, stop, pause, (fast)forward, etc.)
author-dependant.
--
Sander Tekelenburg
The Web
example (although
requiring users to hover over the video will mean many won't ever discover
this functonality, just like the contextual menu -- I imagine this is what
Apple's Action button aims to solve).
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
, or otherwise
you'd force data to be downloaded by UAs that can't or won't handle it. (I
don't mean the zip file itself, but its content.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
to allow this, but UAs would have to allows users to
override that in favour of the UA's built-in UI. (See also
http://www.euronet.nl/~tekelenb/WWW/LINK/ for the general argument.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
/01requirements.php#req9
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 08:22 + UTC, on 2007-03-06, Benjamin Hawkes-Lewis wrote:
Sander Tekelenburg wrote:
[...]
[http://webrepair.org/02strategy/02certification/01requirements.php#req20]
Well, that makes some sense for block elements, but less for inline
elements.
Agreed.
[...]
it would be good
. But that will result in 'jumpy rendering' because browsers
can't allocate the proper rendering space until the image's dimensions are
known.
[*] http://webrepair.org/02strategy/02certification/01requirements.php Btw,
this is our initial take. We very much welcome community feedback.
--
Sander
to.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
naivity on my part, but that's very
much on purpose ;) Cynicism just stops one from even trying.)
[...]
If you can
make it semantic and pretty, you've got a winner.
Agreed.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
and semantics (perfectly happy with black text on a grey
background) to those who only care about looks. The majority is somewhere
inbetween.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
easier than to
succesfully preach to each and every webdesigner out there... I consider this
shift towards using HTML generators an opportunity to get closer to a
semantically rich and accessible Web.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 14:42 +1300 UTC, on 2007-01-07, Matthew Paul Thomas wrote:
On Jan 7, 2007, at 7:13 AM, Sander Tekelenburg wrote:
[...]
It's still entirely unclear to me *why* the cite attribute needs a
replacement. What is wrong with it?
First, it's hard for UAs to present cite= in a way that is both
format for
hyphenation rules, and browsers would accept such description files as a
plug-in. This would allow each language's specialist to write their rules,
and share them, without putting that burden on browser authors. (Browsers
could of course still be shipped with such rulesets.)
--
Sander
At 02:19 +0100 UTC, on 2007-01-11, Håkon Wium Lie wrote:
Also sprach Sander Tekelenburg:
FWIW, my feeling is that it would be best if there'd be a defined format
for
hyphenation rules, and browsers would accept such description files [...]
This format exists. It was pioneered by TeX
the metadata more visual.
It's still entirely unclear to me *why* the cite attribute needs a
replacement. What is wrong with it?
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
easily recognisable clue
can be added. For instance something like the dotted underline that has
become somewhat common, to indicate title attributes for abbr and acronym.)
--
Sander Tekelenburg, http://www.euronet.nl/~tekelenb/
At 16:26 + UTC, on 2006-12-31, Benjamin Hawkes-Lewis wrote:
Sander Tekelenburg wrote:
[...]
I assumed Anne meant something like:
qrhubarb rhubarb rhubarb/q [citea href=www.example.comNemo,
Works, IV/a/cite]
Ah. Maybe, that's what he meant, yes. But I don't see how this offers any
At 02:37 + UTC, on 2006-12-08, Ian Hickson wrote:
On Fri, 8 Dec 2006, Sander Tekelenburg wrote:
[...]
http://www.whatwg.org/specs/web-apps/current-work/#parsing [...]
The error handling for parse errors is well-defined: user agents must
either act as described below when encountering
. (Especially if you consider more than just HTML. Think of
things like javascript-dependancy, Flash-dependancy, WindowsMedia-depencency,
and even CSS-dependancy.)
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 16:13 + UTC, on 2006-12-08, Simon Pieters wrote:
From: Sander Tekelenburg [EMAIL PROTECTED]
[...] But it still leaves the question whether
every browser will in fact be HTML5 compliant.
They probably won't, at least for the next few years.
Right. That's a window of opportunity
spec, stop processing the document, and have InternetExplorer present
such documents as if they're fine.
What then? Will every other browser really tell the user that it won't try to
interpret what the author might have meant?
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
At 06:30 -0500 UTC, on 2006-12-05, Mike Schinkel wrote:
Sander Tekelenburg wrote:
[...]
The tools need to be standard and compatible.
I can't follow this. In what sense? Tidy is Tidy.
AWPS authors can incorporate it into their product.
What standard or compatibility plays a role here
At 01:22 + UTC, on 2006-12-08, Ian Hickson wrote:
On Thu, 7 Dec 2006, Sander Tekelenburg wrote:
At 00:45 + UTC, on 2006-12-05, Ian Hickson wrote:
[...]
I'm still somewhat sceptical about the reality of this though, as it relies
on the author checking the document with at least one
[I unintentionally sent my previous message off-list. Sorry about that. Am
moving this back to the list again. As there's nothing personal in it, I
assume that's OK.]
At 18:37 + UTC, on 2006-12-04, Ian Hickson wrote:
On Mon, 4 Dec 2006, Sander Tekelenburg wrote:
[...]
[smiley
At 20:46 + UTC, on 2006-12-04, Ian Hickson wrote:
On Mon, 4 Dec 2006, Sander Tekelenburg wrote:
[...]
[ESP engines]
Surely you're not saying that HTML5 will define error handling for every
possible case a UA may run into?
Yes. In fact, not only will it define this, it already _does_
this option is not very likely to produce good
results.
--
Sander Tekelenburg
The Web Repair Initiative: http://webrepair.org/
.)
--
Sander Tekelenburg, http://www.euronet.nl/~tekelenb/
--
Sander Tekelenburg, http://www.euronet.nl/~tekelenb/
At 17:54 +0100 UTC, on 2006-08-24, James Graham wrote:
Sander Tekelenburg wrote:
A good implementation would
[...]
A much simpler implementation would simply work like existing form autofill,
matching values the values that the user has supplied to other country
inputs in
the past without
the functionality of the page, then
that's bad.
Agreed.
[...]
On Thu, 15 Jun 2006, Sander Tekelenburg wrote:
[...] Just like authors cannot know what font size is
best for a user they cannot know whether a spellchecker is useful or a
nuisance.
But they can suggest what font-size might
out in
a HTML spec.
[*] http://www.newsreaders.com/gnksa/
--
Sander Tekelenburg, http://www.euronet.nl/~tekelenb/
has been submitted. Thus by allowing authors
to state that a spellchecker must be on, you could end up in a stupid 'loop'
when the spellchecker guides the user to do one thing, and the server wants
another thing.)
--
Sander Tekelenburg, http://www.euronet.nl/~tekelenb/
At 09:12 -0500 UTC, on 2006-01-17, Matthew Raymond wrote:
Sander Tekelenburg wrote:
At 15:26 -0500 UTC, on 2006-01-10, Matthew Raymond wrote:
[...]
So what you're saying is that display: meta will basically mean
not presented in the body.
Well, in the sense that in most browsing
1 - 100 of 104 matches
Mail list logo
