On 3/4/10 4:42 AM, Fumitoshi Ukai (鵜飼文敏) wrote:
Hi,
I noticed that WebSocket spec updated to not inlcude framing overhead in
bufferedAmount.
I asked that since from API point of view it doesn't make
much sense to have the frame bytes to be magically included in the
bufferedAmount.
What if we
On 3/4/10 4:11 AM, Ojan Vafai wrote:
WebKit would like to implement this in the (very) near future. Before
proceeding, we'd like to hear from other browser vendors that you're
roughly on board with this direction of adding beforeinput and input events.
Here are the changes I can think of that
On Thu, Mar 4, 2010 at 18:52, Olli Pettay olli.pet...@helsinki.fi wrote:
On 3/4/10 4:42 AM, Fumitoshi Ukai (鵜飼文敏) wrote:
Hi,
I noticed that WebSocket spec updated to not inlcude framing overhead in
bufferedAmount.
I asked that since from API point of view it doesn't make
much sense to
On 3/4/10 12:17 PM, Fumitoshi Ukai (鵜飼文敏) wrote:
On Thu, Mar 4, 2010 at 18:52, Olli Pettay olli.pet...@helsinki.fi
mailto:olli.pet...@helsinki.fi wrote:
On 3/4/10 4:42 AM, Fumitoshi Ukai (鵜飼文敏) wrote:
Hi,
I noticed that WebSocket spec updated to not inlcude framing
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(), Node.replaceChild(),
Node.insertBefore().
Is it option-specific, though? Last I checked, various
On Mar 4, 2010, at 2:27 AM, Stewart Brodie wrote:
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(), Node.replaceChild
(),
Node.insertBefore().
Is
On Thu, 04 Mar 2010 11:27:23 +0100, Stewart Brodie
stewart.bro...@antplc.com wrote:
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(),
Anne van Kesteren ann...@opera.com wrote:
On Thu, 04 Mar 2010 11:27:23 +0100, Stewart Brodie
stewart.bro...@antplc.com wrote:
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
On Thu, 04 Mar 2010 13:05:13 +0100, Stewart Brodie
stewart.bro...@antplc.com wrote:
Is this documented anywhere?
On some W3C mailing list archive I think.
By compatibility problems, presumably you
mean bugs in Firefox that were then exploited by content authors who
didn't know better?
Apart from compatibility issues, there's also the fact that requiring
explicit adopt/import is a pointless burden on authors.
Rob
--
He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We
On 3/3/2010 7:06 PM, Philip Taylor wrote:
On Wed, Mar 3, 2010 at 10:55 AM, Brett Zamirbret...@yahoo.com wrote:
On 3/2/2010 6:54 PM, Ian Hickson wrote:
On Tue, 2 Mar 2010, Elliotte Rusty Harold wrote:
Briefly it seems that? causes the parser to go into Bogus comment
state,
I'd like to see if I can move this forward a bit. Let's drop some of
my original suggestions and break the solution into two separate
simple features that we can discuss independently. Firstly, of the
problems with overlays listed in my original email ([1]), I think the
following are the most
12 matches
Mail list logo
