Maciej, Adam,
On 03/17/2012 12:26 AM, Maciej Stachowiak wrote:
Therefore, I think this work is not appropriate for the WebKit repository at
this time, even as a WebCore Module. Of course, implementing the feature
outside the main repository, e.g. via GitHub, is ok, and may be an opportunity
Hi,
On Wed, Feb 29, 2012 at 12:00 PM, William Siegrist wsiegr...@apple.com wrote:
This should be fixed now.
trac is down today for us.
bugs.webkit.org is also down with this error :
Software error:
Can't connect to the database.
Error: could not connect to server: Operation timed out
On 19 March 2012 22:44, Alexis Menard alexis.men...@openbossa.org wrote:
Hi,
On Wed, Feb 29, 2012 at 12:00 PM, William Siegrist wsiegr...@apple.com
wrote:
This should be fixed now.
trac is down today for us.
bugs.webkit.org is also down with this error :
I'm also seeing them down with
On Mon, Mar 19, 2012 at 8:37 AM, Mike Lawther mikelawt...@google.comwrote:
On 19 March 2012 22:44, Alexis Menard alexis.men...@openbossa.org wrote:
Hi,
On Wed, Feb 29, 2012 at 12:00 PM, William Siegrist wsiegr...@apple.com
wrote:
This should be fixed now.
trac is down today for us.
All services have been restored.
-Bill
On Mar 19, 2012, at 4:44 AM, Alexis Menard wrote:
Hi,
On Wed, Feb 29, 2012 at 12:00 PM, William Siegrist wsiegr...@apple.com
wrote:
This should be fixed now.
trac is down today for us.
bugs.webkit.org is also down with this error :
Just taking the opportunity here since it's Trac related, but the link
that is sent on a new user registration is currently wrong, just need
to do a s/www/trac/ on the URL sent.
Best regards,
Luis Felipe
On Mon, Mar 19, 2012 at 10:53 AM, William Siegrist wsiegr...@apple.com wrote:
All services
On Mar 19, 2012, at 9:02 AM, Luis Felipe Strano Moraes luis.str...@gmail.com
wrote:
Just taking the opportunity here since it's Trac related, but the link
that is sent on a new user registration is currently wrong, just need
to do a s/www/trac/ on the URL sent.
Actually, the www link is
Well, I've already registered by using the trac subdomain, but trying
it again now gives me a Bad or expired token. message, which I
assume means your fix has worked.
--lf
On Mon, Mar 19, 2012 at 1:12 PM, William Siegrist wsiegr...@apple.com wrote:
On Mar 19, 2012, at 9:02 AM, Luis Felipe
Yes, that's close enough. Thanks for testing and sorry for the inconvenience.
-Bill
On Mar 19, 2012, at 9:25 AM, Luis Felipe Strano Moraes luis.str...@gmail.com
wrote:
Well, I've already registered by using the trac subdomain, but trying
it again now gives me a Bad or expired token.
Hey,
I intend to add a graph in the inspector's timeline panel that shows the
number of global handles for V8. The V8 bindings use maps for WebCore
objects to global handles to V8 wrapper objects. A steady increase of
global handles is often a sign of a memory leak within v8 bindings.
My
I intend to add a graph in the inspector's timeline panel that shows the
number of global handles for V8. The V8 bindings use maps for WebCore objects
to global handles to V8 wrapper objects. A steady increase of global handles
is often a sign of a memory leak within v8 bindings.
Are you
On Mon, Mar 19, 2012 at 9:47 PM, Geoffrey Garen gga...@apple.com wrote:
I intend to add a graph in the inspector's timeline panel that shows the
number of global handles for V8. The V8 bindings use maps for WebCore
objects to global handles to V8 wrapper objects. A steady increase of
global
Maciej, I've been trying to find a home for Ink data for some time.
The one inroad I've made was to make the case in the touch events 2
proposal:
https://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html
Is that what I should move forward with, with Ink?
I've been following the Sensor
Hi,
There is a patch posted https://bugs.webkit.org/show_bug.cgi?id=81590 for
removal of the 'magic iframe' feature. This is the ability to move 'live'
iframe from one page to another w/o unloading it.
If you have interest or ideas about this feature, please reply.
HISTORY
This feature was added
Hi Dmitry.
Two thoughts on this:
(1) If we remove this feature, are Chromium/GMail developers going to
re-request the other shared document features that this feature subsumed? Or
are y'all now convinced that shared document is, in general, not a good idea?
The reason I ask this is that,
On Mon, Mar 19, 2012 at 6:09 PM, Geoffrey Garen gga...@apple.com wrote:
Hi Dmitry.
Two thoughts on this:
(1) If we remove this feature, are Chromium/GMail developers going to
re-request the other shared document features that this feature subsumed?
Or are y'all now convinced that shared
I support the removal. I've seen quite a few security bugs caused by this
feature.
Please make sure the spec changes as Geoff pointed out.
- Ryosuke
On Mon, Mar 19, 2012 at 5:51 PM, Dmitry Titov dim...@chromium.org wrote:
Hi,
There is a patch posted
I have no immediate objection to removing the shared iframe feature since, as
you say, it's a source of problems, very few apps use it, and no apps require
it. It's great that we did this feature through a pre-existing web technology,
so we discovered its problems, and can now remove it,
Hello WebKittens,
While I am loathe to take up list space with another style guide
threads, Eric Seidel recently pointed out to me some ambiguities in
the style guide at https://bugs.webkit.org/show_bug.cgi?id=81602.
Namely sections three and four of the #include Statements section.
The relevant
19 matches
Mail list logo
