Re: [whatwg] apple-touch-icon

2014-07-28 Thread Mathias Bynens
On Sun, Jul 27, 2014 at 1:13 PM, Anne van Kesteren wrote: > For we already define the /favicon.ico fallback. If a > page lacks we should probably also look at > Apple's proprietary extension here given that it's quite widely > adopted. Chrome supports it and there is some work going on in Firefo

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Anne van Kesteren
On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson wrote: > That seems like it'd be no more complicated, but would involve less new > API surface (not to mention fewer new ways to shoot yourself in the foot, > e.g. getting the 'fetch-as' value wrong), and wouldn't require us to come > up with a way to e

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Anne van Kesteren
On Wed, Jul 23, 2014 at 1:07 AM, Ben Maurer wrote: > To follow this up with a concrete suggestion: > > var myfetch = window.fetch('my.css', {'fetch-as': 'stylesheet'}); > myfetch.then(function(resp) { > document.body.appendChild(resp.body.asStyleSheet()); > }); If you have 'fetch-as' you need a

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Anne van Kesteren
On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson wrote: > Why not: > >var mystyle = E('link', { rel: 'stylesheet', href: 'my.css', whenneeded: > true }); >document.body.appendChild(mystyle); >var myfetch = mystyle.fetch; >... > > ...where "E()" is some mechanism to easily create new e

Re: [whatwg] why does fetch() specify response body processing frequency?

2014-07-28 Thread Anne van Kesteren
On Wed, Jul 23, 2014 at 5:42 AM, Takeshi Yoshino wrote: > "process response body" in the XHR spec is only handling errors and firing a > readystatechange event and ProgressEvents. "response" in the XHR spec [1] is > set to the argument "response" of "process response" hook. I think this > "set" me

Re: [whatwg] How to determine content-type of file: protocol

2014-07-28 Thread duanyao
On 07/28/2014 06:34, Gordon P. Hemsley wrote: Sorry for the delay in responding. Your message fell through the cracks in my e-mail filters. On 07/17/2014 08:26 AM, duanyao wrote: Hi, My first question is about a rule in MIME Sniffing specification (http://mimesniff.spec.whatwg.org): 5.

Re: [whatwg] How to determine content-type of file: protocol

2014-07-28 Thread Gordon P. Hemsley
On 07/28/2014 08:01 AM, duanyao wrote: On 07/28/2014 06:34, Gordon P. Hemsley wrote: Sorry for the delay in responding. Your message fell through the cracks in my e-mail filters. On 07/17/2014 08:26 AM, duanyao wrote: Hi, My first question is about a rule in MIME Sniffing specification (http:

Re: [whatwg] apple-touch-icon

2014-07-28 Thread John Mellor
Chrome 30 dropped support[1] for fetching apple-touch-icon-* from well known URLs, since the 404 pages that are usually returned were consuming 3-4% of all mobile bandwidth usage[2]. We're unlikely to reverse that. We still support apple-touch-icon-* via link rel under some circumstances (e.g. for

Re: [whatwg] apple-touch-icon

2014-07-28 Thread Kevin Marks
Using a single JPEG/PNG that is also part of the home page display is a way to mitigate bandwidth used. Another way to do this is to use an SVG for a logo - which browsers support this now? On 28 Jul 2014 07:59, "John Mellor" wrote: > Chrome 30 dropped support[1] for fetching apple-touch-icon-* f

Re: [whatwg] How to determine content-type of file: protocol

2014-07-28 Thread duanyao
On 07/28/2014 22:08, Gordon P. Hemsley wrote: On 07/28/2014 08:01 AM, duanyao wrote: On 07/28/2014 06:34, Gordon P. Hemsley wrote: Sorry for the delay in responding. Your message fell through the cracks in my e-mail filters. On 07/17/2014 08:26 AM, duanyao wrote: Hi, My first question is abo

[whatwg] Fullscreen API and out-of-process

2014-07-28 Thread Anne van Kesteren
There's two things the Fullscreen API does: 1. Resize the top-level browsing context's document's viewport. (I.e. resizing the window of the browser.) 2. Change state of that document and its descendant documents. 1 needs to happen asynchronously. 2 needs to happen from a task per-document. Poten

[whatwg] [Notifications] Behavior of Notification.requestPermission in workers

2014-07-28 Thread Peter Beverloo
Since the entire Notification object is exposed both on window and in workers, I'd like some clarification on the intended behavior of Notification.requestPermission() when called in the background. http://notifications.spec.whatwg.org/#dom-notification-requestpermission Some options: (1) Re

Re: [whatwg] [Notifications] Behavior of Notification.requestPermission in workers

2014-07-28 Thread Anne van Kesteren
On Mon, Jul 28, 2014 at 6:55 PM, Peter Beverloo wrote: > Any opinions? I prefer (4), add [Exposed=Window]. -- http://annevankesteren.nl/

Re: [whatwg] [Notifications] Behavior of Notification.requestPermission in workers

2014-07-28 Thread Peter Beverloo
That'd work for me too. Peter On Mon, Jul 28, 2014 at 1:00 PM, Anne van Kesteren wrote: > On Mon, Jul 28, 2014 at 6:55 PM, Peter Beverloo > wrote: > > Any opinions? > > I prefer (4), add [Exposed=Window]. > > > -- > http://annevankesteren.nl/ >

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ian Hickson
On Mon, 28 Jul 2014, Anne van Kesteren wrote: > On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson wrote: > > Why not: > > > >var mystyle = E('link', { rel: 'stylesheet', href: 'my.css', whenneeded: > > true }); > >document.body.appendChild(mystyle); > >var myfetch = mystyle.fetch; > >.

Re: [whatwg] [Notifications] Behavior of Notification.requestPermission in workers

2014-07-28 Thread Anne van Kesteren
On Mon, Jul 28, 2014 at 7:04 PM, Peter Beverloo wrote: > That'd work for me too. Done: https://github.com/whatwg/notifications/commit/cd7c05b55faa8580287f3afd9e9f011df5eefa37 -- http://annevankesteren.nl/

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Anne van Kesteren
On Mon, Jul 28, 2014 at 7:07 PM, Ian Hickson wrote: > On Mon, 28 Jul 2014, Anne van Kesteren wrote: >> On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson wrote: >>>var mystyle = E('link', { rel: 'stylesheet', href: 'my.css', whenneeded: >>> true }); >>>document.body.appendChild(mystyle); >>>

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ian Hickson
On Mon, 28 Jul 2014, Anne van Kesteren wrote: > > On Mon, Jul 28, 2014 at 7:07 PM, Ian Hickson wrote: > > On Mon, 28 Jul 2014, Anne van Kesteren wrote: > >> On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson wrote: > >>>var mystyle = E('link', { rel: 'stylesheet', href: 'my.css', > >>> whenneeded:

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread ι™ˆζ™Ίζ˜Œ
On Mon, Jul 28, 2014 at 10:14 AM, Anne van Kesteren wrote: > On Mon, Jul 28, 2014 at 7:07 PM, Ian Hickson wrote: > > On Mon, 28 Jul 2014, Anne van Kesteren wrote: > >> On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson wrote: > >>>var mystyle = E('link', { rel: 'stylesheet', href: 'my.css', > whe

Re: [whatwg] Fullscreen API and out-of-process

2014-07-28 Thread Adam Barth
Can you explain what experiment you could run to determine whether (2) happens synchronously or asynchronously? Adam On Jul 28, 2014 9:03 AM, "Anne van Kesteren" wrote: > There's two things the Fullscreen API does: > > 1. Resize the top-level browsing context's document's viewport. (I.e. > resi

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ben Maurer
What about initial parameters to fetch (vs modifications you could make in flight via the myfetch object). Would there be an attribute of that you could use to pass parameters to fetch (eg a custom header)? On Mon, Jul 28, 2014 at 10:24 AM, Ian Hickson wrote: > On Mon, 28 Jul 2014, Anne van Ke

Re: [whatwg] Fullscreen API and out-of-process

2014-07-28 Thread Anne van Kesteren
On Mon, Jul 28, 2014 at 7:42 PM, Adam Barth wrote: > Can you explain what experiment you could run to determine whether (2) > happens synchronously or asynchronously? I'm not sure I understand the question. Do you mean if you can observe that the tasks in different documents might run at the sam

Re: [whatwg] Fullscreen API and out-of-process

2014-07-28 Thread Daniel Cheng
Caveat: I'm not really familiar with the fullscreen API implementation in Chrome. I imagine the synchronous checks would be implemented with a sync IPC from the requesting renderer to the browser (which implies the browser process must keep track of the fullscreen enabled flag and whether or not t

Re: [whatwg] Fullscreen API and out-of-process

2014-07-28 Thread Adam Barth
On Jul 28, 2014 10:58 AM, "Anne van Kesteren" wrote: > > On Mon, Jul 28, 2014 at 7:42 PM, Adam Barth wrote: > > Can you explain what experiment you could run to determine whether (2) > > happens synchronously or asynchronously? > > I'm not sure I understand the question. > > Do you mean if you ca

Re: [whatwg] Fullscreen API and out-of-process

2014-07-28 Thread James Robinson
On Mon, Jul 28, 2014 at 9:03 AM, Anne van Kesteren wrote: > (How are animation frames synchronized across > boundaries?) > requestAnimationFrame specifies that the callback fires for all iframes within the same task, but it's not black-box observable between cross-origin iframes so it doesn't m

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ian Hickson
On Mon, 28 Jul 2014, Ben Maurer wrote: > > What about initial parameters to fetch (vs modifications you could make > in flight via the myfetch object). Would there be an attribute of > that you could use to pass parameters to fetch (eg a custom header)? What's the use case here? Why are we tryi

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ben Maurer
The idea is you could specify any parameter to fetch. For example, if fetch allowed you to specify an HTTP/2 priority, you could specify that. As a concrete example of why passing a header might be useful, Facebook uses an automated pipeline to decide what CSS/JS files to package together. If we c

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ian Hickson
On Mon, 28 Jul 2014, Ben Maurer wrote: > > The idea is you could specify any parameter to fetch. For example, if > fetch allowed you to specify an HTTP/2 priority, you could specify that. > > As a concrete example of why passing a header might be useful, Facebook > uses an automated pipeline to

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Ben Maurer
On Mon, Jul 28, 2014 at 12:51 PM, Ian Hickson wrote: > > Ah, I see. Makes sense. > > Are there any cases where you'd know the headers you want to send at the > time the markup is written, before JS is involved, or would you always be > updating the fetch settings from script? I think there are c

Re: [whatwg] Fetch Objects and scripts/stylesheets

2014-07-28 Thread Anne van Kesteren
On Mon, Jul 28, 2014 at 8:34 PM, Ian Hickson wrote: > What's the use case here? Why are we trying to send custom headers on a > ? E.g. for and such you want to turn authentication dialogs off. Cross-origin images can be fine, but not if they start spawning confusing dialogs to users making them

Re: [whatwg] Fullscreen API and out-of-process

2014-07-28 Thread Anne van Kesteren
On Mon, Jul 28, 2014 at 8:16 PM, Adam Barth wrote: > I meant a black-box experiment (i.e., no access to browser internal state). > Put another way, can you describe a sequence of events in which the author > or the user could observe the difference? If not, then the question is > moot. Well if b