Re: [whatwg] Change request: rules for pixel ratio

2008-06-11 Thread Philip Jägenstedt
On Tue, 2008-06-10 at 10:48 -0700, Ralph Giles wrote: Does this mean the implementation must retrieve the self-described pixel aspect ratio from the stream and supply it as part of the DOM? Yes, the implementation would read the pixel ratio from the video stream. In libtheora this is

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Borek Bernard
Hi Adrian, That is actually a very good point, I missed that. In fact, it means that _tab should not be part of HTML spec because it would possibly make things even worse than they currently are (opening GReader links in new _tabs in old browsers would lead to losing the opened articles) . I

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Kristof Zelechovski
Once you have support in CSS, you can use DOM+CSS from JS. No particular support within JS is required. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Borek Bernard Sent: Wednesday, June 11, 2008 10:37 AM To: Ian Hickson; whatwg@lists.whatwg.org

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Jens Meiert
In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that authors should have the ability to suggest that links open in new windows and new tabs. The suggested solution is to introduce a new browsing context keyword _tab. In general, it's best to let users decide where the link

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Borek Bernard
Hi Kristof, my knowledge of JS is limited but how would you handle this situation: in your web app, you want to provide a keyboard shortcut for opening current item into a new tab. You need to invoke this action from JavaScript so setting CSS to some DOM element is not enough (AFAIK). I think

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Ian Hickson
On Wed, 11 Jun 2008, Jens Meiert wrote: In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that authors should have the ability to suggest that links open in new windows and new tabs. The suggested solution is to introduce a new browsing context keyword _tab. In

[whatwg] ImageData feedback

2008-06-11 Thread Ian Hickson
On Tue, 19 Feb 2008, Oliver Hunt wrote: The first is relatively simple, 3.14.11.1.10 states If any of the arguments to createImageData() or getImageData() are infinite or NaN, or if either the sw or sh arguments are zero, the method must instead raise an INDEX_SIZE_ERR exception. I feel

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Jens Meiert
What is interesting though is that authors can let open new windows/tabs by HTML, CSS, /and/ scripting. I am not sure if this functionality, that may ultimately impede user experience, can really be considered structural, presentational, /and/ behavioral. I have no idea what you mean or

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Ian Hickson
On Wed, 11 Jun 2008, Jens Meiert wrote: What is interesting though is that authors can let open new windows/tabs by HTML, CSS, /and/ scripting. I am not sure if this functionality, that may ultimately impede user experience, can really be considered structural, presentational,

Re: [whatwg] [canvas] imageRenderingQuality property

2008-06-11 Thread Ian Hickson
On Mon, 2 Jun 2008, Vladimir Vukicevic wrote: I'd like to propose adding an imageRenderingQuality property on the canvas 2D context to allow authors to choose speed vs. quality when rendering images (especially transformed ones). How can an author know which is appropriate? This is

Re: [whatwg] [WF2] |min| and |max| number of selected |option|s

2008-06-11 Thread Lachlan Hunt
Christoph Päper wrote: Dear WHAT WG When using input type=checkbox or select multiple one somtimes wants to limit the number of selected check boxes or options. Could you provide some examples of some sites that need to apply such limits, and show how people are currently achieving

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Kristof Zelechovski
You can use A.click instead of window.open. I have ignored the keyboard shortcut requirement because it is irrelevant. I agree that modifying window.open to support tabs would be more consistent; I just wanted to make you realize that neither is it strictly necessary nor does it require any

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread João Eiras
As mentioned multiple times, that up to the user agent, or browser if you prefer, to control. Users with browsers with tabbed interface want tabs and that it. Leaving such usability in control of a webpage is bad. All browser that support tabs allow the user to choose if they want the

Re: [whatwg] Proposal: target=_tab

2008-06-11 Thread Kristof Zelechovski
For the record: I do not advocate the original recommendation; I only hypothesized about what can be achieved with CSS instead. I never recommended actually doing it. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joao Eiras Sent: Wednesday, June

Re: [whatwg] [canvas] imageRenderingQuality property

2008-06-11 Thread Robert O'Callahan
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, switch to high speed? This makes sense. However, there is still

Re: [whatwg] Some media element details

2008-06-11 Thread Ian Hickson
On Fri, 16 May 2008, Antti Koivisto wrote: [It would be nice to have a read-only attribute (called playing for example) that would be true when the element is actively playing. Knowing if the playback is progressing is necessary for implementing basic playback UIs with JS. It is clumsy

Re: [whatwg] Some media element details

2008-06-11 Thread Ian Hickson
On Fri, 16 May 2008, James Justin Harrell wrote: The current HTMLMediaElement interface is inconsistent and is designed in such a way that making changes to it will be extremely difficult. The network state is given by the networkState attribute, and is one of: EMPTY, LOADING,

Re: [whatwg] Some media element details

2008-06-11 Thread Ian Hickson
On Fri, 23 May 2008, Bonner, Matt (IPG) wrote: Knowing if the playback is progressing is necessary for implementing basic playback UIs with JS. It is clumsy and not very obvious that you need to do var playing = !video.paused !video.ended video.readyState =

Re: [whatwg] ***DHSPAM*** re-thinking cue ranges

2008-06-11 Thread Ian Hickson
On Thu, 22 May 2008, Dave Singer wrote: WARNING: this email is sent to both the WhatWG and W3C Public HTML list, as it is a proposal. Please be careful about where you reply/follow-up to. The editors may have a preference (and if they do, I hope they express it). My preference is to