Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-25 00:57, Alexey Proskuryakov wrote: 24.01.2012, в 15:10, Julian Reschke написал(а): b) RFC 6266 works without UA sniffing if you're willing to serve plain ASCII to legacy browsers (IE< 9 and Safari) We are talking about how to encode existing non-ASCII file names, there is no

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 15:10, Julian Reschke написал(а): > b) RFC 6266 works without UA sniffing if you're willing to serve plain ASCII > to legacy browsers (IE < 9 and Safari) We are talking about how to encode existing non-ASCII file names, there is no equivalent plain ASCII to send instead. > We ha

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-25 00:02, Alexey Proskuryakov wrote: 24.01.2012, в 14:33, Julian Reschke написал(а): I know you don't like it but please stop spreading FUD. RFC 5987 allows senders to send the same thing to all clients without UA sniffing. If you have a different proposal for which this is true p

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 14:33, Julian Reschke написал(а): >>> I know you don't like it but please stop spreading FUD. RFC 5987 allows >>> senders to send the same thing to all clients without UA sniffing. If you >>> have a different proposal for which this is true please go ahead and write >>> it down.

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-24 23:28, Alexey Proskuryakov wrote: 24.01.2012, в 14:03, Julian Reschke написал(а): Having UTF-8 Content-Disposition served by all Web sites that offer downloads would be the ideal outcome from higher principles. RFC 5987 style gobbledygook really has no purpose here, and only co

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 14:03, Julian Reschke написал(а): >> Having UTF-8 Content-Disposition served by all Web sites that offer >> downloads would be the ideal outcome from higher principles. RFC 5987 style >> gobbledygook really has no purpose here, and only complicates life for >> implementors, site

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-24 22:50, Alexey Proskuryakov wrote: 24.01.2012, в 13:36, Julian Reschke написал(а): You may be right about the default browser encoding, but I'm pretty sure you are not right about UTF-8. Having UTF-8 Content-Disposition served by all Web sites that offer downloads would be the

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 13:36, Julian Reschke написал(а): > You may be right about the default browser encoding, but I'm pretty sure you > are not right about UTF-8. Having UTF-8 Content-Disposition served by all Web sites that offer downloads would be the ideal outcome from higher principles. RFC 5987

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-24 22:29, Alexey Proskuryakov wrote: 24.01.2012, в 11:07, Julian Reschke написал(а): My conclusion is that the "use the referring page's encoding" quirk isn't needed. You're welcome to prove me wrong. I'm happy that we agree on UTF-8 and default browser encoding being needed. Th

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 11:07, Julian Reschke написал(а): > My conclusion is that the "use the referring page's encoding" quirk isn't > needed. You're welcome to prove me wrong. I'm happy that we agree on UTF-8 and default browser encoding being needed. That's a huge step forward. Will this be reflected

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-24 19:44, Alexey Proskuryakov wrote: 24.01.2012, в 10:04, Julian Reschke написал(а): Sorry, Alexey. You did claim this is "needed for compatibility with existing content". Please be more careful with quotation marks. You are not quoting me, and I'm not sure what you actually ref

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 10:04, Julian Reschke написал(а): > Sorry, Alexey. > > You did claim this is "needed for compatibility with existing content". Please be more careful with quotation marks. You are not quoting me, and I'm not sure what you actually refer to. > But unless I'm missing something, *n

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-24 19:00, Alexey Proskuryakov wrote: 24.01.2012, в 9:45, Julian Reschke написал(а): Did you find out for how long this was broken? I can't even recall the last Safari update, insofar I have my doubts that this change affected any real world content. I didn't check when exactly t

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 9:45, Julian Reschke написал(а): > Did you find out for how long this was broken? I can't even recall the last > Safari update, insofar I have my doubts that this change affected any real > world content. I didn't check when exactly this broke. As discussed earlier in this threa

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-24 18:38, Alexey Proskuryakov wrote: 24.01.2012, в 02:41, Julian Reschke написал(а): Please see. Unless I'm testing the wrong thing (in which case I'd like to hear what's wrong!), it seems that neither Chrome nor Safari use the en

Re: [webkit-dev] Removing deprecatedFrameEncoding

24.01.2012, в 02:41, Julian Reschke написал(а): > Please see . > > Unless I'm testing the wrong thing (in which case I'd like to hear what's > wrong!), it seems that neither Chrome nor Safari use the encoding of the > referring page. At least

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-19 02:00, Julian Reschke wrote: ... Please see . Unless I'm testing the wrong thing (in which case I'd like to hear what's wrong!), it seems that neither Chrome nor Safari use the encoding of the referring page. At least not in th

Re: [webkit-dev] Removing deprecatedFrameEncoding

On Thu, Jan 19, 2012 at 1:38 PM, Geoffrey Garen wrote: >>> We don't typically add #ifdefs to cross-platform WebKit code solely to make >>> different choices about web standards and web compatibility in different >>> ports. (Have we ever done that before?) It strikes me as destructive to >>> Web

Re: [webkit-dev] Removing deprecatedFrameEncoding

>> We don't typically add #ifdefs to cross-platform WebKit code solely to make >> different choices about web standards and web compatibility in different >> ports. (Have we ever done that before?) It strikes me as destructive to >> WebKit and the web to start doing so now. I'm strongly opposed

Re: [webkit-dev] Removing deprecatedFrameEncoding

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/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/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

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

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

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

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

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

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/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

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

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

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

> 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] Removing deprecatedFrameEncoding

16.01.2012, в 16:24, Julian Reschke написал(а): > But we should keep in mind that what's much more important here is to > actually provide developers with a protocol/format that is interoperable for > non-ASCII. I note that Safari is the only current browser which doesn't > implement RFC 5987

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-17 01:06, Adam Barth wrote: On Mon, Jan 16, 2012 at 3:15 PM, Geoffrey Garen wrote: I just read through the Bugzilla bugs on this topic. Hopefully, I'm a mostly neutral observer. We should remove deprecatedFrameEncoding. Removing the code has the following benefits: 1) Standards

Re: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-17 00:57, Alexey Proskuryakov wrote: 16.01.2012, в 15:15, Geoffrey Garen написал(а): 1) Standards compliance. To me, this seems like your strongest argument. However… I'm pretty sure that no major browser implements - or maybe even intends to implement - all encoding-related as

Re: [webkit-dev] Removing deprecatedFrameEncoding

On Mon, Jan 16, 2012 at 3:15 PM, Geoffrey Garen wrote: > I just read through the Bugzilla bugs on this topic. Hopefully, I'm a mostly > neutral observer. > >> We should remove deprecatedFrameEncoding.  Removing the code has the >> following benefits: >> >> 1) Standards compliance. > > To me, this

Re: [webkit-dev] Removing deprecatedFrameEncoding

16.01.2012, в 15:15, Geoffrey Garen написал(а): >> 1) Standards compliance. > > To me, this seems like your strongest argument. However… I'm pretty sure that no major browser implements - or maybe even intends to implement - all encoding-related aspects of RFC 6266. For example, Chrome uses d

Re: [webkit-dev] Removing deprecatedFrameEncoding

Hi Adam. I just read through the Bugzilla bugs on this topic. Hopefully, I'm a mostly neutral observer. > We should remove deprecatedFrameEncoding. Removing the code has the > following benefits: > > 1) Standards compliance. To me, this seems like your strongest argument. However… > b) Most

Re: [webkit-dev] Removing deprecatedFrameEncoding

On Sun, Jan 15, 2012 at 9:52 PM, Adam Barth wrote: > We've previously discussed this topic in Bug 67882 and Bug 75905. > > We should remove deprecatedFrameEncoding. Removing the code has the > following benefits: > > 1) Standards compliance. There was a discussion in the HTTP working > group ab

[webkit-dev] Removing deprecatedFrameEncoding

We've previously discussed this topic in Bug 67882 and Bug 75905. We should remove deprecatedFrameEncoding. Removing the code has the following benefits: 1) Standards compliance. There was a discussion in the HTTP working group about whether the requesting context should be a factor in determin