Hi there,
At the moment WebKit does not deliberately expose any of the properties of
Javascript objects to clients. Those it does expose seem to be as much by
luck as anything else. One example is navigator.useragent, which in Qt's
case ultimately returns whatever the client has set in
Sounds like you want XBL. :)
On Mon, Sep 28, 2009 at 8:27 PM, Chris Frost chrisfros...@gmail.com wrote:
Hello All,
I am thinking about creating some custom HTML tags to abstract the process
of creating graphical widgets such as clock and calendar. To make it work, I
would imagine I need
If your goal is to specify the useragent string that can be done
entirely in the API layer without modifying WebCore at all (this is
how Mac browsers built on the system WebKit specify their app name).
The changes you're requesting should not involve WebCore in any way.
If you're wanting
Hello all
Now, I have a problem and I don't konw how to solve it, I hope you
help me, thank you!
I have written a scripting plugin with NPAPI and this plugin has
some properties and methods. it has a intValue property and two methods of
getValue and setValue. Now I don't
Hi Kevin,
WebKit approach is NOT to free memory before quit to make the quit process
as fast as possible. The memory manager should free the unfreed objects.
However, this approach makes really hard to find the real leaks (which
are unreferenced objects).
In my experince the unfreed (non-leak)
Some leak checkers are based on all objects being deleted at shutdown.
Those won’t work with WebKit. It doesn’t delete all objects at shutdown.
Other leak checkers are based on finding unreachable objects. Those
work well with WebKit.
-- Darin
Hi Zoltan,
On Sep 29, 2009, at 12:39 PM, Zoltan Herczeg wrote:
Hi Kevin,
WebKit approach is NOT to free memory before quit to make the quit
process
as fast as possible. The memory manager should free the unfreed
objects.
However, this approach makes really hard to find the real leaks
7 matches
Mail list logo
