Re: [whatwg] Proposal: target="_tab"

2008/6/13 Borek Bernard <[EMAIL PROTECTED]>: > Hi João, > > you're right that everything important has been already said. I > have withdrawn this proposal because it has been pointed out that it > is not backwards compatible and the correct solution will be part of > CSS3 anyway (which is much more

Re: [whatwg] Proposal: target="_tab"

I've been following this discussion for a while and I agree a new '_tab' target is not necessary. To my mind _blank implies a new browser canvas. There are two implementations for creating a new canvas these days; a new window, or a new tab. The key question is: what does _blank mean? Does

Re: [whatwg] Text APIs on

On Thu, 8 May 2008, Mathieu HENRI wrote: > > > > The idea is that only scalable (vector) fonts should be used, since > > otherwise things will quickly look ugly. I've made the spec require > > this. > > > > Going forward the spec is likely to require effects such as adding > > text to paths, w

Re: [whatwg] createImageData

On Jun 9, 2008, at 8:25 PM, Jonas Sicking wrote: Vladimir Vukicevic wrote: Sorry it took me a bit to respond here... so, ok, based on the discussion, I'd suggest: - user-created ImageData-like objects should be supported, e.g. with language such as: Do note that dealing with user-created

[whatwg] Fwd: nav Element

To the correct list this time... -- Forwarded message -- From: Jorge Bay Gondra <[EMAIL PROTECTED]> Date: 2008/6/12 Subject: nav Element To: [EMAIL PROTECTED] Hi to all, About the nav element: I was trying to imaging how it would be to build a site, and I realized that, in the ca

Re: [whatwg] [canvas] imageRenderingQuality property

On Thu, 12 Jun 2008, Robert O'Callahan wrote: > On Wed, Jun 11, 2008 at 10:34 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: > > > Why not just have the UA run in a high quality mode the first time it > > is painted on, but if the script tries to paint again within a certain > > amount of time, swit

Re: [whatwg] are relative values of CanvasRenderingContext2D.font live to style changes?

On Thu, 12 Jun 2008, L. David Baron wrote: > > I'm looking at > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas.html#text > which currently says: > # When the 'font-size' component is set to lengths using > # percentages, 'em' or 'ex' units, or the 'larger' or 'smaller' >

Re: [whatwg] Some media element details

The _function_ performed by the play/pause button is reciprocally correlated; OTOH, its _interactivity_ (whether enabled) can be related to playback state. Not that I like this overprotective design. HTH, Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf

Re: [whatwg] Interpretation of video poster attribute

On Thu, 12 Jun 2008, Philip J�genstedt wrote: > > src="video_of_unknown_but_same_dimension"> > > This is a probable and reasonable scenario, but currently it's > impossible to use a poster image without knowing its dimensions. It's not impossible; first black would render 300x150, then the pos

Re: [whatwg] Fwd: nav Element

Jorge Bay Gondra wrote: To the correct list this time... -- Forwarded message -- From: Jorge Bay Gondra <[EMAIL PROTECTED]> Date: 2008/6/12 Subject: nav Element To: [EMAIL PROTECTED] Hi to all, About the nav element: I was trying to imaging how it would be to build a site, and

[whatwg] video background color (Was: Interpretation of video poster attribute)

The issue with the poster attribute is resolved, but one comment made me remember something I've wondered about: On Fri, 2008-06-13 at 09:26 +, Ian Hickson wrote: > It's not impossible; first black would render 300x150, then the poster The spec says: Areas of the element's playback area tha

Re: [whatwg] video background color

On Fri, 13 Jun 2008 13:42:28 +0200, Philip Jägenstedt <[EMAIL PROTECTED]> wrote: On Fri, 2008-06-13 at 09:26 +, Ian Hickson wrote: It's not impossible; first black would render 300x150, then the poster The spec says: Areas of the element's playback area that do not contain the video repr

Re: [whatwg] video background color (Was: Interpretation of video poster attribute)

On Fri, 13 Jun 2008, Philip J�genstedt wrote: > > The issue with the poster attribute is resolved, but one comment made me > remember something I've wondered about: > > On Fri, 2008-06-13 at 09:26 +, Ian Hickson wrote: > > > It's not impossible; first black would render 300x150, then the pos

Re: [whatwg] Opportunistic caching

Ian Hickson wrote: On Tue, 10 Jun 2008, Honza Bambas wrote: Hi, I would like to ask for clarification of opportunistic caching spec in Offline Web Applications, the article 4.9.1.9. Adding a resource whom URI matches an opportunistic name space seems to be done only for top level documents

[whatwg] Use of 'direction' of canvas element

http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas.html#text has the following bullet point: # Form a hypothetical infinitely wide CSS line box containing a # single inline box containing the text text, with all the # properties at their initial values except the 'font' pr

[whatwg] A document's cookie context

The current draft of the spec doesn't specify how to compute the cookie context for a document. Here is how to compute it: A document's cookie context can be represented as a URI and largely (but not exactly) follows the document's origin. 1) If the document does not have a browsing context (e.g

[whatwg] document.open() and security context

The current description of document.open(), at doesn't mention the method's effect on the document's security context. The document.open() method replaces the document's security context with the security context of the currently executing