[whatwg] About the HTML spec inconsistency in URL APIs' Collect URL Parameters definition

2011-07-21 Thread Shawn Gong
Hello, When collecting URL Parameters, if we have ab, since the parameter between is empty, we ignore it, and get the parameterNames [a, b]; however, if we have a=b then we'll get a parameter with empty name and empty value, and have the parameterNames [a, , b]. The two behaviors are

Re: [whatwg] Specification of window.find()

2011-07-21 Thread Aryeh Gregor
On Wed, Jul 20, 2011 at 6:23 PM, Tim Down timd...@gmail.com wrote: Yes, but it's significantly better than the alternative, which is to write your own code to search for text that spans nodes. It shouldn't be *too* hard to write that code. First do the search in textContent and get a list of

Re: [whatwg] a rel=attachment

2011-07-21 Thread 坊野 博典
Greetings all, This is just out of curiosity. Would it be possible to give me the encoding used for this download attribute? I think we have several options when we use non-ASCII characters (this example uses Cyrillic characters) as the value of this attribute as listed below. 1. Use the same

Re: [whatwg] base in body

2011-07-21 Thread Mark Callow
On Wed, 20 Jul 2011 05:07:05 +0200, Boris Zbarsky bzbar...@mit.edu wrote: That said, I'm not sure I understand the security concern. What kind of whitelist-based filter would let through scripts whose URIs it does not control, exactly? Can the security concern be mitigated by only allowing

Re: [whatwg] base in body

2011-07-21 Thread Boris Zbarsky
On 7/21/11 11:51 PM, Mark Callow wrote: Seems like a bug in the whitelist filter to me. Shouldn't the filter be checking requests using the full URL just before they are dispatched? We're talking a filter on the HTML generation, not in the browser. -Boris