Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Alexey Proskuryakov
18.01.2012, в 17:01, Adam Barth написал(а): >>> My understanding is that Safari, as shipping, does not use the referring >>> page's charset for decoding the C-D filename. Or am I missing something? So >>> what default is left? The client's locale? >> >> Yes, someone broke that. I'm in the proc

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Adam Barth
2012/1/18 Julian Reschke : > If you can write down what you think needs to be done, and can get > Chrome/Firefox/IE/Opera on board, this may be worth documenting. I think > that's what Adam tried ~ 15 months ago. By the way, this my long-term goal. My plan has been to align browser behavior befor

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Adam Barth
2012/1/18 Alexey Proskuryakov : > 18.01.2012, в 16:23, Julian Reschke написал(а): >> My understanding is that Safari, as shipping, does not use the referring >> page's charset for decoding the C-D filename. Or am I missing something? So >> what default is left? The client's locale? > > Yes, someo

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Julian Reschke
On 2012-01-19 01:42, Alexey Proskuryakov wrote: 18.01.2012, в 16:23, Julian Reschke написал(а): It's been communicated (see) that a behavior that relies on external state won't be accepted. I don't think that it's fair

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Alexey Proskuryakov
18.01.2012, в 16:23, Julian Reschke написал(а): >> It's been communicated >> (see) >> that a behavior that relies on external state won't be accepted. I don't >> think that it's fair to blame browser vendors for not worki

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Julian Reschke
On 2012-01-19 01:00, Alexey Proskuryakov wrote: 18.01.2012, в 15:41, Julian Reschke написал(а): We asked browser developers to write down what *they* think is needed, and didn't get a proposal -- mainly because the browsers do not interoperate on this. It's been communicated (see

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Alexey Proskuryakov
18.01.2012, в 15:41, Julian Reschke написал(а): > We asked browser developers to write down what *they* think is needed, and > didn't get a proposal -- mainly because the browsers do not interoperate on > this. It's been communicated (see

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Julian Reschke
On 2012-01-19 00:28, Alexey Proskuryakov wrote: 18.01.2012, в 13:02, Adam Barth написал(а): I used to hold that opinion, but folks convinced me (and the rest of the httpbis working group) otherwise, hence the standard. A working group that that can be convinced to specify something so out of

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Alexey Proskuryakov
18.01.2012, в 13:02, Adam Barth написал(а): > I used to hold that opinion, but folks convinced me (and the rest of > the httpbis working group) otherwise, hence the standard. A working group that that can be convinced to specify something so out of line with how browsers work is not one we shou

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Adam Barth
2012/1/18 Alexey Proskuryakov : > 18.01.2012, в 11:26, Geoffrey Garen написал(а): >> Once again, I think the best option is to make a decision about >> deprecatedFrameEncoding based on its merits. > > Most browsers respect default encoding when parsing Content-Disposition (*), > which is against

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Julian Reschke
On 2012-01-18 21:11, Alexey Proskuryakov wrote: 18.01.2012, в 11:26, Geoffrey Garen написал(а): Once again, I think the best option is to make a decision about deprecatedFrameEncoding based on its merits. Most browsers respect default encoding when parsing Content-Disposition (*), which is

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Alexey Proskuryakov
18.01.2012, в 11:26, Geoffrey Garen написал(а): > Once again, I think the best option is to make a decision about > deprecatedFrameEncoding based on its merits. Most browsers respect default encoding when parsing Content-Disposition (*), which is against the letter and spirit of RFC 6266. So I

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Adam Barth
On Wed, Jan 18, 2012 at 11:26 AM, Geoffrey Garen wrote: >> All that being said, if you don't wish to comply with this standard at >> this time, that's your choice.  I'm just asking for an ifdef so I can >> turn this non-standards compliant code off in the Chromium port. > > We don't typically add

Re: [webkit-dev] Removing deprecatedFrameEncoding

2012-01-18 Thread Geoffrey Garen
> All that being said, if you don't wish to comply with this standard at > this time, that's your choice. I'm just asking for an ifdef so I can > turn this non-standards compliant code off in the Chromium port. We don't typically add #ifdefs to cross-platform WebKit code solely to make different

Re: [webkit-dev] WEBKITOUTPUTDIR documentation

2012-01-18 Thread Seo Sanghyeon
Done. https://bugs.webkit.org/show_bug.cgi?id=76544 2012/1/18, Raphael Kubo da Costa : > Seo Sanghyeon writes: > >> Building WebKit document at http://www.webkit.org/building/build.html >> seems to suggest that WEBKITOUTPUTDIR only works on Windows, >> but this is not the case. >> >> Current word