Maciej Stachowiak wrote:
I posted the mail below four weeks ago HTML WG's mailing list, hoping
for feedback from Microsoft and Apple. All I got was some off-list
feedback that wasn't really helpful, thus I'm reposting over here
(trying to find out whether people over here are more receptive
On Mon, Jul 21, 2008 at 10:31 PM, Robert (Jamie) Munro wrote:
Keryx Web wrote:
label for=myfieldInstructions
strong class=error Must be a valid value/strong
/label
input id=myfield etc /
But presentationwise it should be displayed like this:
Instructions [ (input) ] Must be a valid
in now days we have different sizes of displays some of them huge with low
resolution and some of them normal but with very tiny dots.
usually the DPI of the development machine is matching the dpi of the VIEWER
but sometimes it doesn't
when progress comes and new displays with higher DPI are
On Tue, 22 Jul 2008, Shimon Doodkin Support wrote:
in now days we have different sizes of displays some of them huge with
low resolution and some of them normal but with very tiny dots. usually
the DPI of the development machine is matching the dpi of the VIEWER but
sometimes it doesn't
On Wed, 9 Jul 2008, Dave Singer wrote:
One of the features proposed for the next version of the video API is
chapter markers and other embedded timed metadata, with corresponding
callbacks for authors to hook into. Would that resolve the problem you
mention?
It may be that if we
On Mon, Jul 21, 2008 at 10:31 PM, Robert (Jamie) Munro wrote:
What's wrong with:
label for=myfieldInstructions/label
input id=myfield etc /
label for=myfield class=error Must be a valid value/label
Can an input not have 2 labels?
Thomas Broyer skrev:
Or even:
labelInstructions input etc
On Tue, 2008-07-22 at 09:58 +, Ian Hickson wrote:
On Wed, 9 Jul 2008, Dave Singer wrote:
On Sat, 12 Jul 2008, Philip Jgenstedt wrote:
Like Dave, I am not terribly enthusiastic about the current cue ranges
spec, which strikes me adding a fair amount of complexity and yet
doesn't
On Tue, Jul 22, 2008 at 1:55 PM, Keryx Web [EMAIL PROTECTED] wrote:
On Mon, Jul 21, 2008 at 10:31 PM, Robert (Jamie) Munro wrote:
What's wrong with:
label for=myfieldInstructions/label
input id=myfield etc /
label for=myfield class=error Must be a valid value/label
Can an input not have
On Tue, Jul 22, 2008 at 6:47 AM, Shannon [EMAIL PROTECTED] wrote:
wait for connection;
receive persistent connection request;
pass request body to service;
response = read from service;
response_length = length of response;
send Content-Length: $response_length;
send $response
close
On Thu, 10 Jul 2008, Philip J�genstedt wrote:
The idea is that if you set the override to a 1:2 ratio, then each
pixel of video data will be rendered 1:2. So you first have to
normalise the width, getting rid of the influence of the official
pixel ratio. No?
I understand what the
On Tue, 22 Jul 2008, Philip J�genstedt wrote:
What are the use cases you think are basic? It's unclear to me what
isn't being solved. Here's one use case, a slide deck:
The most obvious use case in my mind is displaying captions/subtitles.
I'd much, much ratio subtitles were done by
The server must escape all user generated content by replacing with
lt; etc. This is perfectly secure for all existing browsers. The
sandbox instructs the browser to unescape. Completely fail safe for
all.
On 7/22/08, James Ide [EMAIL PROTECTED] wrote:
I'm not sure that I follow - it seems to
On Tue, 2008-07-22 at 21:58 +, Ian Hickson wrote:
On Thu, 10 Jul 2008, Philip Jgenstedt wrote:
I understand what the intention is, but think the terminology is
confusing:
[snip]
I've tried to make the spec generally much more explicit about this.
Please let me know if the spec makes
On Tue, 2008-07-22 at 22:00 +, Ian Hickson wrote:
On Tue, 22 Jul 2008, Philip Jgenstedt wrote:
What are the use cases you think are basic? It's unclear to me what
isn't being solved. Here's one use case, a slide deck:
The most obvious use case in my mind is displaying
14 matches
Mail list logo
