Am 21.06.2011 02:16 schrieb Ojan Vafai:
It is certainly the case that some large subset of users use spaces to align
content, not to mention really care about things like two spaces after
periods, etc. One way or another, contentEditable needs to support this.
If we were starting with a clean
On 2011-06-20 21:28, Jonas Sicking wrote:
On Mon, Jun 20, 2011 at 7:13 AM, Per-Erik Brodin
per-erik.bro...@ericsson.com wrote:
On 2011-06-20 12:53, Jonas Sicking wrote:
Headers that the implementation adds doesn't need to be added to this
list. For example the Host header is set by the
On 2011-06-20 21:59, Ian Hickson wrote:
According to the CORS specification, a request is not to be terminated
even when the resource sharing check fails. However, when using CORS
with EventSource I think it may be justified since the response is
typically not returned right away.
Not sure
On 6/21/11 5:21 AM, Hallvord R. M. Steen wrote:
Another issue I noticed is in the text under the heading the
javascript: URL scheme - specifically the last otherwise part of the
text. This is about trying to navigate a window from a different origin
to a javascript: URL. Don't we expect a
On Mon, Jun 20, 2011 at 6:05 PM, Ryosuke Niwa rn...@webkit.org wrote:
Problem is that not all user agents, in particular, mail clients support
white-space: pre-wrap.
Good point. That's pretty much the final nail in the coffin. I'll
specify something with nbsp's here, although I don't know how
On 6/14/2011 2:32 AM, Tab Atkins Jr. wrote:
On Mon, Jun 13, 2011 at 2:29 AM, Brett Zamirbret...@yahoo.com wrote:
Thanks, that's helpful. Still would be nice to have item-* though...
Well, your idea for custom item-* attributes is just a way to more
concisely embed triples of non-visible data.
On Fri, 17 Jun 2011, ilya goberman wrote:
I do not really understand what specify the request to happen with
credentials really mean. Can someone explain or point to an example?
It just means that the user's relevant cookies are included in the
request.
My opinion is that it should be
