Re: [whatwg] Forcing orientation in content

On Fri, Jul 12, 2013 at 10:25 PM, Jonas Sicking wrote: > If the content is sized better for portrait or landscape, then it's > generally good for the user if the mode is forced by the application. > Otherwise the user will have to scroll, or will see content that is > smaller than it otherwise wo

Re: [whatwg] Forcing orientation in content

On Fri, Jul 12, 2013 at 12:45 PM, Ian Hickson wrote: > On Thu, 18 Apr 2013, David Bruant wrote: >> >> Currently working on a web project where tablet support (iPad >> especially) is important, I'm facing a need which apparently the >> platform doesn't support. I would need to lock the screen in la

Re: [whatwg] scrdoc and session history don't play along in the spec

On Fri, Jul 12, 2013 at 1:09 PM, Boris Zbarsky wrote: > On 7/12/13 3:39 PM, Ian Hickson wrote: >> That wasn't the intent. I've tried to clarify it. > > Hmm. It might help to make it clearer in > http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#navigate > that "new resource

Re: [whatwg] Forcing orientation in content

On Fri, Jul 12, 2013 at 2:45 PM, Ian Hickson wrote: > Why? As a user on desktop, I can resize my window however I want, to be > landscape or portrait. Why wouldn't I be allowed to do the same on any > other device? > In mobile accelerometer/gyro-based games, you don't want the user's shifting th

Re: [whatwg] HTML: A DOM attribute that returns the language of a node

Well, my true hope is that such a DOM attribute like "language" will be specified in the HTML or DOM spec. Especially since it's not currently possible to get the language of a node through JavaScript methods alone. See [1] and its replies. --Peter [1]: http://lists.w3.org/Archives/Public/pu

Re: [whatwg] Forcing orientation in content

On Fri, 12 Jul 2013, Peter Occil wrote: > > One use case I can think of is games. For instance, there are several > games for Android that run the game in a particular orientation, such as > Jewels Deluxe, Shoot the Apple, and similar puzzle and casual games. > > I can't speak for why that's th

Re: [whatwg] Forcing orientation in content

One use case I can think of is games. For instance, there are several games for Android that run the game in a particular orientation, such as Jewels Deluxe, Shoot the Apple, and similar puzzle and casual games. I can't speak for why that's the case exactly, but I believe it's for at least on

Re: [whatwg] Stack trace in window.onerror

On Fri, Jul 12, 2013 at 5:51 PM, Garrett Smith wrote: > On 7/12/13, James Greene wrote: > > Ian — > > Hi James - > > I've interleaved, combined with your top post below. > > > I'm curious: would do you say that? All evergreen browsers already > include > > a `stack` property on their core `Error

Re: [whatwg] Stack trace in window.onerror

On 7/12/13, James Greene wrote: > Ian — Hi James - I've interleaved, combined with your top post below. > I'm curious: would do you say that? All evergreen browsers already include > a `stack` property on their core `Error` prototypes, so it seems to me that > the only thing preventing us from

Re: [whatwg] Forms-related feedback

On Wed, 9 Jan 2013, TAMURA, Kent wrote: > On Wed, Nov 21, 2012 at 7:51 AM, Ian Hickson wrote: > > On Fri, 7 Sep 2012, TAMURA, Kent wrote: > > > > > > * For date, datetime, datetime-local, month, time, week, the > > > attribute returns a string in a field. If a field is text-editable, > > > it sh

Re: [whatwg] Inert nodes and element.click()

On Thu, 23 May 2013, Matt Falkenhagen wrote: > > I have some questions about these concepts. > > 1. For an inert element, what happens on element.click() or > element.dispatchEvent(new Event('click'))? The spec says an inert node > is treated as absent "for the purposes of targeting user interac

Re: [whatwg] Reorganizing and fixing "origin"

On Wed, 22 May 2013, Anne van Kesteren wrote: > > As Bj?rn points out in > http://www.ietf.org/mail-archive/web/websec/current/msg01512.html > defining origin of a URL in terms of STD66 is broken. So we should > define it in terms of the URL Standard. > > The Origin header also has problems, as

Re: [whatwg] Script preloading

(being as brief as I possibly can...) > As per the existing outline, I don't see how it could have any "sensitivity". So, just to clarify, `

Re: [whatwg] Alignment of empty buttons

On 7/12/13 4:08 PM, Ian Hickson wrote: The HTML spec is pretty explicit about it not being: # When the button binding applies to a button element, the element is # expected to render as an 'inline-block' box rendered as a button whose # contents are the contents of the element. -- http://www.w

Re: [whatwg] scrdoc and session history don't play along in the spec

On 7/12/13 3:39 PM, Ian Hickson wrote: > That wasn't the intent. I've tried to clarify it. Hmm. It might help to make it clearer in http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#navigate that "new resource" does not mean "URL". Maybe have some explicit thing that r

Re: [whatwg] Alignment of empty buttons

On Fri, 3 May 2013, Boris Zbarsky wrote: > On 5/3/13 7:07 PM, Christian Biesinger wrote: > > fantasai pointed out that CSS does specify this: > > "If the box does not have a baseline, align the bottom margin edge > > with the parent's baseline." > > (http://www.w3.org/TR/CSS2/visudet.html#propdef-v

Re: [whatwg] Script preloading

On Fri, Jul 12, 2013 at 7:56 PM, Kyle Simpson wrote: [ snip ] > Again: my question (which remains unanswered), & the reason I stated the > error/retry/fallback use case in detail, is whether or not the dependency > attributes proposal, as put forth by Jake (and Ian) will or will not, > factuall

Re: [whatwg] HTML: A DOM attribute that returns the language of a node

On Wed, 24 Apr 2013, Peter Occil wrote: > > Well in my case, I have written an HTML parser in Java and C# [1][2], > which parses HTML documents and returns an object that implements a > subset of the DOM, so far. As far as possible, I included only methods > and attributes that were specified

Re: [whatwg] Forcing orientation in content

On Thu, 18 Apr 2013, David Bruant wrote: > > Currently working on a web project where tablet support (iPad > especially) is important, I'm facing a need which apparently the > platform doesn't support. I would need to lock the screen in landscape > mode. Why? As a user on desktop, I can resize

Re: [whatwg] scrdoc and session history don't play along in the spec

On Fri, 5 Apr 2013, Boris Zbarsky wrote: > > The session history algorithm in the spec navigates to urls. That wasn't the intent. I've tried to clarify it. > As far as I can tell, on the face of it, this means that this testcase: > > > http://web.mit.edu";> > Click me, then later hit b

Re: [whatwg] Proposal: Add window.getLastError (or modify invocation arguments of window.onerror)

I'd love that! Perhaps similar to what Node.js did with their `uncaughtException` event ? Sincerely, James Greene On Fri, Jul 12, 2013 at 1:40 PM, Elliott Sprehn wrote: > Can we just add a new event that takes an event obj

Re: [whatwg] img loading events - can load & error fire for the same image?

On Fri, 5 Apr 2013, Jake Archibald wrote: > > Been reading the steps for image downloading - > http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html#update-the-image-data > > As far as I can tell: > > Step 12 "If selected source is null" is the only step where an "er

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

On Fri, Jul 12, 2013 at 2:50 PM, Boris Zbarsky wrote: > If nothing else because that seems user-hostile (both to web developers > examining location values and users who are shown document.URL or > location.href in web pages). But then we shouldn't garble pathname either and we do because we have

Re: [whatwg] Script preloading

> (AT EYE-WATERING-LENGTH) I'm sorry I'm too verbose on the list for everyone's taste. Every time I'm brief and make assumptions, I get accusations like Jake's repeated ones that I'm just "asserting without reason". FWIW, my exhaustion of this process is not about my eyes, but my fingers sure

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

On 7/12/13 2:40 PM, Adam Barth wrote: Why not change Firefox to use punycode in window.location? If nothing else because that seems user-hostile (both to web developers examining location values and users who are shown document.URL or location.href in web pages). -Boris

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

On Fri, Jul 12, 2013 at 11:35 AM, Boris Zbarsky wrote: > On 7/12/13 2:15 PM, Ian Hickson wrote: >> What's not useful about the way it's defined? It's set to a specific >> string. > > I couldn't find where it was normatively set to anything. > >>> In cases when the hostname is non-ASCII, the Refere

Re: [whatwg] Proposal: Add window.getLastError (or modify invocation arguments of window.onerror)

Can we just add a new event that takes an event object instead of a huge list of arguments? :) On Fri, Jul 12, 2013 at 11:30 AM, James Greene wrote: > I'd rather get an Error-like duck-typed object with this shell info for > cross-domain requests than to not get a real Error object when the > un

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

On 7/12/13 2:15 PM, Ian Hickson wrote: What's not useful about the way it's defined? It's set to a specific string. I couldn't find where it was normatively set to anything. In cases when the hostname is non-ASCII, the Referer header will have it encoded in punycode. Is that defined anywher

Re: [whatwg] Proposal: Add window.getLastError (or modify invocation arguments of window.onerror)

I'd rather get an Error-like duck-typed object with this shell info for cross-domain requests than to not get a real Error object when the unhandled error *is* from the same origin. Adding the trace as another new argument to `window.onerror` is certainly an option but the parameter list is gettin

Re: [whatwg] Stack trace in window.onerror

Ian — I'm curious: would do you say that? All evergreen browsers already include a `stack` property on their core `Error` prototypes, so it seems to me that the only thing preventing us from getting that useful information for unhandled errors is the fact that `window.onerror` does not provide us

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

On Wed, 20 Mar 2013, Boris Zbarsky wrote: > > The spec for document.referrer says: > > The referrer attribute must return the document's referrer. > > The "document's referrer" is not really defined anywhere in a useful way > that I can find. What's not useful about the way it's defined? It's

Re: [whatwg] Script preloading

On Fri, Jul 12, 2013 at 4:31 PM, Kyle Simpson wrote: > > Ok, and I'm saying they shouldn't be asking LABjs to handle it, they > should be asking the devtools teams at browser vendors to give them ways to > deal with it. You're not going to be able to pause execution for code, > implement future b

Re: [whatwg] Why are we merging Document and HTMLDocument again?

On 7/12/13 1:57 PM, Ian Hickson wrote: Having not heard any interest from anyone else, I haven't done anything. That's because other UAs are just silently ignoring the spec as currently written, for the most part... -Boris

Re: [whatwg] Schemes for registerProtocolHandler

On Mon, 11 Mar 2013, Simon Pieters wrote: > > While looking at our testsuite for register*Handler I noticed that we > seem to support some schemes that are not in the spec: > > im ("works like xmpp" says wikipedia) > ircs (secure equivalent of irc) > wtai (apparently prompts the user what to do w

Re: [whatwg] Why are we merging Document and HTMLDocument again?

On Thu, 14 Mar 2013, Anne van Kesteren wrote: > On Tue, Mar 5, 2013 at 8:42 PM, Boris Zbarsky wrote: > > On 3/5/13 3:30 PM, Ian Hickson wrote: > >> I'd be fine with having a Document descendant that is used for > >> Documents that have global scopes / browsing contexts / the works, > >> and one

Re: [whatwg] supporting HTMLElement.dataset on SVG elements

On Fri, Jul 12, 2013 at 10:40 AM, David Carlisle wrote: > For SVG are you considering allowing data-* always or just in svg-in-html? SVG is going to (or maybe already has?) added the data-* attributes to SVG elements. ~TJ

Re: [whatwg] supporting HTMLElement.dataset on SVG elements

On 12/07/2013 18:21, Ian Hickson wrote: On Wed, 6 Feb 2013, Cameron McCormack wrote: As part of aligning SVG with some not-so-HTML-specific features of HTML, the SVG WG would like to support data-* attributes on SVG elements. In mixed HTML/SVG documents, it seems like you would want to be able

Re: [whatwg] Canonical Image and Color

On Mon, 11 Feb 2013, Brian Blakely wrote: > > Meta elements for defining a canonical image and color to be associated > with the page(s) in which they are included. This is intended for use > by user agents and third-party applications (such as social networks), > referred to collectively as "

Re: [whatwg] HTML Specification update request: bug 20939

On Sat, 9 Feb 2013, Bob Owen wrote: > > While discussing with Boris Zbarsky, some work I am doing on sandboxing > for Mozilla, we realised that the sections in the HTML specification on > browsing context security and browsing context names, could do with some > clarification with regard to the

Re: [whatwg] A question about portrait-secondary of screen orientation

Will do so. Thanks! From Windows Phone From: Ian Hickson Sent: ‎2013/‎7/‎12 10:26 To: Chundong Wang Cc: whatwg@lists.whatwg.org Subject: Re: [whatwg] A question about portrait-seco

Re: [whatwg] A question about portrait-secondary of screen orientation

On Fri, 8 Feb 2013, Chundong Wang wrote: > > Hello - Got a question of screen orientation on portrait/landscape. > > Let's say we have a device doesn't support portrait-secondary, by > spec we should remove it from > allow list which is fine. However if

Re: [whatwg] supporting HTMLElement.dataset on SVG elements

On Wed, 6 Feb 2013, Cameron McCormack wrote: > > As part of aligning SVG with some not-so-HTML-specific features of HTML, > the SVG WG would like to support data-* attributes on SVG elements. In > mixed HTML/SVG documents, it seems like you would want to be able to use > these attributes regard

[whatwg] Stack trace in window.onerror

On Tue, 5 Feb 2013, Nathan Broadbent wrote: > > The current information passed to window.onerror rarely provides > sufficient information to find the cause of the error. The column number > argument will be a big step forward, but a stack trace would be > especially useful. I would like to add

Re: [whatwg] Reporting errors during Web Worker startup

On Wed, 9 Jan 2013, Kenneth Russell wrote: > > http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#creating-workers > > doesn't seem to define what happens if there aren't enough resources to > create a separate parallel execution environment. User agents may impose impleme

Re: [whatwg] Baseline of objects

bz wrote: > On 12/28/12 1:42 PM, Jonas Grus Dinesen wrote: > > I am looking for a feature to set the baseline of an object, fx an svg > > figure (rectangle, triangle etc) which makes it possible to let fx > > height and width of an object grow upwards and not downwards. Maybe by > > setting hori

Re: [whatwg] Script preloading

> Ok, and I'm saying they shouldn't be asking LABjs to handle it, they should > be asking the devtools teams at browser vendors to give them ways to deal > with it. You're not going to be able to pause execution for code, implement > future breakpoints, or debug root causes for this sort of thin

Re: [whatwg] Adding features needed for WebGL to ImageBitmap

Thanks Ken, that makes it much clearer to me. The main concern I have with all this is the potential for OOM crashes. I'm happy as long as the spec remains vague about what "undue latency" means, so we still have the possibility of gracefully degrading performance in low memory conditions by evic

Re: [whatwg] Script preloading

On Thu, Jul 11, 2013 at 10:46 PM, Kyle Simpson wrote: > > How is this any different from the case today when

Re: [whatwg] Script preloading

On 9 July 2013 20:39, Ian Hickson wrote: > > A topic that regularly comes up is script loading. > > I sent an e-mail responding to related feedback last year, though it > didn't get any replies to the script loading parts of it: > > > http://lists.w3.org/Archives/Public/public-whatwg-archive/2012

Re: [whatwg] Script preloading

On 7/11/13 6:00 AM, "Jake Archibald" wrote: >> >> >> >>Š almost 50% of scripts Š sent without proper >>caching headers. If the browser is doing what it should do, it won't >>cache those > >This is not how link[rel=subresource] should work, the first request >for the subresource should pick up f