ted to
maxLength. Namely, editing functionality understands grapheme clusters very
well, so you can change selections by moving caret right or left one
"character", and so forth. Web sites frequently perform some editing on the
text as you type it.
- WBR, Alexey Proskuryakov
) Is there a limit to how many bytes we should look at?
Related to the last question, WebKit doesn't implement re-navigation (neither
for charset sniffing, nor for ), and I don't think that we ever
should.
- WBR, Alexey Proskuryakov
> On Tue, 19 Jul 2011, Alexey Proskuryakov wrote:
>>
>> What meaning will this attribute have on a platform that simply doesn't
>> expose the notion of a file?
>
> None, presumably the same as "Content-Disposition: attachment" in the same
> case.
able file on Mac OS X,
then the system warns you about it on first launch, and tells you where it was
downloaded from, not where a link to the download was.
Hosting services do have their policies on what can be hosted. As we discuss a
way to subvert those policies, we shouldn't start with an assumption that it's
inconsequential.
- WBR, Alexey Proskuryakov
l
known domain. This kind of download could be same origin or cross origin.
Perhaps an author who has not been given permission to change server HTTP
responses is not trusted enough to change them via HTML either.
- WBR, Alexey Proskuryakov
as more platforms arise that have creative ways of
presenting data to users.
It also doesn't naturally help understanding that it's just poor man's
Content-Disposition:attachment. From this point of view, I like Ian's original
proposal (rel=attachment) more.
- WBR, Alexey Proskuryakov
ht" to "forward" appears
like a very appropriate thing to ask for, among other things necessary to
support vertical text.
- WBR, Alexey Proskuryakov
ertical text. For most people, left is
left, and up is up. There is no reason to make it more complicated than it is
already.
- WBR, Alexey Proskuryakov
" and "right" to mean something different would be
much more confusing in the long run. Just like we didn't redefine "left" and
"right" for RTL, I don't see why we need to do that for vertical text.
- WBR, Alexey Proskuryakov
g a site that tries to prevent me from leaving it, it's
always by returning a string from onbeforeunload.
- WBR, Alexey Proskuryakov
Appcache API has everything to provide progress UI to the user, but with every
good progress bar, there goes a Cancel button.
I suggest adding an abort() method to ApplicationCache interface.
- WBR, Alexey Proskuryakov
wards (which happens on live sites in
window.open()/write()/print()/close() scenario).
And yes, we only defer window.print() if the document is still "loading" at the
time of the call. There are obviously multiple definitions of "loading"
possible for this feature.
- WBR, Alexey Proskuryakov
org/show_bug.cgi?id=43658> - it has some information about
trickier aspects of the behavior. This looks like something that needs to be
formally specified.
- WBR, Alexey Proskuryakov
=44406> has a live demo (Firefox 3.6.10
handles it correctly, according to my reading of the spec).
- WBR, Alexey Proskuryakov
30.09.2010, в 18:21, Michael Nordman написал(а):
> I don't think 'fallback' entries can be foreign because they must be
> of the same-origin as t
- in particular, section 6.5.1 says "Let candidate be the fallback
resource" and then "If candidate is not marked as foreign..."
I found it confusing that there is a specific mention of foreign for explicit
entries, but not for fallback ones.
- WBR, Alexey Proskuryakov
with Firefox), I think
it's something we could eventually do, but only if HTML5 agrees.
- WBR, Alexey Proskuryakov
w.w3.org/TR/REC-html40/intro/sgmltut.html#h-3.3.4.2
>. I do not really suggest following this aspect of it, although it's
the most pure logically. Firefox behavior seems the most practical to
me.
- WBR, Alexey Proskuryakov
Kit bug <https://bugs.webkit.org/show_bug.cgi?id=22678
>.
- WBR, Alexey Proskuryakov
ssing of Document objects
already associated with an application cache in the cache group.
Which part of the spec wins?
- WBR, Alexey Proskuryakov
On 05.03.2010, at 15:32, Alexey Proskuryakov wrote:
for something no one should care about, as you
implied above.
From API perspective I do care. Web developers shouldn't need to know
about the protocol, yet (s)he should be able to understand what
bufferedAmount means.
An explanation
"it's how much data is buffered to be sent over
network" seems adequate to me.
- WBR, Alexey Proskuryakov
t makes the results slightly
misleading, even if that's so slightly that it's not important in
practice.
Remembering frame offsets even after data has been serialized to a
stream is an unusual requirement for networking code.
- WBR, Alexey Proskuryakov
xclude protocol overhead in bufferedAmount, and we know
that there are 8 bytes still queued (a\xFF\x00data\xFF), and we know
that there were three frames sent (with an overhead of 6 bytes) how
would we know that the answer is 5?
- WBR, Alexey Proskuryakov
nt when establishing
a connection, adding a small constant at the beginning will make no
difference to flow control. And the constant is going to be zero in
practice, because the data will immediately go where we can't see it.
- WBR, Alexey Proskuryakov
specs.
I find it unfortunate that where the spec says "queue a task", most
(or all) implementations will perform those actions immediately. This
may be indistinguishable from JavaScript client code, but it will be a
source of confusion for developers.
- WBR, Alexey Proskuryakov
ocket and removing all data that was received. The spec says "When a
user agent is to close the Web Socket connection, it must drop all
subsequent data from the server" - but with the current spec text, you
can get message events after you call close() from onopen handler.
..
Would that be acceptable?
I don't understand what this means.
- WBR, Alexey Proskuryakov
establishing streaming connections over proxies, but the point stands, as the
actual implementation is shared.
- WBR, Alexey Proskuryakov
ch when it was made in XHR specs (both v1 and
v2), and I think that it should be reverted.
- WBR, Alexey Proskuryakov
ich runs "atomically".
- WBR, Alexey Proskuryakov
what JavaScript code sees, and all the intermediaries must (and do)
act as if that were the real thing.
- WBR, Alexey Proskuryakov
ttpRequest events.
XMLHttpRequest network events are "asynchronous" too.
Looks like the spec says so now. Does any browser post XMLHttpRequest
events asynchronously? This change in the spec is not harmless, as it
seems to make readystatechange event pretty much useless.
- WBR, Alexey Proskuryakov
On 03.12.2009, at 9:50, Alexey Proskuryakov wrote:
If server sends back handshake response and a data frame, and close
immediately, fast enough to run JavaScript on browser, how
readyState should be?
I'd expect it to work in the same way it works for XMLHttpRequest -
e.g.,
, the test is available
at <http://trac.webkit.org/browser/trunk/LayoutTests/websocket/tests/script-tests/simple.js?rev=51615
>, and its expected results at <http://trac.webkit.org/browser/trunk/LayoutTests/websocket/tests/simple-expected.txt
>.
- WBR, Alexey Proskuryakov
k it makes more sense to return a resolved URL - e.g. (new
WebSocket("ws://host/path/../")).URL would return "ws://host/".
- WBR, Alexey Proskuryakov
an authentication token", and if the UA fails to send
the
right extra bit, then fail. I think if we did this, we'd want to punt
until version 2, though.
Yes, I think that relying on HTTP specs to define authentication to
Web Sockets takes the "fake HTTP handshake" concept too far.
- WBR, Alexey Proskuryakov
an to correct in the spec?
If practical uses of Web Sockets are all going to be over SSL (for
proxy compatibility reasons), then even Basic auth seems ok for many
cases, but NTLM still has important benefits over it. The primary
benefit I'm aware of is that passwords don't need to be stored on the
server.
- WBR, Alexey Proskuryakov
on connection basis, so I
don't think that closing the connection right after receiving a
challenge can work with them.
- WBR, Alexey Proskuryakov
the close().
Why not? My understanding is that it can take arbitrary amount of time
- the server can choose not to close its side of connection for years,
and to send data over it.
- WBR, Alexey Proskuryakov
d likely make the intention clearer.
- WBR, Alexey Proskuryakov
a requirement to immediately change readyState to
CLOSED, and to fire a close event. If all this happens asynchronously
after the server agrees to close the connection, then my example will
work fine, of course.
- WBR, Alexey Proskuryakov
ing and doesn't raise
exceptions would be a clear signal that send() just blocks until it's
possible to send data to me, and I'm sure to many others, as well.
There is no reason to silently drop data sent over a TCP connection -
after all, we could as well base the protocol on UDP if we did, and
lose nothing.
- WBR, Alexey Proskuryakov
needed is of course
file uploading, but even if we dismiss it as a special case that can
be served with custom code, there's also e.g. captured video or audio
that can be downgraded in quality for slow connections.
- WBR, Alexey Proskuryakov
);
- the client never learns that the server is done sending data.
As Web Sockets are basically at the same level as TCP, and TCP
provides complete info about socket state, I don't think that
delegating connection closing to app-level protocols would be
appropriate.
- WBR, Alexey Proskuryakov
but it's a potential issue at all stages -
from generating content to checking it with automated tools to
consuming it.
For authors and admins, it may be a nuisance to maintain an UTF-8 text
file if the rest of the site is in a different encoding.
- WBR, Alexey Proskuryakov
Disregarding charset from
HTTP headers is just a weird special case for a few text resource
types. If we were going to deprecate HTML, XML and CSS, but keep
appcache manifest going forward, it could maybe make sense.
- WBR, Alexey Proskuryakov
ink makes sense).
Thus, I think that the way for a persistent worker to manipulate the
cache is by opening a browser window with an HTML document.
- WBR, Alexey Proskuryakov
s in terms of a model for users, not any
specific security threats - if we think of persistent workers as an
equivalent of native applications that need installation, then we
should consider that native applications don't usually update
themselves without user consent.
- WBR, Alexey Proskuryakov
exposing application cache APIs to them.
- WBR, Alexey Proskuryakov
On 24.03.2009, at 8:09, Ian Hickson wrote:
(I would expect Firefox, Safari, and Chrome to follow suit; Firefox
for
compatibility, and Safari and Chrome for privacy.)
FWIW, WebKit returns just the file name now.
- WBR, Alexey Proskuryakov
honored, adding special cases is an unnecessary
complication.
Formally, a proxy can re-encode any text/* resource and expect the
client to honor Content-Type charset over and built-in
preconceptions, although I think that such proxies are extremely rare
in this millennium.
- WBR, Alexey
n to use.
My point is that the manifest format is quite extensible as it is, so
only a very drastic change would require versioning.
But anyway, it will still be possible to change signatures: just use
"^?EXTENDED CACHE MANIFEST", not "^?CACHE MANIFEST2".
- WBR, Alexey Proskuryakov
L5 one may affect existing clients.
this means we could never do:
"^?CACHE MANIFEST2"
If incompatible changes to the format are ever needed, we can change
Content-Type.
- WBR, Alexey Proskuryakov
s
whose namespaces are already in the mapping. I don't think that it is
helpful - fallback namespaces are matched by prefix, so it doesn't
resolve ambiguity. I suggest dropping this requirement, possibly
specifying that if the map is ambiguous, the first match wins.
- WBR, Alexey Proskuryakov
nate(), no messages will
be
dispatched to worker's event listeners.
Once 'closing' is set to true, the queue discards any additional
tasks.
There is no "closing" flag on the Worker object, it's only defined on
WorkerGlobalScope as far as I can see.
- WBR, Alexey Proskuryakov
is added for
terminate algorithm, and this looks like a copy/paste mistake, because
the event won't be dispatched anyway.
- WBR, Alexey Proskuryakov
ent to what Gecko does, I believe.
Note however that I'm talking about worker objects here, not ports.
- WBR, Alexey Proskuryakov
rm of algorithms, and relies on a number of
arguable implicit assumptions on the implementation of their steps, it is
hard to process or verify the algorithms. In my opinion (I'm not claiming
expertise either!), a message passing design would be much clearer.
There are lots of discussions about designing multi-threaded algorithms on
the net, one I liked quite a bit recently is
<http://codemines.blogspot.com/2006/09/another-thread-on-threads.html> - it
presents the do's and don'ts very well.
- WBR, Alexey Proskuryakov.
origin and effective script origin of scripts running in workers are
the origin of the absolute URL given that the worker's
locationattribute represents."
- WBR, Alexey Proskuryakov
sages are queued in closed ports until those are
started, so I think that it applies word to word to closed ports.
- WBR, Alexey Proskuryakov
Nov 14, 2008, в 10:00 AM, Jonas Sicking написал(а):
What are the use cases? Also note that we can't use it with shared
workers since they can be connected to several pages from
different uris.
It returns the script's URL, not the page's.
Oh?! Then I understand even less what the use case
fact, I'm strongly considering dropping MessagePort from WebKit (at
least for now), and going with Mozilla worker API.
- WBR, Alexey Proskuryakov
HTML5 channel messaging) should be cleaned up
from anything that mentions synchronous access to entangled port's
data structures to really be verified for correctness. This is not
straightforward, and may seriously affect the API - e.g., I doubt that
passing MessagePorts around is implementable with reasonable
complexity, and there is not a lot of use in MessagePorts if they
cannot be passed around.
- WBR, Alexey Proskuryakov
around MessagePorts, so I
suggest we table that for v2. It can always be added back later.
Since they so drastically affect the API design, I think putting
them off
is a mistake. We might end up constraining ourselves in unobvious
ways.
I agree.
- WBR, Alexey Proskuryakov
thinking can be corrected rather
easily, but not all of them. So, I do not really see how anyone can
claim implementing the spec, or even a subset of it at this point.
- WBR, Alexey Proskuryakov
issue any more - Aaron's
explanation about the name of event dispatched by connect() is
perfectly fine with me, and I don't think there are any issues with
MessagePort.startConversation().
- WBR, Alexey Proskuryakov
hy I'm concerned about the details of this particular proposal.
- WBR, Alexey Proskuryakov
) method is a convenience method that
simplifies create a new MessageChannel and invokingpostMessage() with
one of the new ports." - it doesn't do anything postMessage() couldn't
do. Receivers are supposed to differentiate events by evt.data.
- WBR, Alexey Proskuryakov
on Worker objects must act as if, when invoked, they immediately
invoked the method of the same name on the port, with the same
arguments").
- WBR, Alexey Proskuryakov
e also installed by ports to listen to
messages.
- WBR, Alexey Proskuryakov
as
making GC dispatch "close" to fix it from other side would suffer from
basically the same logical problem.
- WBR, Alexey Proskuryakov.
as a number of other options. If we create a separate
interface for every Worker isolation level needed (both inside and
outside), we'll soon end up with PrivateWorker, SharedDataWorker and
who knows what else.
- WBR, Alexey Proskuryakov
t developer feedback already).
- WBR, Alexey Proskuryakov
ple case" looks no different, but there is no
confusion about which port to use.
- WBR, Alexey Proskuryakov
cept the constructor is
SharedWorker("foo.js", "foo");
Is there any benefit in having a different name for this constructor?
If dedicated and shared workers are going to have identical
implementation (notably, if they have exactly the same lifetime), I
don't see any benefit in making them look different.
- WBR, Alexey Proskuryakov
ourse.
- WBR, Alexey Proskuryakov
tructor), it becomes indistinguishable from a dedicated worker.
Hiding close() possibly sounds more like something a high-level
framework may want to do to enforce a certain design pattern than a
core feature.
- WBR, Alexey Proskuryakov
st close the default port.
Both shared and dedicated workers have to maintain a strong reference
to a context that created them, just to have a context to execute
event listeners in. So, they are basically the same as far as
implementation is concerned AFAICT.
- WBR, Alexey Proskuryakov
rence in behavior?
- WBR, Alexey Proskuryakov
warning about the perils of NULLs
in strings (usually in C-style strings). At least for WebKit, I expect
that it would be safer and easier to avoid such problems without
introducing a new decoder mode just for manifests.
- WBR, Alexey Proskuryakov
kit/gbk.html>
<http://nypop.com/~ap/webkit/gb18030.html>
What differences are you seeing between Firefox and WebKit? It
seems that the behavior may be a bit more tricky than just treating
all encodings from GBK family as GB18030.
- WBR, Alexey Proskuryakov
On Feb 10, 2008, at 3:17 PM, Anne van Kesteren wrote:
On Sat, 09 Feb 2008 22:06:39 +0100, Alexey Proskuryakov
<[EMAIL PROTECTED]> wrote:
On Feb 9, 2008, at 12:58 PM, Anne van Kesteren wrote:
As far as the unload handler question, what are the semantics for
XHR?
I think the user l
ounds like a reasonable use case (really, is there a
better way?).
- WBR, Alexey Proskuryakov
That's a good question :)
- WBR, Alexey Proskuryakov
be some limits put on this, as otherwise a script
could continue to use resources indefinitely after a browser window is
closed. But I do not see where it is specified, explicitly or
implicitly.
- WBR, Alexey Proskuryakov
85 matches
Mail list logo
