Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
On 11/21/2010 4:12 PM, Robert O'Callahan wrote: On Sun, Nov 21, 2010 at 9:59 AM, Charles Pritchard ch...@jumis.com mailto:ch...@jumis.com wrote: Rob: Mobile deployments using dpiPixelRatio (as has been adopted by Moz and Webkit) and target-DpiDensity work well on the mobile, they

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Robert O'Callahan
On Wed, Nov 24, 2010 at 10:14 PM, Charles Pritchard ch...@jumis.com wrote: window.dpiPixelRatio does not change. Is it mozDpiPixelRatio ? There is no such property. Rob -- Now the Bereans were of more noble character than the Thessalonians, for they received the message with great

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
On 11/24/2010 1:12 AM, Robert O'Callahan wrote: On Wed, Nov 24, 2010 at 9:09 PM, Charles Pritchard ch...@jumis.com mailto:ch...@jumis.com wrote: On 11/21/2010 4:12 PM, Robert O'Callahan wrote: On Sun, Nov 21, 2010 at 9:59 AM, Charles Pritchard ch...@jumis.com

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
Sorry about that, devicePixelRatio On 11/24/2010 1:14 AM, Robert O'Callahan wrote: On Wed, Nov 24, 2010 at 10:14 PM, Charles Pritchard ch...@jumis.com mailto:ch...@jumis.com wrote: window.dpiPixelRatio does not change. Is it mozDpiPixelRatio ? There is no such property. Rob -- Now

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
https://bugzilla.mozilla.org/show_bug.cgi?id=486200 Come on Robert: It needs to be chrome-only because I don't want Web authors to have easy access to information about screen pixels. They'll try to defeat our zooming or size things to screen pixels, which we don't want. They defeat your

[whatwg] Media Fragments URI specification and HTML5: call for review

2010-11-24 Thread Raphaël Troncy
Dear Mike, HTML5, The Media Fragments WG has issued a Last Call WD a couple of month ago and would welcome comments from the HTML WG on its entire specification Media Fragments URI 1.0 located at http://www.w3.org/TR/2010/WD-media-frags-20100408. If you plan to send comments, please let us

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Henri Sivonen
Charles Pritchard wrote: TV use-cases seem like they'll become more prevalent, with Apple and Google and their devices. Apple TV doesn't have legacy connectors--only HDMI. A quick look at the specs of Google TV devices suggests that Google TV devices are also HDMI-only. The devices sold as

Re: [whatwg] Constraint validation feedback (various threads)

2010-11-24 Thread Mounir Lamouri
On 11/16/2010 04:35 PM, Anne van Kesteren wrote: Actually, that specific problem was addressed long ago based on feedback from us: Constraint validation: If an element has a maximum allowed value length, and its dirty value flag is true, and the code-point length of the element's value is

[whatwg] TimedTracks and MPEG transport streams - tracks can change dynamically

2010-11-24 Thread Eric Winkelman
I'm investigating how TimedTracks can be used for in-band-data-tracks within MPEG transport streams (used for cable television). In this format, the number and types of in-band-data-tracks can change over time. So, for example, when the programming switches from a football game to a movie, an

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Boris Zbarsky
On 11/24/10 4:13 AM, Charles Pritchard wrote: And, these aren't great lengths. It's about 6 lines of javascript. Uh... That depends on how your drawing path is set up. If I understand correctly what you're doing, you have to get the DPI ration (call it N), change the canvas width/height by a

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
On 11/24/2010 10:23 AM, Boris Zbarsky wrote: On 11/24/10 4:13 AM, Charles Pritchard wrote: And, these aren't great lengths. It's about 6 lines of javascript. Uh... That depends on how your drawing path is set up. If I understand correctly what you're doing, you have to get the DPI ration

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Boris Zbarsky
On 11/24/10 1:26 PM, Charles Pritchard wrote: But the upshot is that people make mistakes. If you don't assume they will, you come to grief. Assuming they'll make mistakes is different than having zero faith in their competence. I have zero faith in across-the-board competence. That is,

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
On 11/24/2010 10:56 AM, Boris Zbarsky wrote: On 11/24/10 1:26 PM, Charles Pritchard wrote: But the upshot is that people make mistakes. If you don't assume they will, you come to grief. Assuming they'll make mistakes is different than having zero faith in their competence. I have zero faith

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Felix Miata
On 2010/11/24 18:38 (GMT-0800) Charles Pritchard composed: I've only asked that information be made available. The response from your group seems to be you can't handle the truth! As a non-UA developer spectating since the beginning of this thread, my take on what you're asking for is it

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Aryeh Gregor
On Wed, Nov 24, 2010 at 4:38 PM, Charles Pritchard ch...@jumis.com wrote: I greatly appreciate the value of standards, but I am at the same time, very sensitive to the effects that centrally planned restrictions have on groups. The aggregate effect is one where tens of millions are harmed by

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-24 Thread Charles Pritchard
On 11/24/2010 2:45 PM, Aryeh Gregor wrote: On Wed, Nov 24, 2010 at 4:38 PM, Charles Pritchardch...@jumis.com wrote: I greatly appreciate the value of standards, but I am at the same time, very sensitive to the effects that centrally planned restrictions have on groups. The aggregate effect is

Re: [whatwg] need a way to set output format from StreamRecorder

2010-11-24 Thread Silvia Pfeiffer
On Wed, Nov 24, 2010 at 4:24 AM, Anne van Kesteren ann...@opera.com wrote: On Fri, 19 Nov 2010 19:50:42 +0100, Per-Erik Brodin per-erik.bro...@ericsson.com wrote: We are about to start implementing stream.record() and StreamRecorder. The spec currently says that “the file must be in a format

[whatwg] Can we deprecate alert(), confirm(), prompt() ?

2010-11-24 Thread Biju
1. Can we deprecate alert(), confirm(), prompt() ? At present many web2.0 js libs are providing alternate [and cool looking] methods to achieve use cases where we need to use alert(), confirm(), prompt(). So do we need those modal dialogs any longer? 2. if we are still keeping them, can we

Re: [whatwg] Can we deprecate alert(), confirm(), prompt() ?

2010-11-24 Thread Nils Dagsson Moskopp
Biju bijumaill...@gmail.com schrieb am Thu, 25 Nov 2010 02:29:31 -0400: 1. Can we deprecate alert(), confirm(), prompt() ? At present many web2.0 js libs are providing alternate [and cool looking] methods to achieve use cases where we need to use alert(), confirm(), prompt(). So do we need

Re: [whatwg] need a way to set output format from StreamRecorder

2010-11-24 Thread Nils Dagsson Moskopp
Silvia Pfeiffer silviapfeiff...@gmail.com schrieb am Thu, 25 Nov 2010 14:05:18 +1100: Can the decision for a file format be taken completely separately from the codec decision for the audio or video element, I wonder? I believe the royalties for encoders are usually higher than the royalties

Re: [whatwg] Can we deprecate alert(), confirm() , prompt() ?

2010-11-24 Thread a...@ashleysheridan.co.uk
I'm not sure what your definition of web 2.0 is, but its not about the way something looks. Removing those modal dialogues would be a very bad idea indeed. There are still valid uses for them, even if they have been abused in the past. Thinking your way, we ought to get rid of the ability to